Skip to content
Back to skills

Unit Planner

ASecurity

Instantiate or update a workspace `UNITS.csv` from a selected pipeline and units template (deps/checkpoints/acceptance).

  • 512 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added February 8, 2026
developmentpythongo

Security analysis

A100/100

Scanned September 20, 2026

npx -y skills add WILLOSCAR/research-units-pipeline-skills --skill unit-planner --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Unit Planner?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Unit Planner
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/willoscar-unit-planner/badge)](https://www.skillsdirectory.com/skills/willoscar-unit-planner)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: unit-planner
binding: library
description: "Instantiate or update a workspace `UNITS.csv` from a selected pipeline and units template (deps/checkpoints/acceptance)."
---

# Skill: unit-planner

## Triggers & routing

- **Trigger**: unit planner, generate UNITS.csv, execution contract, units template, 生成工作单元.
- **Use when**: 初始化/更新执行合同:从 pipeline 选择生成 `UNITS.csv`,或 scope 扩展需要新增 units/依赖。
- **Skip if**: `UNITS.csv` 已正确反映当前 scope(无需重写)。
- **Network**: none.
- **Guardrail**: 保持 CSV 合法;scope 增长时新增 units;只在满足验收后标 `DONE`。


## Goal

- Turn a pipeline (`pipelines/*.pipeline.md`) into a concrete `UNITS.csv` contract for a specific workspace.

## Inputs

- `PIPELINE.lock.md` (preferred) or a chosen `pipelines/*.pipeline.md`
- `templates/UNITS.*.csv` referenced by the pipeline front matter
- Existing workspace artifacts (to adjust scope if needed)

## Outputs

- `UNITS.csv` (in the workspace root)
- Optional: `STATUS.md` updated with next runnable units

## Procedure (MUST FOLLOW)
Uses: `templates/UNITS.*.csv`.


1. Read `PIPELINE.lock.md` (or ask to create it via `pipeline-router`).
2. Copy the pipeline’s `units_template` into the workspace as `UNITS.csv` if missing.
3. If `UNITS.csv` exists, only edit it to reflect:
   - new scope (add rows)
   - corrected dependencies
   - clarified acceptance criteria
4. Ensure every unit has: `unit_id`, `skill`, `outputs`, `acceptance`, `checkpoint`, `status`, `owner`.
5. Keep checkpoints consistent with `CHECKPOINTS.md`; add missing checkpoints if the pipeline uses custom checkpoints.

## Acceptance criteria (MUST CHECK)

- [ ] `UNITS.csv` parses as CSV and includes all required columns.
- [ ] Every `depends_on` references an existing `U###`.

## Side effects

- Allowed: edit `UNITS.csv`, `STATUS.md`, `CHECKPOINTS.md` (for adding custom checkpoints).
- Not allowed: change pipeline files in `pipelines/` unless requested.

## Troubleshooting

### Issue: `PIPELINE.lock.md` is missing

**Fix**:
- Run `pipeline-router` (Mode A) or `uv run python scripts/pipeline.py kickoff|init` to create `PIPELINE.lock.md` before generating units.

### Issue: `UNITS.csv` becomes invalid CSV after edits

**Fix**:
- Keep semicolon-delimited `inputs/outputs` and avoid unescaped commas inside fields; validate with `uv run python scripts/validate_repo.py`.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.