sprint-status

Generate a terminal dashboard from sprint-status.yaml with global, epic, and blocked-issue views.

2|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/EvanPluchart/kyomu --skill sprint-status-evanpluchart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-status
Source: https://github.com/EvanPluchart/kyomu/tree/main/.claude/skills/sprint-status
Command: npx skills add https://github.com/EvanPluchart/kyomu --skill sprint-status-evanpluchart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes uncertainty in sprint execution by synthesizing sprint progress, epic breakdowns, and blocked story reasons into a single terminal-readable dashboard.

Core Features & Use Cases

  • Sprint-wide progress dashboard: Computes global completion (done/total), status counts, size distribution, and time spent vs estimates from a sprint status source of truth.
  • Epic-level visibility: Summarizes progress per epic to quickly identify which initiatives are on track, completed, or stalled.
  • Issue-focused blockers & risks: Lists blocked stories with unresolved dependency/error/complexity reasons and highlights stories with extreme difficulty.

Quick Start

Run sprint-status in normal mode using the sprint path from your repo’s sprint folders to print a formatted dashboard in your terminal.

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 progress dashboard from my terminal?

To generate a sprint progress dashboard, run the command in normal mode using your repository's sprint path to print a terminal-formatted text dashboard. It reads your sprint status source of truth and computes global completion, status counts, and size distribution.

How does dependency-aware next story selection work for sprint planning?

Dependency-aware next story selection resolves story availability by checking unresolved dependencies within your sprint status source of truth. It evaluates blocked stories and computes which todo stories are ready for execution based on dependency constraints.

Can I view epic-level analytics for my sprint tracking?

Yes, you can view epic-level analytics by running the command in Epics mode. It summarizes progress per epic from your sprint status source of truth, helping you quickly identify which initiatives are on track, completed, or stalled.

What is the best way to track blocked stories and sprint blockers?

The best way to track blocked stories is using Issues mode, which lists blocked stories with unresolved dependency, error, or complexity reasons from your sprint status source of truth. It highlights stories with extreme difficulty for risk assessment.

Does sprint reporting work with multi-sprint tracking workflows?

Yes, sprint reporting supports multi-sprint tracking workflows. It reads your structured sprint status source of truth and generates terminal-formatted text dashboards for both single-sprint and multi-sprint reporting with next-story selection.

Why does my sprint status dashboard show incomplete progress metrics?

Your sprint status dashboard may show incomplete metrics if the sprint status source of truth file lacks complete done/total counts or time spent estimates. The tool computes distributions and progress directly from this structured input file.