gds-sprint-planning

To generate a sprint plan from markdown epic files, run a workflow that reads epic and story structures to produce a complete sprint-status.yaml. It detects current progress using filesystem evidence and preserves higher statuses when present.

Yes, you can track sprint progress automatically by generating a sprint-status.yaml file. This machine-readable file documents story statuses by reading epic markdown definitions and detecting existing filesystem evidence.

Sprint planning automation detects story statuses by examining filesystem evidence. It reads epic and story markdown structures, identifies existing progress markers, and preserves the highest statuses already present in the project.

Sprint planning workflow supports both whole-epic markdown documents and optional sharded epic indexes. This flexible approach allows it to read epic and story structures regardless of how your project files are organized.

The automated sprint tracker outputs a machine-readable sprint-status.yaml file. It includes a detailed workflow header and documents the detected statuses of all epics and stories from your markdown project files.

No external dependencies are required to generate a sprint-status.yaml from epics. The workflow operates directly on your existing markdown epic and story files, requiring no additional components to parse and track progress.