writing-plans

To generate implementation plans, this skill produces detailed, actionable documents containing exact file locations, required code changes, concrete samples, and verification steps. It enforces TDD, DRY principles, frequent commits, and saves the plan to docs/plans/YYYY-MM-DD-<feature-name>.md.

The best way to create an engineering plan for developers lacking context is generating bite-sized, deterministic tasks with exact file paths, code snippets, and testing steps. This ensures all necessary implementation details are captured in a single, reproducible markdown document.

Writing an implementation plan that enforces TDD and DRY principles involves generating step-by-step tasks that include required code changes, concrete examples, and verification testing steps. The plan also references documentation and commit histories to ensure project traceability.

Yes, this implementation planning skill works for teams that have completed design but need execution steps. It converts design into executable work by producing comprehensive plans detailing file paths, code snippets, tests, and documentation for engineers with minimal context.

To include verification and acceptance criteria when documenting code implementation plans, the skill generates verification-driven tasks. Each task section contains step-by-step actions, required testing steps, and acceptance criteria to verify the implementation across the repository.

Your software implementation plan needs exact file paths and frequent commit references to ensure deterministic planning and traceability. These elements allow engineers with minimal context to accurately implement, test, and document features while maintaining DRY principles across the repository.