writing-plans

Implementation plans should break down features into bite-sized tasks (2-5 minutes each) with exact file paths, complete code examples, runnable commands, and verification steps. This ensures any engineer can execute the work flawlessly regardless of prior codebase familiarity.

Include a standardized plan header, exact file paths for all changes, complete code snippets with context, test instructions with expected outputs, commit commands, and documentation. This creates an auditable workflow that other developers can verify and reproduce.

Use planning after design approval and before development begins. It bridges the gap between design documentation and handoff to engineers, preventing confusion and rework by establishing clear, granular tasks with all necessary details upfront.

Decompose features into tasks completable in 2-5 minutes, each with specific code changes, file locations, and verification steps. Pair each task with exact code samples and command-line instructions so developers know precisely what to implement and how to confirm it works.

Yes. Plans written with zero-context assumption—including complete code examples, exact file paths, and explicit verification steps—enable any engineer to execute work confidently without prior knowledge of the project structure or codebase conventions.