Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Deprecated — forwards to bmad-sprint-planning (status view)
.claude/skills/bmad-code-org-bmad-sprint-status/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-04 | ✗→✓ | ▲ Improved | -41% | 0% |
| case-05 | ✗→✓ | ▲ Improved | -27% | 0% |
| case-06 | ✗→✓ | ▲ Improved | -73% | 0% |
| case-07 | ✗→✓ | ▲ Improved | -42% | 0% |
| case-09 | ✗→✓ | ▲ Improved | -51% | 0% |
This skill was consolidated into bmad-sprint-planning, which now owns the whole sprint-status artifact: gate it, generate it, view it. It is retained as a thin compatibility shim so existing invocations by name and _bmad/custom/bmad-sprint-status.toml override files keep working. New work should invoke bmad-sprint-planning directly — "show sprint status" routes straight to the status view.
uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow. This picks up any {project-root}/_bmad/custom/bmad-sprint-status.toml and bmad-sprint-status.user.toml overrides for the legacy fields (activation_steps_prepend, activation_steps_append, persistent_facts, on_complete).{project-root}/_bmad/bmm/config.yaml (and config.user.yaml if present) to resolve {user_name} and {communication_language}.{communication_language}:> Notice: bmad-sprint-status is deprecated and will be removed in a future release. It now forwards to bmad-sprint-planning, whose status view covers everything this skill did. To silence this notice, invoke bmad-sprint-planning directly next time (e.g. "show sprint status") and migrate any _bmad/custom/bmad-sprint-status.toml overrides to _bmad/custom/bmad-sprint-planning.toml.
bmad-sprint-planning with the following context. Pass these as the activating context so it honors them instead of resolving its own customization from scratch:status view — skip bmad-sprint-planning's usual intent detection and its readiness gate.bmad-sprint-planning's own customize.toml for the four legacy fields: activation_steps_prepend, activation_steps_append, persistent_facts, and on_complete = the resolved values from step 1.bmad-sprint-planning takes the workflow from here. Do not execute any further steps in this shim.
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→fail | 10,535 | 8,631 | -18% | 1 | 1 | 0% | 1,602 | 2,140 | +34% | 0 | 0 | — |
case-02 | fail→fail | 16,554 | 14,522 | -12% | 1 | 1 | 0% | 2,627 | 1,972 | -25% | 0 | 0 | — |
case-03 | fail→fail | 12,677 | 16,536 | +30% | 1 | 1 | 0% | 1,935 | 1,342 | -31% | 0 | 0 | — |
case-04 | fail→pass | 17,759 | 3,583 | -80% | 1 | 1 | 0% | 2,000 | 1,178 | -41% | 0 | 0 | — |
case-05 | fail→pass | 11,390 | 3,638 | -68% | 1 | 1 | 0% | 1,582 | 1,152 | -27% | 0 | 0 | — |
case-06 | fail→pass | 41,610 | 4,048 | -90% | 1 | 1 | 0% | 4,196 | 1,128 | -73% | 0 | 0 | — |
case-07 | fail→pass | 16,017 | 4,784 | -70% | 1 | 1 | 0% | 2,207 | 1,271 | -42% | 0 | 0 | — |
case-08 | fail→fail | 11,101 | 4,183 | -62% | 1 | 1 | 0% | 1,731 | 1,212 | -30% | 0 | 0 | — |
case-09 | fail→pass | 23,564 | 3,579 | -85% | 1 | 1 | 0% | 2,138 | 1,041 | -51% | 0 | 0 | — |
case-10 | fail→pass | 7,555 | 3,782 | -50% | 1 | 1 | 0% | 1,042 | 1,141 | +10% | 0 | 0 | — |
case-11 | pass→pass | 5,825 | 4,758 | -18% | 1 | 1 | 0% | 987 | 1,176 | +19% | 0 | 0 | — |
case-12 | fail→pass | 9,490 | 4,783 | -50% | 1 | 1 | 0% | 1,444 | 1,230 | -15% | 0 | 0 | — |
case-13 | fail→pass | 12,567 | 5,616 | -55% | 1 | 1 | 0% | 1,795 | 1,533 | -15% | 0 | 0 | — |
case-14 | pass→fail | 12,941 | 3,905 | -70% | 1 | 1 | 0% | 1,919 | 1,184 | -38% | 0 | 0 | — |
case-15 | fail→pass | 10,410 | 5,333 | -49% | 1 | 1 | 0% | 1,393 | 1,378 | -1% | 0 | 0 | — |
case-16 | fail→pass | 8,310 | 2,649 | -68% | 1 | 1 | 0% | 1,441 | 947 | -34% | 0 | 0 | — |
case-17 | pass→pass | 19,287 | 2,575 | -87% | 1 | 1 | 0% | 3,214 | 856 | -73% | 0 | 0 | — |
case-18 | fail→pass | 17,781 | 3,655 | -79% | 1 | 1 | 0% | 2,879 | 995 | -65% | 0 | 0 | — |
case-19 | fail→pass | 17,159 | 2,753 | -84% | 1 | 1 | 0% | 1,612 | 1,001 | -38% | 0 | 0 | — |
case-20 | pass→pass | 14,236 | 15,961 | +12% | 1 | 1 | 0% | 2,209 | 3,012 | +36% | 0 | 0 | — |
case-21 | pass→pass | 10,971 | 9,615 | -12% | 1 | 1 | 0% | 1,796 | 2,075 | +16% | 0 | 0 | — |
case-22 | pass→pass | 12,191 | 13,556 | +11% | 1 | 1 | 0% | 1,823 | 3,050 | +67% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted, and 21 counted toward the lift figure. The other 1 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of +50 percentage points is the difference between those two pass rates over the 21 comparable cases. 1 case got worse with the skill loaded, and it is included in that figure.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.