plan

To break down a specification document into testable user stories, use automated planning to generate a plan.md file alongside JSON story files with acceptance criteria. This ensures comprehensive feature coverage and prepares tasks for the build phase.

Creating an implementation plan with acceptance criteria involves parsing a spec file to output a plan.md document and structured JSON stories. These outputs define the technical approach and step-by-step verification tests required for feature completion.

Yes, you can generate JSON test files automatically from feature specifications. The planning process creates step-by-step tests in JSON format to verify story completion, directly integrating the generated tests into your validation and build workflows.

Test driven development planning integrates seamlessly with build and validation workflows. The generated plan.md and JSON story files connect directly with validation, review, and build processes to maintain a complete development lifecycle.

The best way to manage task dependencies when planning new features is to generate structured JSON stories that explicitly map requirements and dependencies. This ensures all task constraints are documented and validated before the build phase begins.