When should I use unit-planner?

unit-planner is useful in the following scenarios: • Workspace Initialization: Automatically generate a comprehensive UNITS.csv execution plan from a pipeline template when starting a new project or workspace. • Dynamic Scope Management: Seamlessly update existing task lists to include new units, dependencies, or revised acceptance criteria as project requirements evolve. • Workflow Standardization: Ensure every work unit follows a strict contract including checkpoints, skill assignments, and clear output definitions to maintain high quality and accountability. • Dependency Tracking: Automatically map and validate complex inter-task dependencies to ensure the correct execution order and prevent project bottlenecks.

unit-planner

from WILLOSCAR

Instantiate or update a workspace `UNITS.csv` from a selected pipeline and units template (deps/checkpoints/acceptance).**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`。

⭐1stars🔀0forks📁View on GitHub🕐Updated Jan 8, 2026⬇️1downloads

When & Why to Use This Skill

The unit-planner skill automates the decomposition of complex workflows into structured execution contracts. By transforming high-level pipelines into granular, trackable task units (UNITS.csv), it ensures project consistency, manages dependencies, and enforces rigorous acceptance criteria for reliable agentic execution.

Use Cases

Workspace Initialization: Automatically generate a comprehensive UNITS.csv execution plan from a pipeline template when starting a new project or workspace.
Dynamic Scope Management: Seamlessly update existing task lists to include new units, dependencies, or revised acceptance criteria as project requirements evolve.
Workflow Standardization: Ensure every work unit follows a strict contract including checkpoints, skill assignments, and clear output definitions to maintain high quality and accountability.
Dependency Tracking: Automatically map and validate complex inter-task dependencies to ensure the correct execution order and prevent project bottlenecks.

name	unit-planner
description	\|
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`。

name

unit-planner

description

**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`。

Skill: unit-planner

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.

Read PIPELINE.lock.md (or ask to create it via pipeline-router).
Copy the pipeline’s units_template into the workspace as UNITS.csv if missing.
If UNITS.csv exists, only edit it to reflect:
- new scope (add rows)
- corrected dependencies
- clarified acceptance criteria
Ensure every unit has: unit_id, skill, outputs, acceptance, checkpoint, status, owner.
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 python scripts/pipeline.py kickoff|init to create PIPELINE.lock.md before generating units.

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