writing-plans

Implementation plans break down features into bite-sized tasks (2-5 minutes each) with exact file paths, complete code examples, and verification steps. This approach works when specs are incomplete or you're handing off work to engineers unfamiliar with the codebase, ensuring they know precisely what to build and how to verify it.

TDD-aligned planning starts with failing tests, then specifies the exact code changes needed to pass them. Each task includes the test to write first, implementation code, file locations, and verification commands, creating a clear sequence from red to green that guides development workflow.

Yes. Comprehensive plans designed for zero-context documentation include exact file paths, runnable code samples, testing instructions, and version-control commands. Engineers can execute tasks without needing to understand the broader system design or make architectural decisions.

Comprehensive planning delivers a frontmatter header, per-task steps organized as failing-test-to-pass sequences, exact file paths, code samples, testing instructions, and version-control commands. This structured format ensures nothing is missed and each task remains independently verifiable.

Create a plan when handing off complex features, when engineers lack codebase context, when specs are vague or incomplete, or when you need to prevent confusion and rework. Plans are especially valuable for project management and development workflow coordination across teams.