generate-tasks

To turn a feature plan into TDD task specifications, you summarize the plan context, draft a detailed test plan covering edge cases, and append task specs directly into the feature plan document before coding begins.

Generating a test plan from a feature brief involves digging into requirements and error expectations to draft explicit test scenarios, ensuring developers have clear scope boundaries before implementation starts.

Keeping task specs and test plans in the same document requires appending the TDD tasks directly inside the PLAN-*.md file, allowing the TDD agent to see requirements and implementation steps without chasing multiple files.

Yes, you can break down a lightweight brief without writing implementation code by summarizing the plan context and drafting a detailed test plan with embedded task specs that satisfy the requirement to collaborate with the developer.

You need to generate TDD task specs from a feature plan when a developer has a PLAN-*.md file or lightweight brief and requires embedded test scenarios and scope boundaries to prevent writing tests from becoming guesswork.