writing-plans

Implementation plans break designs into concrete, executable tasks specifying exact file paths, code snippets, tests, and verification steps. This approach ensures engineers with zero codebase context can execute tasks reliably and rapidly.

The best way to break down engineering documentation is generating comprehensive task-level plans that include precise file modifications, code examples, required tests, and verification steps. This enables rapid execution with minimal context switching.

You can generate an implementation plan that includes exact file paths and tests by creating a feature-specific plan file. Save it under docs/plans using a date prefix and feature name, then follow the steps sequentially while committing changes.

Yes, this implementation planning approach explicitly targets engineers with zero codebase context. It provides exact file paths, code examples, and verification steps for each task, ensuring reliable implementation without prior project knowledge.

You should save generated implementation plans in a dedicated directory at docs/plans. The system uses a date prefix and feature name convention, creating reproducible execution files like docs/plans/YYYY-MM-DD-<feature-name>.md.