mcpField
U
unit-planner

unit-planner

github.com/willoscarAgent workflows51739 installsUpdated 3w ago
Repository

About unit-planner

unit-planner is a workflow skill that turns a selected pipeline into a workspace-specific UNITS.csv execution contract. It can add units as scope changes and checks required columns and dependencies.

Key features

  1. 01Creates UNITS.csv from a pipeline template
  2. 02Adjusts units for expanded scope
  3. 03Checks required CSV columns
  4. 04Validates unit dependencies
  5. 05Can update STATUS.md with runnable units

Use cases

  1. 01Initializing a workspace execution plan
  2. 02Adding units when project scope expands
  3. 03Correcting dependencies and acceptance criteria

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/willoscar/research-units-pipeline-skills --skill unit-planner

After installing, type/unit-plannerin Claude Code to confirm it loaded.

Details

From the project README

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.

Comments

Markdown supported