writing-plans

Task decomposition breaks complex features into bite-sized tasks with explicit file paths, concrete code examples, and testing steps. This approach ensures engineering teams can proceed without ambiguity by documenting every implementation detail upfront.

Subagent-driven development uses a two-stage review process that checks spec compliance before coding. It relies on precise implementation plans containing exact file paths and testing commands so subagents can execute bite-sized tasks effectively.

TDD-style implementation plans include clear criteria for completion, explicit testing steps, and concrete code examples. They decompose features into bite-sized tasks with exact file paths to support iterative test-driven development workflows.

Implementation plans are optimized for vector search by including concrete task structures, dependencies, and outcome-oriented prompts. This ensures specific file paths and testing commands are retrievable during subagent-driven development.

Document file paths and testing commands using artifact templates within an implementation plan. This specifies exact code snippets and testing commands, breaking work into bite-sized tasks with clear scope for comprehensive upfront documentation.

You need an implementation-level plan when starting complex work that requires comprehensive upfront design. It prevents ambiguity by ensuring every detail from file paths to tests is documented before development begins.