writing-plans

Implementation plans convert requirements into bite-sized, test-first tasks by decomposing work into 2–5 minute steps with exact file paths and explicit test commands. This approach ensures deterministic execution and reduces thrash before writing code.

Test-first task decomposition breaks engineering changes into small intervals: writing failing tests, verifying failure, implementing minimal code, re-running tests, and committing. It provides exact file paths assuming the engineer has near-zero codebase context.

Yes, this approach suits multi-step engineering changes in existing repositories where the implementer lacks domain or codebase context. It provides exact file paths, complete code snippets, and guidance on documentation to check for implementation details.

A file-specific implementation plan enforces a consistent header and step structure, specifying which files to create or modify, which tests to add, and exact commands with expected FAIL or PASS outcomes. The plan is saved to a dated docs/plans path.

Bite-sized test-first tasks are not ideal for simple, single-step modifications that do not require explicit test commands or detailed codebase context. They are best suited for complex, multi-step engineering changes needing strict decomposition.