writing-plans

Implementation plans break down finalized designs into bite-sized, actionable tasks with explicit file paths, complete code examples, and verification steps. Start with your design document, then structure each task as a 2–5 minute unit with test-driven development guidance and commit instructions for smooth handoff to engineers unfamiliar with the codebase.

Task breakdowns require exact file locations, full code snippets, precise verification commands, and test-first instructions. Each step should be independently executable, reference relevant documentation, and include commit-ready guidance so engineers can verify work at each stage without domain knowledge or codebase context.

Yes. Implementation plans assume zero-context knowledge and minimal domain familiarity, making them ideal for handing off complex features to engineers new to the project. Complete code examples and explicit file paths eliminate ambiguity and reduce rework.

Test-driven development and commit instructions are embedded directly into each task step. Engineers write tests first, verify functionality using provided commands, then commit at natural boundaries, creating a clear audit trail and reducing integration friction.

Decompose the feature into small, testable units ordered by dependency. Each unit gets its own task with code samples, test assertions, and commit scope. This approach enables parallel work, frequent verification, and incremental integration without blocking other engineers.