gds-sprint-status

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

1|Updated Sep 18, 2026
One-click install
npx skills add https://github.com/PastaSus/egg-defender --skill gds-sprint-status-pastasus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-sprint-status
Source: https://github.com/PastaSus/egg-defender/tree/main/.agents/skills/gds-sprint-status
Command: npx skills add https://github.com/PastaSus/egg-defender --skill gds-sprint-status-pastasus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agile teams lose track of where stories and epics stand across a sprint. This Skill reads the sprint-status.yaml tracking file, aggregates story, epic, and retrospective counts, surfaces risks like stale data or orphaned stories, and recommends the next workflow to run. ## Core Features & Use Cases - Sprint Aggregation: Parses sprint-status.yaml to count stories and epics by status (backlog, ready-for-dev, in-progress, review, done) and validates all status values against known states. - Risk Detection: Flags stale status files older than 7 days, orphaned stories without a matching epic, in-progress epics with no stories, and unknown status values with interactive correction. - Next-Action Recommendation: Selects the next workflow (dev-story, code-review, create-story, or retrospective) with the target story and agent role, and supports data and validate modes for programmatic consumption. - Use Case: A developer starts the day by asking for sprint status, sees that one story is in review and two are ready for development, and immediately launches the recommended code-review workflow. ## Quick Start Ask the assistant to check 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 for my project?

Ask the assistant to check or show sprint status. The Skill reads the sprint-status.yaml file from your implementation artifacts directory, summarizes story and epic counts by status, and displays risks plus a recommended next workflow.

What file does the sprint status summary use?

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

What risks does sprint status tracking detect?

It detects stale status files older than 7 days, orphaned stories without a matching epic, in-progress epics with no stories, stories stuck in review, and unrecognized status values, prompting corrections interactively.

Can sprint status output be consumed by other workflows?

Yes. Data mode returns structured outputs like next_workflow_id, next_story_id, next_agent, status counts, and risks for callers. Validate mode checks file existence, required metadata fields, and status value validity, returning is_valid with errors and suggestions.

What happens when sprint-status.yaml has invalid status values?

The Skill lists each unrecognized entry with valid options for stories, epics, and retrospectives, then asks for corrections. Provided fixes are written back to sprint-status.yaml and the file is re-parsed before continuing.