sprint-status

Parse sprint plan and story files to generate a markdown progress report.

14|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill sprint-status-euraika-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-status
Source: https://github.com/Euraika-Labs/Codex-Code-Game-Studios/tree/main/.agents/skills/sprint-status
Command: npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill sprint-status-euraika-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often lack a quick, consolidated view of sprint progress, making it hard to spot delays, risks, or stalled stories without manually combing through plans and files.

Core Features & Use Cases

  • Reads the current sprint plan and optional sprint-status.yaml to extract story details.
  • Calculates days remaining, time consumed, and generates a burndown assessment.
  • Scans story files for status markers, detects stale in‑progress stories, and highlights emerging risks.
  • Provides a concise markdown report suitable for stand‑up meetings or rapid status checks.

Quick Start

Use the sprint-status skill to get a concise snapshot of the current sprint’s progress and risks.

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 burndown report from markdown story files?

To generate a sprint burndown report, the skill reads your current sprint plan and story markdown files, parses status markers, calculates days remaining, and outputs a concise markdown summary of progress and risks.

Can I detect stalled in-progress stories during an active sprint?

Yes, you can detect stalled in-progress stories by scanning story files for status markers and date metrics, which highlights stale tasks and surfaces emerging risks for your active sprint.

What's the best way to get a quick sprint status snapshot for stand-up meetings?

The best way to get a quick sprint status snapshot is to parse sprint plan files and calculate burndown metrics, producing a concise markdown report suitable for rapid stand-up reviews.

Does sprint tracking work with YAML and markdown plan files?

Sprint tracking works with both markdown and YAML files, reading the sprint plan and an optional sprint-status.yaml configuration to extract story details and calculate time consumed.

How are emerging risks identified during sprint story tracking?

Emerging risks are identified by scanning story files for status markers and calculating date metrics, detecting stale in-progress stories and time consumption issues to highlight potential sprint delays.

What do I need to calculate sprint burndown and days remaining?

You need access to production sprint plan files in markdown or YAML format with story status markers, which the skill parses to calculate days remaining, time consumed, and burndown progress.