gds-sprint-status

Summarizes sprint status from sprint-status.yaml and recommends the next workflow action.

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill gds-sprint-status-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-sprint-status
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/gds-sprint-status
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill gds-sprint-status-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agile teams lose track of where stories and epics stand when sprint data lives in a raw YAML file. This Skill parses sprint-status.yaml, counts story and epic statuses, surfaces risks like stale data or orphaned stories, and recommends the next workflow action. ## Core Features & Use Cases - Sprint Summarization: Parses sprint-status.yaml to count stories and epics by status (backlog, ready-for-dev, in-progress, review, done) and displays a formatted summary. - Risk Detection: Flags stale status files, orphaned stories, in-progress epics without stories, and unrecognized status values with guided correction. - Next-Action Recommendation: Selects the next workflow (dev-story, code-review, create-story, or retrospective) based on priority rules, with interactive, data, and validate execution modes. - Use Case: A developer asks "check sprint status" and immediately sees story counts, risks, and a recommendation to run code review on the story currently in review. ## Quick Start Ask the assistant to check the sprint status and show the recommended next workflow for the current project.

Frequently Asked Questions about gds-sprint-status

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

FAQPage Schema
How do I check sprint status in a BMAD workflow?

Ask the assistant to check or show sprint status. The Skill reads sprint-status.yaml from the implementation artifacts directory, counts story and epic statuses, and displays a summary with risks and a recommended next workflow.

What file does the sprint status workflow read?

It reads sprint-status.yaml located in the implementation artifacts directory configured in the project config. If the file is missing, it instructs you to run the sprint-planning workflow first to generate it.

What risks does sprint status detection surface?

It flags stories in review needing code review, stale status files older than seven days, orphaned stories without a matching epic, in-progress epics with no stories, and unrecognized status values with an option to correct them.

How does the workflow decide the next recommended action?

It follows a priority order: in-progress stories get dev-story, review stories get code-review, ready-for-dev stories get dev-story, backlog stories get create-story, and optional retrospectives get the retrospective workflow.

Can sprint status be validated without running the full summary?

Yes, validate mode checks that sprint-status.yaml exists, contains required metadata fields, has a non-empty development_status section, and uses only recognized status values, returning structured is_valid and error outputs.