sprint-status

Reads sprint plans and story files to compile sprint progress metrics.

Updated Jul 22, 2025
One-click install
npx skills add https://github.com/MichaelSolati/mkai --skill sprint-status-michaelsolati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-status
Source: https://github.com/MichaelSolati/mkai/tree/main/profiles/game-dev/skills/sprint-status
Command: npx skills add https://github.com/MichaelSolati/mkai --skill sprint-status-michaelsolati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually tracking sprint progress, checking individual story statuses, and calculating burndown metrics is time-consuming and prone to oversight, especially for fast-moving software development teams that need quick situational awareness during active sprints.

Core Features & Use Cases

  • Automated Status Compilation: Reads sprint plans and story files to extract task status, priority, and owner information without manual data entry.
  • Burndown & Risk Assessment: Calculates remaining sprint time, completion percentage, and flags stale in-progress stories that have not been updated in 4 or more days.
  • Use Case: A scrum master running this skill mid-sprint can instantly identify blocked must-have tasks, assess if the team is on track to meet the sprint goal, and catch stalled work before it impacts delivery.

Quick Start

Ask your AI assistant to run the sprint-status skill to get an instant progress snapshot of your current active sprint, including burndown metrics and at-risk tasks.

Frequently Asked Questions about sprint-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate sprint progress tracking without manual data entry?

Automated sprint progress tracking reads existing sprint plans and story files to extract task status, priority, and owner information, compiling real-time metrics without manual data entry.

How does burndown health assessment identify at-risk deliverables during an active sprint?

Burndown health assessment calculates remaining sprint time and completion percentage, flagging stale in-progress stories untouched for 4 or more days and highlighting at-risk must-have deliverables for intervention.

Can I use this for read-only sprint reporting if I only need to identify blockers?

Yes, this read-only sprint reporting tool serves software development teams and scrum masters by instantly identifying blocked must-have tasks and stalled work during active sprints.

What's the best way to get a mid-sprint progress snapshot for scrum teams?

Getting a mid-sprint progress snapshot requires running an automated status compilation against sprint plans and associated story files to quickly assess task completion and catch stalled work before it impacts delivery.

When should I not rely on automated sprint status compilation for risk assessment?

Automated sprint status compilation relies on reading existing sprint plans and story files, so it is not suitable if your project lacks structured story files or requires write access to update task statuses directly.