planner-workflow
Installation
SKILL.md
Planner Phase Workflow
You have been assigned a planning task to create a full plan with phases for a feature. Your spawn prompt contains the feature description, requirements, and plan folder path. This skill teaches you how to handle the entire planning process end-to-end.
Why This Workflow Exists
The user experienced planners that guessed at patterns, skipped template sections, and produced phases with generic code blocks. Each step below prevents a specific failure:
| Step | Prevents |
|---|---|
| Read templates completely | Missing required sections, rework during review |
| Create task list | Lost progress after context compact, skipped phases |
| Read codebase references | Code blocks that don't match real project patterns |
| Checkpoint 1 (plan summary) | Building 20 phases on wrong assumptions — hours wasted |
| Self-validate each phase | Placeholder content and missing TDD discovered late in review |
Step 1: Read Templates
The user created these templates specifically so phases don't miss required sections. Skipping template reading causes incomplete phases that require rework during implementation.