writing-plans

To turn software requirements into an implementation plan, you map affected files, interfaces, and tests, then decompose the work into bite-sized, test-driven steps with exact paths, validation commands, and commit points.

Codebase decomposition for task planning maps the specific files, responsibilities, interfaces, and tests affected by a feature before implementation begins, ensuring engineers have clear boundaries and concrete execution details.

Break down multi-step engineering tasks by planning independent, bite-sized actions that specify exact file paths, expected results, test-first guidance, and commit points to ensure another engineer can execute the work with minimal context.

Yes, you can generate a plan for another engineer to execute by ensuring the output is placeholder-free, covers specification requirements, checks type and interface consistency, and provides explicit execution handoff options.

The best way to validate specification coverage is to run a plan quality review that checks for placeholder-free instructions, type and interface consistency, and explicit execution handoff options before passing the plan to implementation.

You should not use a structured implementation plan for single-step tasks lacking explicit boundaries, or when a feature requires no codebase decomposition, test planning, or file-level changes.