skills.rest
johnatas-henrique
johnatas-henriqueCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sprint-status

Aggregate sprint metrics and flag stale tasks from plan and story files.

Updated Jul 16, 2026
Search Tags:#agile#status report#task tracking#sprint#burndown#stale detection
One-click install
npx skills add https://github.com/johnatas-henrique/overdrive --skill sprint-status-johnatas-henrique
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sprint-status
Source: https://github.com/johnatas-henrique/overdrive/tree/main/.opencode/skills/sprint-status
Command: npx skills add https://github.com/johnatas-henrique/overdrive --skill sprint-status-johnatas-henrique

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually tracking sprint progress across scattered plan and story files is time-consuming and often leads to missed blockers, stale tasks, and inaccurate burndown assessments. This Skill automates the process to give teams fast, accurate situational awareness without manual file digging.

Core Features & Use Cases

  • Automated Sprint Aggregation: Reads sprint plans and story files to pull task status, owner, priority, and date information in seconds.
  • Burndown & Risk Assessment: Calculates time consumed vs completion percentage to flag if the sprint is on track, at risk, or behind, and highlights stale in-progress tasks.
  • Use Case: For a 2-week product development sprint, run this Skill to get a 30-second update on must-have feature progress without reviewing individual task files manually.

Quick Start

Use the sprint-status skill to generate a concise progress report for your current or specified sprint.

Frequently Asked Questions about sprint-status

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

FAQPage Schema
How do I track sprint burndown across multiple story files without manual checks?▼

Automated sprint aggregation reads scattered plan and story files to pull task status, owner, priority, and dates, calculating burndown and completion percentages in seconds without manual file digging.

What is stale task detection in agile sprint tracking?▼

Stale task detection in agile sprint tracking identifies in-progress work that has not been updated recently, automatically flagging these tasks as risks to highlight potential blockers slowing sprint progress.

Can I generate a read-only sprint status report without modifying project files?▼

Yes, you can generate a read-only sprint status report without modifying project files, as the automated aggregation process provides situational awareness of burndown and task status while leaving source files untouched.

Does automated sprint status tracking work for a 2-week product development sprint?▼

Yes, automated sprint status tracking works for a 2-week product development sprint by aggregating metrics from plan and story files to deliver a fast 30-second update on must-have feature progress.

How do I flag sprint risks like behind or at-risk progress automatically?▼

To flag sprint risks automatically, the tracking process calculates time consumed against completion percentage to determine if the sprint is on track, at risk, or behind, while highlighting stale in-progress tasks.

Related Skills

Explore More Product & Management Skills→
rakhnianskii9rakhnianskii9

sprint-status

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

Community
Intermediate
wanghaishengwanghaisheng
10

sprint-plan

Generate and update sprint plans and status reports for agile teams.

Community
Advanced
sumilee-pcusumilee-pcu

sprint-status

Analyze sprint progress files and story markers to generate burndown reports.

Community
Intermediate
tygwantygwan
1

sync-fix

Detect and fix inconsistencies across Phase tasks, Sprint backlogs, and progress records.

Community
Basic