sprint-status

Summarize sprint health from sprint plan and story statuses.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/packetalien/cursor-game-studios --skill sprint-status-packetalien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-status
Source: https://github.com/packetalien/cursor-game-studios/tree/main/.cursor/skills/sprint-status
Command: npx skills add https://github.com/packetalien/cursor-game-studios --skill sprint-status-packetalien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a fast, reliable view of sprint health by reading the sprint plan and story statuses to surface progress, risk, and remaining work.

Core Features & Use Cases

  • Read the current sprint plan and story entries to extract goals, dates, and status markers.
  • Produce a concise, under-30-lines snapshot including burndown context and emerging risks.
  • Works for the current sprint or a specified sprint and supports quick situational awareness during execution.

Quick Start

Run /sprint-status to generate a quick sprint health snapshot.

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 quick sprint status snapshot for my agile project?

To get a sprint status snapshot, run /sprint-status to read the sprint plan and story statuses. It produces an under-30-lines report with burndown context, emerging risks, and recommended actions for quick situational awareness.

What is sprint burndown insight and how does it surface project risks?

Sprint burndown insight tracks remaining work against the sprint timeline to expose progress delays. Reading story statuses and the sprint plan surfaces emerging risks and provides a structured health report with recommended actions.

Can I generate a sprint health report for a specified past sprint?

Yes, sprint health reports work for the current sprint or a specified sprint. By reading the sprint plan and optional sprint-status.yaml, it extracts goals and dates to produce a concise snapshot for any targeted sprint.

What data format is needed to track sprint progress and burndown?

Tracking sprint progress relies on the sprint data format, specifically the sprint plan and an optional sprint-status.yaml file. These contain the goals, dates, and story statuses required to generate the burndown insight snapshot.

Does sprint-status require any external project-management integrations?

No, sprint-status has no external dependencies or integrations. It operates independently by reading the local sprint plan and story entries to summarize sprint health, burndown context, and risks.