gds-sprint-planning

Run the sprint planning workflow, which scans files matching *epic*.md in your planning artifacts directory, extracts all epics and stories, and writes a complete sprint-status.yaml with detected statuses to your implementation artifacts folder.

The workflow checks whether a story markdown file exists in the stories location; if found, the story status upgrades to at least ready-for-dev. Existing more advanced statuses like in-progress or done are always preserved and never downgraded.

Yes. If no whole epic document exists, it looks for an epics/index.md, reads the index, then loads every listed epic section file to build complete coverage. Whole documents take priority when both forms exist.

Epics flow backlog to in-progress to done. Stories flow backlog, ready-for-dev, in-progress, review, then done. Retrospectives toggle between optional and done. All transitions are documented in the generated YAML header.

Missing stories usually mean the epic files use nonstandard headers. The workflow expects patterns like '### Story 1.1: Title' to convert into kebab-case keys such as 1-1-title, so verify your epic markdown follows that heading format.