Read sprint plans and story markers to report progress and stale work.
npx skills add https://github.com/scomofo/dragon-forge --skill sprint-status-scomofo
Please help me install this Agent Skill. Skill: sprint-status Source: https://github.com/scomofo/dragon-forge/tree/main/.agents/skills/sprint-status Command: npx skills add https://github.com/scomofo/dragon-forge --skill sprint-status-scomofo
It eliminates uncertainty about how a sprint is progressing by quickly summarizing sprint goal progress, story/task status, burndown signals, and emerging risks from the repository’s sprint plan and story markers.
production/sprint-status.yaml when present as the authoritative source; otherwise infers status by scanning referenced story/task files for DONE/IN PROGRESS/BLOCKED/NOT STARTED markers.Run /sprint-status to get the current sprint’s progress snapshot with burndown assessment and any at-risk or stale items.
High-intent search queries and answers about installing and using this skill.
To get a sprint progress snapshot, the tool parses your sprint plan file and scans story task status markers. It computes completion metrics, days remaining, and burndown signals to provide a concise read-only status update.
Sprint burndown tracking works by reading sprint-status.yaml or scanning story files for DONE, IN PROGRESS, BLOCKED, and NOT STARTED markers. It then calculates completion versus time consumed to detect alignment issues and emit escalation flags.
Yes, you can track sprint status for a specific sprint number by requesting it directly. If no number is specified, the tool automatically targets the most recently updated sprint file in your repository.
Stale in-progress work is detected by evaluating update timestamps on story and task files. When items remain in progress beyond expected thresholds, the snapshot flags them as STALE and emits at-risk or critical guidance.
No, sprint status reporting is strictly read-only and performs no file writes or proposed changes. It only reads sprint plans and task markers to generate burndown metrics, escalation flags, and a single recommendation.
The best way to assess sprint risk is to run an automated snapshot that computes days remaining, completion alignment, and stale work flags. It emits escalation guidance when thresholds are crossed, providing a fast read-only assessment.
tygwanControl sprint lifecycles and track velocity and burndown metrics.
zhongadamwangGenerate standardized project status reports and executive dashboards from project documentation.
wsmanTrack sprint progress and task status from markdown sprint plan files.
JaviMontanoTrack daily throughput with burndown charts and Monte Carlo projections.