writing-plans

An implementation plan breaks down a feature design into atomic 2-5 minute tasks with exact file paths, code snippets, and verification commands. Start with your architecture and tech stack, then list each task with dependencies, edge cases, and commit messages so any engineer can execute it without ambiguity.

A complete plan contains goal, architecture, and tech stack as mandatory headers, followed by granular tasks specifying file locations, exact code examples, verification steps, required dependencies, edge cases, and documentation standards. This structure eliminates confusion and rework.

Yes. Implementation plans are designed for engineers with zero prior context. They provide step-by-step guidance with exact file paths and code snippets, making them ideal for onboarding and reducing ramp-up time on complex features.

Tasks should be atomic and completable in 2-5 minutes. Each task includes exact file paths, code snippets, verification commands, and commit messages. This granularity prevents ambiguity and enables parallel execution by multiple engineers.

Create an implementation plan after your design phase is complete. Once architecture is defined and technical decisions are locked, generate the plan to provide engineers with precise execution guidance for the implementation phase.

Vague instructions lead to confusion, rework, and delays, especially for new team members. Detailed plans with exact file paths, code examples, and verification steps eliminate ambiguity and ensure consistent, efficient implementation across the team.