bmad-story-pipeline

Original：🇺🇸 English

Translated

Run configurable BMAD pipeline for story delivery using subagent

2installs

Sourceterryso/claude-bmad-skills

Added on2026-03-08

NPX Install

npx skill4agent add terryso/claude-bmad-skills bmad-story-pipeline

SKILL.md Content

View Translation Comparison →

BMAD Story Pipeline

Complete the delivery pipeline for story

{ARGUMENT}

using configurable workflow.

Pre-step: Determine Story Number

If

{ARGUMENT}

is empty or not provided:

Read

_bmad-output/implementation-artifacts/sprint-status.yaml

(or

docs/sprint/sprint-status.yaml

) to find stories

Find the first story with status "todo" or "in-progress"
Use that story number as
```
{STORY_ID}
```
If no story found, ask user to specify story number

The story number format is typically

X-Y

(e.g.,

1-1

,

2-3

).

Execution Strategy

Read workflow steps from references/workflow-steps.md
Execute each step sequentially using Task tool (general-purpose agent)
Output progress after each step
After pipeline, update status to done

Workflow Steps

Read and execute steps from references/workflow-steps.md.

For each step defined there, you MUST use the Task tool to execute in a subagent:

Task(
  subagent_type: "general-purpose",
  description: "<Step description>",
  prompt: "Execute the command: <COMMAND_WITH_STORY_ID>
Return: 1) Step completion status 2) Key outputs 3) Any issues to note"
)

Example Invocations

Step 1 - Create Story:

Task(
  subagent_type: "general-purpose",
  description: "Create user story {STORY_ID}",
  prompt: "Execute /bmad-bmm-create-story {STORY_ID} yolo to create story file. Return: 1) Story ID and Title 2) Created files 3) Any issues"
)

Step 2 - ATDD Tests:

Task(
  subagent_type: "general-purpose",
  description: "Generate ATDD tests for {STORY_ID}",
  prompt: "Execute /bmad-tea-testarch-atdd {STORY_ID} yolo to generate acceptance tests. Return: 1) ATDD checklist 2) Test files created 3) Any issues"
)

Step 3 - Development:

Task(
  subagent_type: "general-purpose",
  description: "Develop user story {STORY_ID}",
  prompt: "Execute /bmad-bmm-dev-story {STORY_ID} yolo to implement story code. Return: 1) Modified files 2) Summary of changes 3) Any issues"
)

Step 4 - Code Review:

Task(
  subagent_type: "general-purpose",
  description: "Code review for {STORY_ID}",
  prompt: "Execute /bmad-bmm-code-review {STORY_ID} yolo for adversarial review. Return: 1) Conclusion (pass/needs-fix) 2) Issues by severity 3) Any blocking issues"
)

Step 5 - Trace Coverage:

Task(
  subagent_type: "general-purpose",
  description: "Trace test coverage for {STORY_ID}",
  prompt: "Execute /bmad-tea-testarch-trace {STORY_ID} yolo for traceability matrix. Return: 1) Coverage percentage 2) Gate decision 3) Any gaps"
)

Execution Flow

For each step:

Replace
```
{STORY_ID}
```
with the actual story number in the prompt
Call Task tool with the step's description and prompt
Wait for completion and capture result
Output progress:
```
[X/5] Step Name - Status
```
If step fails, stop and report error

Progress Display

After each step, output progress:

📊 Pipeline Progress: [X/5] ████████░░░░ 40%

✅ Step X: <Step Name>
   Result: <Brief result summary>

Error Handling

If any step fails:

Stop executing subsequent steps

Output error information:

❌ Pipeline Failed at Step X: <Step Name>

Error: <Error details>

💡 Suggested actions:
- Check the story file for issues
- Run the failed step manually: <command>
- Fix the issue and restart pipeline

Do NOT proceed to next steps

Post-Pipeline: Update Status

After ALL steps complete successfully:

Update sprint-status.yaml:
- Find the story entry
- Change status from
```
in-progress
```
  to
```
done
```
Update story document (if exists):
- Change
```
Status:
```
  to
```
done
```
- Mark all tasks with ✅

Output final summary:

🎉 Pipeline Complete!

Story: {STORY_ID}
Status: done

📋 Steps completed: 5/5
✅ Create User Story
✅ Generate ATDD Tests
✅ Development
✅ Code Review
✅ Trace Test Coverage

Configuration

To customize the pipeline workflow, edit: references/workflow-steps.md

Changes supported:

Add/remove steps
Modify step commands
Reorder steps
Change descriptions