creating-plans

Create comprehensive implementation plans by specifying exact file paths, code samples, testing steps, and verification commands. The plan is saved as a markdown document with sections for summary, full task breakdown, to-do checklist, code blocks, integration points, and local CI commands—enabling engineers with zero codebase context to execute end-to-end.

An implementation plan must include file path references, code examples, usage patterns, integration points, testing procedures, verification steps, and CI commands. It follows DRY and YAGNI principles, focusing on minimal essential tasks while providing exact instructions for each step.

Structure the plan with a brief summary, detailed task breakdown organized by file and module, exact code blocks ready to use, clear file paths, step-by-step to-do checklist, and verification commands. This eliminates ambiguity and allows developers to move directly from reading to implementation.

Yes, implementation plans span the full repository scope when needed. They map dependencies between files, specify integration points, include relevant docs references, and outline testing across all affected modules—providing task-scoped work that covers the complete feature end-to-end.

Include executable code blocks with realistic examples, exact file paths where code belongs, clear testing procedures with commands for local CI, and verification steps that confirm each component works. This ensures the plan is immediately actionable without requiring interpretation.