writing-plans

Implementation plans must specify exact file paths, complete code samples, verification commands, and expected outputs so engineers with zero codebase context can execute without guessing. Break work into atomic 2-5 minute tasks with prerequisites, commit instructions, and failure recovery steps.

A complete implementation plan covers goal and architecture, tech stack, exact file paths, full code examples, step-by-step commands with expected output, verification steps, failure recovery procedures, and review checkpoints—enabling engineers to work independently without domain knowledge.

Decompose implementation into atomic steps lasting 2-5 minutes each, such as writing a failing test, running it, writing minimal implementation, and committing. Each step includes files to touch, prerequisites, exact code, commands, expected results, and next steps.

Generate implementation plans during design handoffs, PRD/TRD validation, and pre-development planning phases to transform high-level design concepts into executable instructions before engineers begin coding.

Yes. Comprehensive plans with explicit file paths, complete code, and verification commands eliminate assumptions, reduce errors, and accelerate onboarding by providing step-by-step guidance independent of prior codebase familiarity.