writing-plans

Implementation plans translate designs into actionable tasks by specifying exact file paths, complete code examples, and verification steps. Structure your plan with clear headers for each phase, include ready-to-integrate code snippets, and list concrete commands to verify correctness—enabling engineers to execute without additional context.

A comprehensive implementation plan includes file-level tasks with precise paths, inline code examples ready for integration, verification commands to confirm correctness, and structured headers organizing work logically. This format lets engineers with minimal codebase knowledge implement confidently without guessing about file locations or integration points.

Yes. Implementation plans are designed for engineers with zero codebase context. By specifying exact file paths, complete code blocks, and step-by-step verification commands, plans eliminate the need for domain knowledge and enable confident execution of design-complete projects.

Implementation plans include explicit verification steps—concrete commands and checks that confirm your code works as intended. Run these commands after completing each task to catch errors early and ensure reproducible, version-controlled execution aligned with the original design.

A design document describes what to build and why; an implementation plan translates that design into exact file paths, complete code examples, and verification commands. Plans provide the concrete, actionable tasks engineers need to execute immediately without interpretation or guesswork.

Yes. Implementation plans apply DRY (don't repeat yourself) and YAGNI (you aren't gonna need it) guidance to avoid redundant code and unnecessary complexity. This keeps plans lean, reproducible, and focused on exactly what the design requires—nothing more.