project-planning

To automate project plan generation, this Skill validates your requirement spec inputs and applies template-driven logic to produce a structured project-plan.md file. It coordinates the planning phase end-to-end, ensuring the output includes required metadata and review-ready structure.

Story mapping influences release planning by using an optional story-map.md file to guide feature grouping and release slices. The Skill coordinates this optional story mapping input to shape the structure and sequencing of the final project plan.

Yes, you can use a template-driven approach to structure project specifications. The Skill checks that planning templates exist and uses them to generate the final project-plan.md, ensuring the output adheres to the required structural and metadata standards.

Yes, you need a requirement spec before starting the project planning phase. The Skill validates preconditions from previous phases, verifying that the current requirement spec exists before generating the project plan.

Without story mapping, the project plan generation proceeds without the optional story-map.md file. This means feature grouping and release slices are generated solely from the requirement spec and template, lacking the refined grouping guidance that story mapping provides.

The best way to orchestrate the planning phase is to validate existing requirement specs, check for available templates, and delegate plan generation to produce a review-ready project-plan.md. This Skill automates that entire workflow, including status guidance for Ready or DOING.