Plan

To turn feature specifications into implementation plans, provide a spec in the specs/ directory and run the plan command. The tool analyzes dependencies and generates a phased execution strategy saved to specs/[YYYYMMDD-slug]/plan.md.

Yes, a loaded foundation is a strict prerequisite for generating an implementation plan. Foundation-aware template selection ensures the plan aligns with your project context before outputting the final plan document.

Foundation-aware template selection automatically aligns generated implementation plans with your project's existing architecture and context. It ensures the resulting phased execution strategy matches your established foundation.

To generate a phased execution strategy from a feature spec, place the specification in specs/ and execute the plan command. The tool outputs a ready-to-implement plan with risk assessment, deliverables, and phasing to specs/[YYYYMMDD-slug]/plan.md.

The best way to structure implementation plans is through automated dependency analysis and phasing. This tool converts specs into clear deliverables and risk assessments for each execution stage, saving a structured plan.md file.

No, a feature specification located in specs/ is a mandatory prerequisite. The plan generation process enforces this requirement to ensure the resulting implementation plan is accurately derived from concrete specifications.