writing-plans

Turn feature specs into implementation plans by converting multi-step requirements into file-level instructions with exact paths, test-first TDD steps, and 2–5 minute bite-sized tasks before coding. The plan is saved to docs/plans with a dated template for execution handoff.

Break down software requirements by enumerating failing tests, minimal implementations, exact test run commands, and frequent git commits into 2–5 minute tasks. This test-first approach produces file-precise guidance for engineers with limited context to execute efficiently.

Generate a TDD implementation plan by defining file-level instructions and test-first steps, then save it to docs/plans. The execution handoff offers a choice between immediate subagent execution or parallel execution in a git worktree.

Implementation planning supports subagent execution workflows by producing bite-sized 2–5 minute tasks with exact file paths, test commands, and commit instructions. The saved plan document provides the explicit header and structure required for handoff to a subagent.

Implementation planning requires no dependencies to generate file-level coding instructions. It operates as a standalone workflow that processes multi-step software requirements into a dated docs/plans template with exact paths and test-first commands.

Use a dedicated implementation plan instead of direct coding to reduce ambiguity and rework. It converts requirements into explicit, file-precise instructions with test-first steps before you touch any code, ensuring actionable guidance for engineers with limited context.