generate-tasks

To convert a feature plan into TDD-ready task specifications, apply the generation process to PLAN-*.md files or direct briefs to draft a test plan, align with plan decisions, and capture edge cases as actionable task requirements.

Generating test plans from existing plan documents is best handled by embedding the resulting task specs directly into the same PLAN-*.md file, which preserves context, avoids document sprawl, and maintains clear handoffs for test-driven development.

Collaborative planning for task specs engages directly with the developer to extract requirements from a feature plan, identifies gaps and risks like ambiguities or dependencies, and drafts a comprehensive test plan to inform scope decisions.

Yes, you can use direct briefs instead of PLAN-*.md files to generate TDD task specs, allowing you to capture edge cases and constraints as actionable task requirements even without a pre-existing markdown plan document.

Embedding task specifications into the same plan document keeps the context intact and avoids file sprawl, ensuring that the test plan, plan decisions, and actionable task requirements remain together for clear implementation handoffs.

Limitations of generating TDD task specs include relying on the clarity of the initial feature plan, as the process highlights ambiguities, edge cases, and dependencies to inform scope, requiring developer collaboration to resolve identified gaps.