gds-sprint-status

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

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill gds-sprint-status-watchthelight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-sprint-status
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/gds-sprint-status
Command: npx skills add https://github.com/watchthelight/shatterfish --skill gds-sprint-status-watchthelight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agile teams tracking epics and stories in a sprint-status.yaml file lack a quick way to see overall progress, detect stale or inconsistent data, and decide which workflow to run next. This Skill parses the status file, validates every status value, surfaces risks, and recommends the next action. ## Core Features & Use Cases - Sprint Summary: Counts stories and epics by status (backlog, ready-for-dev, in-progress, review, done) and displays a formatted dashboard. - Risk Detection: Flags stale status files, orphaned stories, in-progress epics without stories, and unrecognized status values with interactive correction. - Next-Action Recommendation: Prioritizes the next workflow (dev-story, code-review, create-story, or retrospective) based on current statuses. - Use Case: A developer returning to a project asks for sprint status and immediately sees that two stories are in review, the file is 10 days stale, and the recommended next step is running code-review on story 2-1. ## Quick Start Ask the assistant to check sprint status and show the current sprint summary with risks and 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 your implementation artifacts directory, parses the development_status map, and displays story and epic counts by status along with risks and a next-step recommendation.

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 exits with an error message directing you to run the sprint-planning workflow first to generate the file. In validate mode it returns is_valid false with a suggestion to run sprint-planning.

How does the skill decide which workflow to recommend next?

It follows a priority order: in-progress stories trigger dev-story, review stories trigger code-review, ready-for-dev stories trigger dev-story, backlog stories trigger create-story, and optional retrospectives trigger retrospective. If everything is done, it congratulates you.

Can the skill fix invalid status values automatically?

It detects unrecognized statuses and prompts you to supply corrections interactively, then updates sprint-status.yaml and re-parses it. You can also skip corrections and continue with the summary.