gds-sprint-planning

To generate sprint-status.yaml from epic markdown files, run the sprint planning workflow to parse story definitions, detect filesystem statuses, and consolidate them into a structured YAML file. It preserves existing statuses while applying defaults for new entries.

Automatic sprint planning detects story statuses by scanning the filesystem for changes and matching them against your epic markdown definitions, preserving existing statuses in the sprint-status.yaml when present.

Yes, you can preserve existing story statuses when regenerating a sprint plan; the workflow detects current statuses from the filesystem and retains them in the sprint-status.yaml unless explicitly updated.

Yes, sprint planning works specifically with projects that maintain epics and stories in markdown files, parsing those definitions to build a complete sprint inventory and validate the structured output.

The best way to track backlog progress using YAML is converting epic markdowns into a consolidated sprint-status.yaml, enabling automatic status tracking, validation, and reporting for your sprint planning process.