sprint-status

Read sprint plans and Story statuses to compute progress and burndown.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/brand6/Claude-Code-Game-Studios-zh-auto --skill sprint-status-brand6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-status
Source: https://github.com/brand6/Claude-Code-Game-Studios-zh-auto/tree/main/.claude/skills/sprint-status
Command: npx skills add https://github.com/brand6/Claude-Code-Game-Studios-zh-auto --skill sprint-status-brand6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reads the current sprint plan and Story statuses to produce a concise progress snapshot including burn-down and risk signals, enabling quick alignment.

Core Features & Use Cases

  • Read sprint plans and Story statuses to summarize progress
  • Compute remaining days and burn-down status
  • Flag emerging risks and blockers for immediate attention

Quick Start

Run sprint-status to generate the latest sprint snapshot and burn-down risk report.

Frequently Asked Questions about sprint-status

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

FAQPage Schema
How do I check sprint progress and burndown from existing story statuses?

Sprint progress is identified by reading the current sprint plan and Story statuses to produce a concise snapshot of progress and burndown. It computes remaining days, burn-down status, and flags emerging risks and blockers for immediate attention.

What is a sprint burndown snapshot and when do I need it for agile planning?

A sprint burndown snapshot summarizes remaining work and days by reading sprint files and Story statuses. You need it during ad-hoc sprint checks to quickly answer how the sprint is progressing and identify emerging risks or blockers for immediate attention.

How do I flag sprint risks and blockers for quick team alignment?

To flag sprint risks and blockers, run this Skill to read your sprint files and Story statuses. It automatically computes burndown status and flags emerging risks and blockers, producing a concise report that enables quick alignment and immediate action.

Can I use this for ad-hoc sprint checks at any point during the iteration?

Yes, you can apply this to ad-hoc sprint checks at any point during the iteration. It reads the current sprint plan and Story statuses on demand to answer how the sprint is progressing and flag risks for quick action.

What sprint planning format does the status reader need to compute remaining days?

The sprint status reader requires sprint plan files and Story statuses as input. It reads these sprint files to extract current statuses, computes remaining days and burn-down, and generates the concise progress snapshot for quick review.