jagreehal Implementation Planning
Critical rules
NO IMPLEMENTATION WITHOUT A PLAN FIRSTfor multi-step work.- Assume the executor has zero codebase context: exact paths, complete code, exact commands with expected output.
- Every task: test → fail → implement → pass → commit. One action per step (~2-5 min).
- Never vague steps, skipped verification, bundled multi-file "and" steps, or assumed knowledge.
- Save to
docs/plans/YYYY-MM-DD-<feature-name>.md. Preferfn(args, deps)and Result types. - Before drafting task bodies, read references/plan-structure.md.
Workflow
- Confirm design is approved (
design-exploration) when requirements were ambiguous. - Write header: goal, architecture, tech stack.
- Break into bite-sized TDD tasks with exact files and copy-pasteable code (see plan-structure).
- Quality-check: one action, exact paths, complete code, expected command output, clear TDD, commit messages.
- Save under
docs/plans/and offer execution handoff (often insidegit-worktrees).
Resources
- references/plan-structure.md — header/task templates and handoff. Read before writing the plan.
Validation
- Header has goal, architecture, tech stack
- Every task follows test → fail → implement → pass → commit
- Exact paths; commands state expected output; no bundled steps
- Plan saved to
docs/plans/and ready for handoff
Constraints
- Skip for single-file/single-function obvious scope.
- Related:
design-exploration,tdd-workflow,git-worktrees,parallel-agent-dispatch,create-tasks.