planning

To create an implementation plan from a feature spec, provide the specification document to the planning engine, which parses requirements and generates a structured plan with linked traceability checkpoints.

Generating an actionable plan produces a suite of artifacts including research.md, data-model.md, contracts, plan.md, and a YAML checkpoints file, all mapped to specific REQ-XXX IDs for traceability.

Traceability across discovery, design, and delivery is maintained by mapping each implementation plan item and artifact to extracted REQ-XXX IDs, ensuring validation gates and checkpoints track requirements throughout the product development workflow.

Yes, you can integrate custom guidelines and validation gates into the planning process, allowing the generated implementation plan and traceability checkpoints to align with specific architecture and product delivery standards.

The best way to automate phased delivery planning is to input a feature specification into the planning engine, which parses requirements and outputs a structured plan.md with YAML checkpoints for each delivery phase.

You need a feature specification containing identifiable requirements to generate a plan, as the planning engine relies on extracting REQ-XXX IDs to build traceability checkpoints and map the implementation artifacts.