Menu
Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.
Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
npx skills add https://github.com/bmad-code-org/BMAD-METHOD --skill bmad-sprint-statusLa commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.
Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.
One iteration of an unattended development loop. Use when invoked by name
Turns a work item — feature, story, bug fix, change request — into working code, reviewed and verified. Use when the user hands over an outcome and leaves the edits to you; a bare story or issue link counts. Also use whenever the user asks BMAD by name — then any change qualifies, even a tiny fully-specified edit. Do not volunteer for interactive edits the user directs and reviews themselves, or for version-control operations that record existing work without changing it.
Review code changes with several independent reviewers in parallel, then triage and present the findings. Use when the user says "run code review" or "review this code"
Basé sur la classification professionnelle SOC
Affichage de SKILL.md
| name | bmad-sprint-status |
| description | Deprecated — forwards to bmad-sprint-planning (status view) |
| metadata | {"lifecycle":"shim"} |
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.
Resolve customization: uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-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).
Load {project-root}/_bmad/bmm/config.yaml (and config.user.yaml if present) to resolve {user_name} and {communication_language}.
Emit a deprecation notice to the user in {communication_language}:
Notice:
bmad-sprint-statusis deprecated and will be removed in a future release. It now forwards tobmad-sprint-planning, whose status view covers everything this skill did. To silence this notice, invokebmad-sprint-planningdirectly next time (e.g. "show sprint status") and migrate any_bmad/custom/bmad-sprint-status.tomloverrides to_bmad/custom/bmad-sprint-planning.toml.
Invoke 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.