sprint-status

Assess sprint progress from plans and story status files.

47|12|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill sprint-status-nuoyanruoshui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-status
Source: https://github.com/nuoyanruoshui/GodotGameFramework/tree/main/Godot/.claude/skills/sprint-status
Command: npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill sprint-status-nuoyanruoshui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides fast, evidence-based sprint visibility without manually reviewing plans, story files, dates, or status markers.

Core Features & Use Cases

  • Sprint Discovery: Identifies the requested or most recently modified sprint plan and extracts its goal, dates, tasks, priorities, owners, and estimates.
  • Progress Analysis: Calculates completion, time consumed, days remaining, burndown status, and risks using authoritative status data or markdown fallbacks.
  • Stale Work Detection: Flags inactive in-progress stories, missing story files, blocked must-haves, and other delivery concerns while remaining read-only.
  • Use Case: Use it during a daily standup to quickly determine whether the sprint is on track, which must-have stories need attention, and what single action should happen next.

Quick Start

Ask the sprint-status skill for the current sprint's progress snapshot or provide a sprint number to inspect a specific sprint.

Frequently Asked Questions about sprint-status

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

FAQPage Schema
How do I get a burndown snapshot for an agile sprint?

To get a burndown snapshot, the skill reads sprint plans and story status files to calculate completion metrics, time consumed, and days remaining. It identifies the most recently modified sprint plan automatically to generate a concise progress report.

How do I detect stale in-progress stories during a sprint health check?

Sprint health checks detect stale in-progress stories by reading story status files and flagging inactive work. The skill identifies missing story files, blocked must-haves, and delivery concerns while remaining strictly read-only.

Does sprint progress tracking work with markdown files or do I need a yaml config?

Sprint progress tracking works with both formats. The skill uses sprint-status.yaml for authoritative data when available, and falls back to markdown markers in your story files to calculate completion metrics and burndown status.

What is the best way to identify must-have story risks for a daily standup?

The best way to identify must-have risks is assessing sprint progress to flag blocked items and stale work. The skill evaluates story priorities and status files to highlight delivery concerns and provides exactly one actionable recommendation.

Can I assess sprint progress without manually reviewing individual story files and dates?

Yes, you can assess sprint progress automatically without manual review. The skill extracts goals, tasks, owners, and estimates directly from sprint plans and calculates burndown status using authoritative status data or markdown fallbacks.