| name | workflow-plan |
| description | Break an approved design into atomic implementation tasks — creates dependency-ordered task specs ready for parallel agent execution. |
Workflow: Plan Phase
Decompose the design into atomic, narrowly-scoped implementation tasks.
Workspace Discovery
The user invokes this as /workflow-plan {slug}.
- If
$ARGUMENTS is empty, scan .workflow/*/ directories and list available workspaces — ask which one
- Scan
.workflow/*/ for a folder matching the slug $ARGUMENTS
- Read
STATUS.yaml — phase must be design-complete or discussion-complete:
design-complete → normal flow, read DESIGN.mddiscussion-complete → design was skipped, derive plan from DISCUSSION.md directly- Otherwise → tell the user which phase to complete first
- If
design-complete: verify DESIGN.md exists. If discussion-complete: verify DISCUSSION.md exists (DESIGN.md is optional).
- Update STATUS.yaml:
phase: plan, updated: {ISO timestamp}
Skills Integration
Skill tagging is mandatory
Every task MUST include an ## Applicable Skills section listing which project skills the task-implementer agent should consult. This is the primary mechanism for ensuring agents follow project patterns.
Available skills for tagging
Project skills (from .claude/skills/ — agent reads these files directly):
