sprint-status

Scan sprint documents for story status and calculate burndown metrics.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides immediate situational awareness for sprint progress, helping you stay on track and identify potential risks with a concise summary.

Core Features & Use Cases

  • Sprint Progress Snapshot: Offers a summary of completed tasks, tasks in progress, and outstanding tasks with a burndown analysis.
  • Stale Story Detection: Flags stories that haven't been updated for more than four days, aiding in risk identification.
  • Automated Reports: Automatically generates reports that can be used for sprint reviews or daily stand-ups.

Quick Start

Check the status of the current sprint by running /sprint-status or /sprint-status [sprint-number].

Frequently Asked Questions about sprint-status

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

FAQPage Schema
How do I generate a sprint status report from markdown documents?

To generate a sprint status report, this Skill scans your sprint markdown documents for story status, calculates burndown metrics, and flags stale stories older than four days. It parses dates and categorizes status to provide a concise progress snapshot.

What is burndown analysis and how does it identify sprint risks?

Burndown analysis calculates sprint progress metrics by scanning completed, in-progress, and outstanding tasks. It identifies sprint risks by flagging stale stories that haven't been updated for more than four days, providing immediate situational awareness.

Can I use sprint tracking for daily stand-ups and sprint reviews?

Yes, you can use sprint tracking for daily stand-ups and sprint reviews. It automatically generates concise summary reports containing burndown analysis and risk identification, offering immediate situational awareness for sprint progress.

Does sprint status reporting work without external dependencies?

Sprint status reporting works without external dependencies. It relies solely on internal scripts to parse markdown formats, compare dates, and categorize story statuses to deliver burndown metrics and risk assessments.

What is the best way to track stale stories during a sprint?

The best way to track stale stories is using automated risk identification that flags stories untouched for more than four days. This detects stalled progress early by scanning markdown documents for date comparison and status updates.