bmad-sprint-status

Forwards deprecated sprint status requests to the bmad-sprint-planning status view.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill bmad-sprint-status-watchthelight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-sprint-status
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/bmad-sprint-status
Command: npx skills add https://github.com/watchthelight/shatterfish --skill bmad-sprint-status-watchthelight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill keeps legacy invocations of the retired bmad-sprint-status workflow working by transparently forwarding them to bmad-sprint-planning, so existing commands and customization files do not break after the consolidation. ## Core Features & Use Cases - Backward Compatibility: Existing invocations by name and _bmad/custom/bmad-sprint-status.toml override files continue to work without changes. - Deprecation Notice: Emits a localized notice telling users to migrate to bmad-sprint-planning and move their TOML overrides. - Context Forwarding: Resolves legacy customization fields (activation steps, persistent facts, on_complete) and passes them, along with the original user input, to bmad-sprint-planning's status view. - Use Case: A team member types the old "show sprint status" command after the workflow was consolidated; the shim resolves their saved overrides, warns about deprecation, and hands off to the current planning workflow. ## Quick Start Ask the assistant to show the current sprint status and it will route through this shim into bmad-sprint-planning's status view.

Frequently Asked Questions about bmad-sprint-status

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

FAQPage Schema
How do I show sprint status in the BMad Method?

Invoke bmad-sprint-planning directly with a request like "show sprint status" to open its status view. The old bmad-sprint-status skill still works but only forwards to bmad-sprint-planning and prints a deprecation notice.

What happened to the bmad-sprint-status skill?

It was consolidated into bmad-sprint-planning, which now owns gating, generating, and viewing the sprint-status artifact. The old skill remains as a thin compatibility shim and will be removed in a future release.

Will my bmad-sprint-status.toml customization file still work?

Yes, the shim resolves `_bmad/custom/bmad-sprint-status.toml` and `bmad-sprint-status.user.toml` overrides for the legacy fields and passes them to bmad-sprint-planning. You should migrate them to `_bmad/custom/bmad-sprint-planning.toml` to silence the deprecation notice.

How do I stop the bmad-sprint-status deprecation notice?

Invoke bmad-sprint-planning directly instead of the deprecated name, for example by asking to show sprint status. Also migrate any legacy TOML overrides to the bmad-sprint-planning customization file.

Does the bmad-sprint-status shim run the sprint workflow itself?

No, it performs no sprint logic of its own. After resolving customization and config, it hands control entirely to bmad-sprint-planning with the status-view intent and the original user input.