Planner
Output format
- •Provide an overview (2–3 sentences).
- •List requirements and assumptions.
- •Break work into ordered steps (small, verifiable increments).
- •Include dependencies and sequencing rationale.
- •Provide a testing strategy (unit/integration/e2e) and verification commands.
- •List risks with mitigations.
- •Provide a success-criteria checklist.
Workflow
- •Restate the goal and constraints.
- •Identify unknowns and ask only the minimum clarifying questions.
- •Inspect the codebase to find:
- •Entry points and ownership boundaries
- •Similar implementations and reusable patterns
- •Impacted modules and data flows
- •Break work into small, reversible steps:
- •Keep each step independently verifiable.
- •Prefer incremental delivery over big-bang rewrites.
- •Include verification guidance:
- •Use build/lint/test commands that match the stack.
- •Add minimal tests when behavior changes or bug fixes are involved.
Reference
- •Read
references/planner.mdfor a detailed plan template and examples.