skills.rest
ArchaonHW
ArchaonHWCOMMUNITY
Explore all skills by this author →
GitHub

gds-sprint-status

Summarizes sprint-status.yaml into story counts, risks, and next workflow recommendations.

Updated Mar 14, 2026
Search Tags:#workflow#agile#yaml#story tracking#bmad#sprint status#risk detection
One-click install
npx skills add https://github.com/ArchaonHW/MingGoRTS --skill gds-sprint-status-archaonhw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gds-sprint-status
Source: https://github.com/ArchaonHW/MingGoRTS/tree/main/.agents/skills/gds-sprint-status
Command: npx skills add https://github.com/ArchaonHW/MingGoRTS --skill gds-sprint-status-archaonhw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agile teams lose track of where their sprint stands when story and epic statuses live in a raw YAML file. This Skill reads sprint-status.yaml, aggregates story and epic counts, surfaces risks like stale data or orphaned stories, and recommends the next workflow action. ## Core Features & Use Cases - Sprint Aggregation: Parses sprint-status.yaml and counts stories and epics by status (backlog, ready-for-dev, in-progress, review, done), including legacy status mapping. - Risk Detection: Flags stale status files, orphaned stories, in-progress epics without stories, and unrecognized status values with interactive 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 that 3 stories are in review, the status file is 10 days old, and the recommended next step is running code-review on story 2-1. ## Quick Start Ask the assistant to check the sprint status and show any risks plus the recommended next workflow.

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 from a YAML file?▼

Run the sprint status workflow, which reads sprint-status.yaml from the implementation artifacts directory, parses story and epic statuses, and displays counts by category along with risks and a recommended next action.

What statuses are valid in sprint-status.yaml?▼

Stories support backlog, ready-for-dev, in-progress, review, and done, with legacy drafted mapped to ready-for-dev. Epics support backlog, in-progress, and done, with legacy contexted mapped to in-progress. Retrospectives support optional and done.

What happens if sprint-status.yaml is missing?▼

The workflow reports that the file was not found and instructs you to run the sprint-planning workflow to generate it before rerunning sprint status. In validate mode it returns is_valid false with a suggestion to run sprint-planning.

How does the skill detect sprint risks?▼

It flags stories stuck in review, status files older than 7 days, orphaned stories without a matching epic, in-progress epics with no stories, and sprints where all epics remain in backlog with nothing ready for development.

Can sprint status output be consumed by other workflows?▼

Yes, data mode returns structured outputs including next_workflow_id, next_story_id, next_agent, status counts, and risks, so calling workflows can consume the recommendation programmatically without interactive prompts.

Related Skills

Explore More Product & Management Skills→
ImaginerLabsImaginerLabs

bmad-sprint-planning

Generate sprint-status.yaml from epic and story markdown files.

Official
Advanced
shaahyshaahy

bmad-sprint-status

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

Community
Intermediate
tuanldastuanldas

team-coordination

Define Scrum team roles, escalation paths, and decision governance.

Community
Advanced
devopstalesdevopstales
1

skillgrid-issue-creation

Create and link external tracker issues for Skillgrid work items.

Community
Advanced