writing-plans

Converting a feature specification into an implementation plan requires decomposing multi-step work into bite-sized, test-driven actions with exact file touchpoints. This produces a buildable plan with minimal ambiguity for engineers to execute.

Task decomposition in TDD planning breaks multi-step development work into bite-sized, test-driven actions with clear component boundaries. It specifies exact create, modify, and test paths so implementation follows a predetermined execution sequence.

Creating an engineering handoff plan involves converting feature specs into a dated document specifying exact create, modify, and test paths. The plan must contain bite-sized TDD tasks, exact commands, and code blocks while prohibiting TODO-style gaps.

You need a structured feature specification to generate a TDD implementation plan, as the process requires upfront architecture and testing strategy definition. The input spec provides the context necessary to determine execution sequence before changing code.

Implementation plans can be executed inline or handed off to subagents task-by-task. The plan-ready format supports both direct execution and sequential delegation by producing discrete, engineer-executable steps with clear component boundaries.

To avoid TODO placeholders and gaps in engineering documentation, enforce anti-placeholder guardrails that prohibit TBD-style gaps. Plans must require concrete code blocks and exact testing commands instead of leaving undefined implementation steps.