skills.rest
cenconq25
cenconq25COMMUNITY
Explore all skills by this author →
GitHub

sprint-status

Summarize sprint progress from sprint plans and story files.

39|6|Updated May 3, 2026
Search Tags:#planning#story#agile#status#sprint#read-only#burndown
One-click install
npx skills add https://github.com/cenconq25/claude-code-app-studio --skill sprint-status-cenconq25
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sprint-status
Source: https://github.com/cenconq25/claude-code-app-studio/tree/main/.claude/skills/sprint-status
Command: npx skills add https://github.com/cenconq25/claude-code-app-studio --skill sprint-status-cenconq25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fast, read-only visibility into sprint health by aggregating the active sprint plan and story statuses, letting teams spot progress gaps quickly.

Core Features & Use Cases

  • Reads the active sprint plan from production/sprints
  • Scans story files in production/epics to determine status
  • Produces a concise, read-only progress snapshot with burndown hints

Quick Start

Ask Claude to generate a real-time sprint snapshot using the active sprint data.

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 status and burndown progress quickly?▼

To check sprint status, the Skill reads the active sprint plan from production/sprints and story files from production/epics, generating a read-only snapshot with burndown hints and progress counts.

What is the best way to surface sprint risks and blockers during a standup?▼

Surfacing sprint risks and blockers is done by reading the active sprint plan and story files to produce a concise snapshot, highlighting status gaps and potential issues for mid-sprint checks.

Can I view sprint health without modifying my project files?▼

Yes, viewing sprint health is completely read-only; the Skill scans production/sprints and production/epics to compute burndown and story counts without writing any files.

Do I need specific file structures to track agile sprint progress?▼

To track agile sprint progress, you need active sprint files in production/sprints and story files in production/epics, with optional production/session-state data for accurate burndown computation.

How does sprint burndown calculation work with story files?▼

Sprint burndown calculation works by reading story statuses from production/epics and cross-referencing them with the active sprint plan, producing a snapshot of completed and remaining work.

When should I use a read-only sprint snapshot instead of editing stories?▼

A read-only sprint snapshot is ideal for sprint reviews, standups, and mid-sprint checks where you need to assess progress and risks without altering the actual sprint plan or story files.

Related Skills

Explore More Product & Management Skills→
tygwantygwan
1

sprint

Control sprint lifecycles and track velocity and burndown metrics.

Community
Basic
Fantasia1999Fantasia1999

scrum-master

Analyze sprint data with Python scripts for forecasting and health scoring.

Community
Advanced
matteocervellimatteocervelli
25

sprint-planner

Plan sprints by optimizing capacity and selecting backlog stories.

Community
Advanced
johnatas-henriquejohnatas-henrique

sprint-status

Aggregate sprint metrics and flag stale tasks from plan and story files.

Community
Intermediate