sprint-status

Produces concise sprint progress snapshots with burndown and risk indicators from sprint files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reads the current sprint plan and related story files to produce a concise progress snapshot with burndown and risk indicators, enabling rapid situational awareness during a sprint.

Core Features & Use Cases

  • Fast sprint health checks: generate a concise snapshot including burndown and emerging risks.
  • Status tracing: reads the sprint plan entries and optional sprint-status.yaml to determine progress and ownership.
  • Non-destructive: read-only tool that never writes files, suitable for quick status updates.

Quick Start

Provide a sprint status summary for the current sprint or for a specified 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 check sprint health and burndown progress quickly?

You can generate a sprint status summary by reading the current sprint plan entries and related story files to produce a concise progress snapshot with burndown and risk indicators for rapid situational awareness.

What is the best way to generate a sprint status report without modifying project files?

A sprint status report is generated using a strictly read-only tool that never writes files or changes story statuses. It reads production sprints and optional sprint-status.yaml to surface actionable recommendations without altering your project data.

Can I get a sprint progress snapshot for a specific sprint number instead of the current one?

Yes, sprint progress snapshots work against the current sprint or a specified sprint number. The tool scans the corresponding sprint plan and story entries to output a bounded, deterministic progress summary with risk indicators.

Does the sprint status tool require a sprint-status.yaml file to function?

No, the sprint-status.yaml file is optional. The tool determines progress and ownership by primarily reading sprint plan entries and related story files, only referencing the yaml file when present for additional status tracing.

Why use a dedicated sprint status snapshot instead of manually checking story files?

A dedicated sprint status snapshot provides rapid situational awareness by bounding output to a deterministic format with burndown and risk indicators. It aggregates sprint plan and story data automatically, surfacing actionable recommendations only when appropriate.