writing-plans

To generate an implementation plan from a design concept, provide the design artifacts to produce a Plan Document with precise file paths, runnable code samples, and test outlines. This plan maps high-level concepts to engineer-ready file-level guidance for unfamiliar codebases.

The best way to break down software design into engineering tasks is to generate a plan that applies task-breakdown principles. This process maps design artifacts to concrete file paths, code examples, and test scaffolds, ensuring traceability and reducing context-switching for engineers.

An engineer-ready implementation plan handles verification by providing test scaffolds and verification steps within the document. It adheres to TDD principles, outlining specific test cases and integration points alongside the provided code samples.

Yes, you can use this planning approach for software projects requiring strict DRY and traceability principles. The generated Plan Document explicitly adheres to DRY and traceability, ensuring code examples and file-level guidance avoid redundancy and maintain design traceability.

Generated software implementation plans are stored as Plan Documents under the docs/plans directory. Each document includes sections, precise file paths, runnable code samples, and test outlines, and is saved with a date stamp for version tracking.

You need detailed file paths and code examples in your software implementation plan to reduce context-switching and speed up handoffs between teams. Precise file-level guidance and runnable samples provide engineers with exact implementation steps for unfamiliar codebases.