skills.rest
CarlosQ96
CarlosQ96COMMUNITY
Explore all skills by this author →
GitHub

sprint-status

Read sprint plans and story files to summarize progress and flag risks.

Updated Apr 9, 2026
Search Tags:#story#agile#status#report#sprint#burndown
One-click install
npx skills add https://github.com/CarlosQ96/robot-crawler --skill sprint-status-carlosq96
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sprint-status
Source: https://github.com/CarlosQ96/robot-crawler/tree/main/.agents/skills/sprint-status
Command: npx skills add https://github.com/CarlosQ96/robot-crawler --skill sprint-status-carlosq96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This sprint status skill helps teams quickly understand sprint progress without sifting through multiple files.

Core Features & Use Cases

  • Reads the current sprint plan and associated stories to compute progress.
  • Generates a concise burndown snapshot and highlights emergent risks, blockers, and stale items.
  • Responds to natural queries like "how is the sprint going" or "sprint update" with a ready-to-share report.

Quick Start

Ask for a sprint-status update to generate a current sprint snapshot.

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 story files?▼

Generating a sprint status report involves reading sprint plans and story files to summarize progress, computing elapsed and remaining days, and surfacing story statuses like DONE or BLOCKED. The output is a concise Markdown-friendly report highlighting risks.

What is the best way to track sprint progress and identify blockers?▼

Tracking sprint progress and identifying blockers is done by reading story files to compute days elapsed and flag stale items. It surfaces statuses for each story and produces a concise report highlighting emergent risks and recommended actions.

How do I calculate burndown and check for stale stories in an agile sprint?▼

Calculating burndown and checking for stale stories requires reading the sprint plan and associated story files. The process computes days remaining, flags stale items based on last-updated dates, and generates a snapshot highlighting blockers.

Does generating a sprint update modify my source story files?▼

Generating a sprint update does not modify any source files. It reads the sprint plan and story files to compute progress and surface statuses, producing a read-only 30-line Markdown-friendly report without altering the original data.

Can I get a quick sprint snapshot for an agile standup?▼

You can get a quick sprint snapshot for an agile standup by querying the current sprint status. It reads story files, computes elapsed days, flags blocked items, and outputs a concise report ready to share with the team.

Why are some story items flagged as stale in my sprint status report?▼

Story items are flagged as stale in a sprint status report when their last-updated dates indicate a lack of recent progress. The report identifies these items to highlight risks and recommend actions for stories that are not moving forward.

Related Skills

Explore More Product & Management Skills→
solace-illsolace-ill

sprint-status

Identify the current sprint by date and compile a status table with per-story status and blockers.

Community
Intermediate
kv0906kv0906
134

progress

Scan daily logs, blocker files, and decision records to generate cross-project status reports.

Community
Intermediate
johnatas-henriquejohnatas-henrique

sprint-status

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

Community
Intermediate
shogo-labsshogo-labs
12

sprint-board

Create and manage sprint board canvases with kanban columns and velocity tracking.

Official
Advanced