gds-sprint-planning

To generate a sprint status YAML from epic markdown files, trigger the sprint planning workflow to automatically discover epics and stories, validate consistency, and produce a consolidated sprint-status.yaml with metadata.

The best way to track epic and story statuses for sprint planning is generating a consolidated status map that aligns epic definitions with actionable development work, keeping planning artifacts synchronized in a single YAML file.

Yes, you can use this workflow to validate consistency between epic definitions and the generated sprint-status.yaml, applying safeguards that preserve higher statuses during the automated status mapping process.

Yes, you need existing epic markdown files as planning artifacts to automate sprint status generation, because the workflow discovers epics and stories directly from these files to build the status map.

The sprint planning automation handles status mapping for retrospectives by applying validation safeguards to preserve higher statuses, consolidating retrospective statuses alongside epics and stories into the final YAML output.