gds-sprint-planning

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

The workflow checks whether a story markdown file exists in the story location for each story key. If found, the story status upgrades to at least ready-for-dev, but existing more advanced statuses like in-progress or done are never downgraded.

Yes. If no whole epic document is found, the workflow looks for a sharded epics directory with an index.md, reads every listed epic section file, and combines them into a complete inventory before generating statuses.

Epics flow from backlog to in-progress to done. Stories flow from backlog to ready-for-dev to in-progress to review to done. Retrospectives toggle between optional and done.

The preservation rule prevents downgrades, so a story already marked done or in-progress keeps its status. Also verify the story file name matches the kebab-case key format, such as 1-1-user-authentication.md in the stories folder.