sprint-status

Report sprint progress and emerging risks from plan and task files.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/imclab/xrA1-swarm --skill sprint-status-imclab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-status
Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/sprint-status
Command: npx skills add https://github.com/imclab/xrA1-swarm --skill sprint-status-imclab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates sprint blind spots by quickly summarizing sprint goal progress, task status, and emerging risks so teams can react early instead of discovering issues late.

Core Features & Use Cases

  • Sprint discovery & goal extraction: Finds the current or requested sprint by reading the appropriate sprint plan file and pulling goal, dates, and story/task metadata.
  • Status reconciliation: Uses production/sprint-status.yaml as the authoritative source when available, otherwise infers status by scanning markdown and referenced story/task files.
  • Burndown and risk assessment: Computes days remaining and completion percentage, upgrades verdicts when stories are stale, and flags conditions like missing files or sprint-at-risk thresholds.
  • Actionable output: Produces a concise table plus clear sections for Attention Needed, Burndown, Must-Haves at Risk, Emerging Risks, and a single concrete recommendation.

Quick Start

Ask for a sprint update by running /sprint-status with no argument to check the current sprint.

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 update for ongoing agile progress tracking?

Sprint status reporting summarizes sprint goal progress, task completion, and emerging risks so teams can react early instead of discovering issues late. It provides a concise snapshot of burndown and stale stories for coordination.

How does sprint burndown assessment and stale-story detection work from markdown files?

Burndown assessment computes days remaining and completion percentage by reading sprint plan markdown files and associated story/task status sources. It infers status via markdown scanning when an authoritative YAML status file is unavailable.

Do I need a specific status file format for agile sprint monitoring and risk assessment?

No specific file is strictly required for sprint monitoring. The tool optionally loads production/sprint-status.yaml as an authoritative source, but otherwise infers task status and emerging risks by scanning markdown and referenced story files.

What is the best way to report sprint progress and flag must-haves at risk?

The best way to report sprint progress is generating a concise table with clear sections for Attention Needed, Burndown, Must-Haves at Risk, Emerging Risks, and a single concrete recommendation, ensuring output stays under thirty lines for fast coordination.

Can I check sprint health for multiple active sprints using markdown project coordination?

Yes, sprint health checking finds the current or requested sprint by reading the appropriate sprint plan file. It pulls goal, dates, and story/task metadata to reconcile status and flag conditions like missing files or sprint-at-risk thresholds.

Why does my sprint update not show complete task status during progress tracking?

Sprint updates may show incomplete task status if markdown files are missing or stories are stale. The risk assessment upgrades verdicts when stories are stale and flags missing files, ensuring emerging risks are visible for project coordination.