What triggers are supported?

bmad:sprint-plan and bmad:create-story.

Where are artifacts written?

Sprint plan at docs/bmad/sprint-plan.md; stories at docs/stories/STORY-*.md; sprint status at bmad/sprint-status.yaml.

Is REFERENCE.md required?

Yes, it must be read first before sprint planning and story creation.

bmad-scrum-master

npx machina-cli add skill xmm/codex-bmad-skills/bmad-scrum-master --openclaw

Files (1)

SKILL.md

3.3 KB

BMAD Scrum Master

Trigger Intents

bmad:sprint-plan
bmad:create-story

Workflow Variants

sprint-plan

Build sprint scope, sequencing, and capacity alignment.

create-story

Generate implementation-ready story files with acceptance criteria.

Inputs

approved planning and architecture artifacts
bmad/workflow-status.yaml
bmad/sprint-status.yaml
team capacity and timeline constraints

Language Guard (Mandatory)

Enforce language selection separately for chat responses and generated artifacts.

Chat language (communication_language) fallback order:

language.communication_language from bmad/project.yaml
English

Rules for chat responses:

Use the resolved chat language for all assistant responses (questions, status updates, summaries, and handoff notes).
Do not switch chat language unless the user explicitly requests a different language in the current thread.

Artifact language (document_output_language) fallback order:

language.document_output_language from bmad/project.yaml
English

Rules for generated artifacts:

Use the resolved artifact language for all generated BMAD documents and structured artifacts.
write prose and field values in the resolved document language
avoid mixed-language requirement clauses with English modal verbs (for example, System shall followed by non-English text)
allow English acronyms/abbreviations in non-English sentences (for example, API, SLA, KPI, OAuth, WCAG)
Keep code snippets, CLI commands, file paths, and identifiers in their original technical form.

Mandatory Reference Load

Before executing sprint-plan or create-story, read REFERENCE.md first. Treat REFERENCE.md as required context for sprint decomposition and story quality.

Output Contract

sprint plan -> docs/bmad/sprint-plan.md
story artifacts -> docs/stories/STORY-*.md
updated sprint state -> bmad/sprint-status.yaml

Core Workflow

Decompose epics into thin vertical stories.
Estimate size (prefer 1-8 points per story).
Plan sprint to match realistic capacity.
Generate stories with acceptance criteria and dependencies.
Update sprint status and hand off to developer.

Script Selection

Story ID generation:
```
bash scripts/generate-story-id.sh
```
Velocity support:
```
python3 scripts/calculate-velocity.py
```
Burndown support:
```
python3 scripts/sprint-burndown.py
```

Template Map

templates/sprint-plan.template.md
Why: sprint objective, scope, and sequencing.
templates/user-story.template.md
Why: story format with acceptance criteria.
templates/sprint-status.template.yaml
Why: machine-readable sprint tracking state.

Reference Map

REFERENCE.md
Must read first for sprint workflow guidance and story quality expectations.
resources/story-sizing-guide.md
Use to keep estimates consistent and avoid oversized stories.

Quality Gates

sprint scope matches team capacity
stories are independent and testable
acceptance criteria and dependencies are explicit
sprint status reflects planned work accurately

Source

git clone https://github.com/xmm/codex-bmad-skills/blob/main/skills/bmad-scrum-master/SKILL.mdView on GitHub

Overview

BMAD Scrum Master enables sprint planning for BMAD by building sprint scope, sequencing, and capacity alignment, and by generating implementation-ready stories with acceptance criteria. It orchestrates inputs like approved planning artifacts and capacity constraints to produce ready-to-use BMAD documents.

How This Skill Works

Triggered by bmad:sprint-plan or bmad:create-story, it reads approved artifacts and status files, decomposes epics into thin vertical stories, and assigns estimates (1–8 points). It then uses templates to generate docs at docs/bmad/sprint-plan.md and docs/stories/STORY-*.md, and updates bmad/sprint-status.yaml.

When to Use It

When building sprint scope for bmad:sprint-plan.
When creating implementation-ready stories for bmad:create-story.
When decomposing epics into thin vertical stories with dependencies.
When aligning sprint capacity with team constraints.
When updating sprint status after planning or story creation.

Quick Start

Step 1: Trigger with bmad:sprint-plan or bmad:create-story.
Step 2: Provide inputs: approved planning artifacts, bmad/workflow-status.yaml, bmad/sprint-status.yaml, capacity constraints.
Step 3: Run the BMAD workflow to generate docs and stories; review and hand off to developers.

Best Practices

Decompose epics into independent, testable stories.
Estimate size 1–8 points per story and use the story-sizing-guide.
Explicitly document acceptance criteria and dependencies.
Verify input artifacts (architecture artifacts, status files) are current.
Always read REFERENCE.md before planning and story creation.

Example Use Cases

Sprint plan for BMAD Q3 feature set using approved architecture artifacts.
Story generation for a new BMAD API integration with acceptance criteria.
Vertical slicing of a BMAD epic into 3–5 stories with clear dependencies.
Capacity alignment for the upcoming sprint using team constraints in sprint-status.yaml.
Documentation artifacts generated to docs folders and sprint-status.yaml updated.

Frequently Asked Questions

Add this skill to your agents