Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/sprint-status
Fast sprint status check. Reads the current sprint plan, scans story files for status, and produces a concise progress snapshot with burndown assessment and emerging risks. Run at any time during a sprint for quick situational awareness.
Passed 10 of 16 test cases with the skill, and 4 of 16 without it.
and 6 more in the full report
9 fixed6 passed either way8 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/2/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are inspecting a legacy sprint project where production/sprint-status.yaml does not exist, so status was inferred by scanning markdown files. What fallback warning note must be added at the bottom of the status report?
| Checked | Without skill | With skill |
|---|---|---|
| Displays a fallback warning note indicating that sprint-status.yaml was not found and recommending /sprint-plan update. | Missed | Passed |
The instructions your model reads when the skill loads.
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys story_granularity,workflow
This is a fast situational awareness check, not a sprint review. It reads the
current sprint plan and story files, scans for status markers, and produces a
concise snapshot in under 30 lines. For detailed sprint management, use
/sprint-plan update or /milestone-review.
This skill is read-only. It never proposes changes, never asks to write files, and makes at most one concrete recommendation.
story_granularity — it sets the
grain of the burn-down read: feature-sized chunks at coarse (the default, via rigor: minimal), task-sized
at balanced (rigor: standard), AC-sized at fine.
Argument: $ARGUMENTS (blank = use current sprint)
/sprint-status 3), search
production/sprints/ for a file matching sprint-003.md, sprint-03.md, sprint-3.md,
or similar (/sprint-plan writes three digits). Report which file was found.production/sprints/ and treat it as the current sprint.production/sprints/ does not exist or is empty:
workflow: minimal there are no sprints by design — the brief's
build order is the plan and the story files carry it. Report progress
through it instead, then stop:
.claude/scripts/story-status.sh
before you read this skill: one line per unfinished story, already in
the route's order (IN_REVIEW, IN_PROGRESS, then TODO — a Ready
or Not Started story — in build order), then BLOCKED, OTHER,
NO_STATUS and the COMPLETE count:!bash "${CLAUDE_SKILL_DIR}/../../scripts/story-status.sh"
test cases passed, vs 4 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.