skills.rest
HordRicJr
HordRicJrCOMMUNITY
Explore all skills by this author →
GitHub

gds-sprint-planning

Generates sprint-status.yaml tracking files by parsing epic and story markdown documents.

6|Updated Aug 29, 2026
Search Tags:#workflow#epics#agile#yaml#sprint planning#user stories#status tracking
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill gds-sprint-planning-hordricjr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gds-sprint-planning
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/gds-sprint-planning
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill gds-sprint-planning-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agile teams lose track of which epics and stories are in backlog, in progress, or done when status lives only in scattered planning documents. This Skill scans epic markdown files and produces a single structured sprint-status.yaml that reflects the real state of development work. ## Core Features & Use Cases - Epic and Story Parsing: Reads whole or sharded epic markdown files (epics.md, epic-1.md, etc.) and extracts every epic, story, and retrospective entry. - Intelligent Status Detection: Upgrades story status to ready-for-dev when a matching story file exists, and never downgrades existing advanced statuses. - Structured YAML Output: Generates a validated sprint-status.yaml with documented status state machines (backlog, ready-for-dev, in-progress, review, done). - Use Case: After writing your product epics, ask the agent to run sprint planning and receive a complete tracking file that developers and agents update as work progresses. ## Quick Start Ask the agent to run sprint planning and generate the sprint status file from your epic documents.

Frequently Asked Questions about gds-sprint-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a sprint status file from epic documents?▼

Run the sprint planning workflow and it scans all files matching the epic pattern in your planning artifacts folder. It extracts every epic and story, detects current statuses, and writes a complete sprint-status.yaml to your implementation artifacts directory.

How does sprint status detection work for stories?▼

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

Can it handle sharded epic files split across multiple documents?▼

Yes. If no whole epics.md file is found, it looks for a sharded structure with an index.md and reads every epic section file listed there. If both whole and sharded versions exist, the whole document takes priority.

What statuses can epics and stories have in sprint-status.yaml?▼

Epics move through backlog, in-progress, and done. Stories follow backlog, ready-for-dev, in-progress, review, and done. Retrospective entries toggle between optional and done.

Why is my story status not updating in sprint-status.yaml?▼

The workflow preserves any existing status that is more advanced than the detected one, so a done story will not revert to ready-for-dev. Verify the story file name matches the kebab-case key format like 1-1-user-authentication.md.

Related Skills

Explore More Software Engineering Skills→
jgabriellimajgabriellima

gds-sprint-planning

Generates sprint-status.yaml tracking files by parsing epic and story markdown documents.

Community
Intermediate
hanzlahabibhanzlahabib
2

rcode-create-story

Create dev-ready story files with BDD acceptance criteria from epic and architecture inputs.

Community
Advanced
skyoxuskyoxu

bmad-sprint-planning

Parse epic Markdown files and generate a deterministic sprint-status.yaml.

Community
Advanced
webrix-aiwebrix-ai
1

issue-sync

Synchronize issues and tasks across GitHub, Jira, and Linear.

Official
Advanced