skills.rest
striderZA
striderZACOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sprint-status

Read active sprint plans and extract story or task status from markdown or sprint-status.yaml.

72|7|Updated Apr 29, 2026
Search Tags:#project management#story tracking#burndown#sprint status#risk detection#read-only reporting
One-click install
npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill sprint-status-striderza
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sprint-status
Source: https://github.com/striderZA/OpenCodeGameStudios/tree/main/.opencode/skills/sprint-status
Command: npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill sprint-status-striderza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint status often gets stuck in scattered updates across chat and docs, making it hard to quickly understand what’s done, what’s blocked, and whether the sprint is slipping.

Core Features & Use Cases

It reads the current sprint plan and scans story/task files for status markers (or uses sprint-status.yaml when available) to produce a concise progress snapshot. It calculates time remaining and completion-based burndown verdicts, flags stale in-progress stories, and surfaces emerging risks like missing files or stalled work. Use it during a sprint for quick situational awareness when you need to answer how the sprint is going without running a full review.

Quick Start

Ask for a sprint update by running sprint-status with no argument to check the current sprint.

Frequently Asked Questions about sprint-status

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

FAQPage Schema
How do I get a quick sprint status update without running a full review?▼

You can get a sprint status update by reading the active sprint plan and extracting story status markers from markdown or sprint-status.yaml. It delivers a capped 30-line snapshot with remaining days and burndown assessment.

How does burndown assessment work for an in-progress sprint?▼

Burndown assessment calculates completion-based progress by scanning story files for status markers and comparing against remaining sprint days. It flags stale in-progress stories and stalled work to surface slipping sprint risks.

Can I check sprint risks like missing story files and stalled tasks mid-sprint?▼

Yes, you can detect mid-sprint risks by using Glob and Grep to locate sprint files and identify missing story files, stalled tasks, and stale in-progress stories. It surfaces these risks with at most one actionable recommendation.

Does sprint tracking work with markdown files or do I need a yaml configuration?▼

Sprint tracking works with markdown files by extracting status markers using Glob and Grep, and optionally reads sprint-status.yaml if available. It requires read-only access to the production/sprints/ directory to locate and parse files.

What are the limitations of read-only sprint status reporting?▼

Read-only sprint status reporting is limited to a capped 30-line output with at most one actionable recommendation, and cannot modify task statuses or sprint files. It only reads from production/sprints/ and optionally sprint-status.yaml.

Related Skills

Explore More Product & Management Skills→
FrancisVargaFrancisVarga

sprint-status

Compute sprint progress tables and risk flags from plan and story files.

Community
Intermediate
easonlaoeasonlao

sprint-status

Produces a sprint progress snapshot with burndown assessment and stale-story flags.

Community
Intermediate
nuoyanruoshuinuoyanruoshui
47

sprint-status

Assess sprint progress from plans and story status files.

Community
Advanced
rakhnianskii9rakhnianskii9

sprint-status

Aggregate sprint plan data and story statuses into a concise progress snapshot.

Community
Intermediate