skills.rest
skyoxu
skyoxuCOMMUNITY
Explore all skills by this author →
GitHub

gds-sprint-status

Summarizes sprint statuses and detects risks from sprint-status.yaml files.

Updated Nov 6, 2025
Search Tags:#workflow#sprint#epic#risk#dev-story#sprint-status
One-click install
npx skills add https://github.com/skyoxu/godotgame --skill gds-sprint-status-skyoxu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gds-sprint-status
Source: https://github.com/skyoxu/godotgame/tree/main/.agents/skills/gds-sprint-status
Command: npx skills add https://github.com/skyoxu/godotgame --skill gds-sprint-status-skyoxu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to summarize sprint status, surface risks, and surface recommended actions for the team.

Core Features & Use Cases

  • Auto-loads sprint_status_file from project context and parses the development_status section (epics, stories, retrospectives) to present a consolidated view.
  • Detects risks such as orphaned stories, stale last_updated timestamps, in-progress epics with no associated stories, and potential blockers, then suggests concrete next steps.
  • Supports an interactive display of status and recommended workflows, enabling quick decisions for planning and execution.

Quick Start

Summarize sprint status and surface risks with one command to generate a prioritized action plan.

Frequently Asked Questions about gds-sprint-status

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

FAQPage Schema
How do I summarize sprint status and identify risks for my development epics?▼

To summarize sprint status, the skill parses a sprint-status.yaml file to detect development risks like orphaned stories or stale epics, generating a consolidated view and recommended next steps for team alignment.

What is the best way to prepare for a sprint retrospective using dev-story data?▼

Preparing for a sprint retrospective involves parsing development_status data to surface potential blockers and stale timestamps, generating recommended workflows to guide actionable team discussions.

Do I need a specific file format to track sprint status and development workflows?▼

Yes, you need a sprint-status.yaml file containing a development_status section with epics, stories, and retrospectives to validate statuses and generate recommended next steps.

How does sprint status validation handle in-progress epics with no associated stories?▼

Sprint status validation detects in-progress epics with no associated stories as a risk, flagging the orphaned state and suggesting concrete next steps to resolve the workflow gap.

Can I use this sprint status summary for daily standups across different project contexts?▼

Yes, the sprint status summary applies to daily standups across project contexts by interactively displaying parsed development_status data and prioritized action plans for quick execution decisions.

Related Skills

Explore More Software Engineering Skills→
skyoxuskyoxu

gds-sprint-planning

Parse epic markdown files to generate and validate sprint-status.yaml.

Community
Advanced
GenEducationGenEducation

bmad-sprint-status

Summarizes sprint progress and flags delivery risks from sprint status records.

Official
Advanced
AhmedKaram50AhmedKaram50

bmad-sprint-planning

Generate sprint-status.yaml from epic markdown files with status tracking.

Community
Intermediate
petrkohutpetrkohut

bmad-sprint-status

Parse YAML sprint status files to aggregate progress and risks.

Community
Advanced