sprint-status

Track sprint progress and task status from markdown sprint plan files.

18|5|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill sprint-status-wsman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-status
Source: https://github.com/wsman/MY-DOGE-MICRO/tree/main/.agents/skills/sprint-status
Command: npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill sprint-status-wsman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill gives teams a fast, reliable snapshot of sprint health without manually opening every plan, story, and status file. It helps identify progress, blockers, stale work, and burndown risk early enough to act.

Core Features & Use Cases

  • Sprint progress summary: Reads the current sprint plan or a specified sprint and turns it into a concise status view.
  • Burndown and risk assessment: Compares completed work against time consumed, then highlights late or blocked must-have items.
  • Status inference and validation: Uses sprint-status data when available, falls back to markdown scanning when needed, and flags missing story files or stale in-progress work.
  • Use case: A product lead can ask for a sprint update and quickly see what is done, what is blocked, and what still needs attention before the sprint ends.

Quick Start

Ask the sprint-status skill to review the current sprint and summarize task progress, burndown, risks, and any stale in-progress stories.

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 progress and burndown status from markdown files?

Sprint progress tracking is done by reading markdown sprint plan files and comparing completed work against time consumed to generate a concise burndown and risk report. The skill scans status markers and optionally uses a sprint-status.yaml file to infer current sprint health.

What is the best way to detect stale in-progress stories during an agile sprint?

Stale in-progress story detection works by scanning markdown story files for status markers and comparing dates to identify work that has remained in-progress without updates. This flags stalled tasks early enough for product leads to act before the sprint ends.

Do I need a sprint-status.yaml file to track sprint health and blockers?

A sprint-status.yaml file is optional for tracking sprint health and blockers. The skill uses sprint-status data when available but falls back to markdown scanning of sprint plan files to infer task status, validate story files, and report risks.

Can I use markdown sprint plans to identify blocked must-have items and burndown risk?

Markdown sprint plans can be used to identify blocked must-have items and burndown risk by scanning status markers and comparing completed work against time consumed. The skill highlights late or blocked items and flags missing story files for agile project updates.

How do I get a sprint update summary for a specific numbered sprint?

Numbered sprint lookups are supported by reading the specified sprint plan file and turning it into a concise status view. The skill summarizes task progress, burndown, risks, and stale in-progress stories for the requested sprint number.

What are the limitations of using markdown scanning for sprint status inference?

Markdown scanning for sprint status inference relies on consistent status markers within plan files and cannot detect progress if story files are missing or poorly formatted. It also requires date comparison data to accurately identify stale in-progress work and burndown risk.