writing-implementation-plans

Implementation plans for engineers with zero codebase context are generated by providing exact file paths, code examples, and verification steps. The process breaks down tasks into bite-sized steps, verifying the current codebase state and researching external dependencies before each phase.

Phase-by-phase development plans ensure all acceptance criteria are met by implementing and testing each phase sequentially. This approach uses task and subcomponent markers for efficient parsing, verifying infrastructure and functionality tasks with distinct methods to guarantee coverage.

Infrastructure versus functionality tasks are verified using distinct, specialized verification methods tailored to each type. The implementation process differentiates these task categories to ensure proper testing and validation of both foundational infrastructure and feature functionality.

Researching external dependencies before writing implementation tasks ensures the plan accurately accounts for library behavior and integration requirements. Verifying these external components beforehand prevents architectural conflicts and ensures the generated file paths and code examples remain accurate.

Detailed implementation plans are explicitly designed for feature development without prior domain knowledge. By verifying the current codebase state and providing exact code examples, the generated plans bridge the context gap for engineers unfamiliar with the project architecture.