bmad-dev-story

Implements sprint stories from spec files using red-green-refactor test-driven workflow.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Wizarck/nexandro --skill bmad-dev-story-wizarck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-dev-story
Source: https://github.com/Wizarck/nexandro/tree/main/skills/bmad-dev-story
Command: npx skills add https://github.com/Wizarck/nexandro --skill bmad-dev-story-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers working with BMAD-method sprint plans need a disciplined way to turn a story spec file into working, tested code without skipping tasks, breaking existing tests, or losing track of review follow-ups. ## Core Features & Use Cases - Story Discovery & Loading: Automatically finds the next ready-for-dev story from sprint-status.yaml or accepts an explicit story file path. - Test-Driven Implementation: Executes each task with a red-green-refactor cycle, writing failing tests first and validating no regressions before marking tasks complete. - Review Continuation: Detects prior code review findings and prioritizes unresolved [AI-Review] follow-up items before continuing regular tasks. - Definition of Done Validation: Runs a comprehensive checklist covering tests, documentation, file lists, and status updates before marking the story ready for review. - Use Case: A developer says "implement the next story in the sprint plan" and the Skill locates the story, implements every task with tests, updates the story file and sprint status, and hands off a review-ready result. ## Quick Start Ask the assistant to implement the next ready-for-dev story from the sprint plan or provide a specific story file path to develop.

Frequently Asked Questions about bmad-dev-story

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

FAQPage Schema
How do I implement the next story in a sprint plan automatically?▼

Provide the story file path or let the workflow read sprint-status.yaml to find the first story marked ready-for-dev. It then loads the story context, implements each task with tests, and updates the status to review when complete.

What is the red-green-refactor cycle in story implementation?▼

Red-green-refactor means writing a failing test first, implementing minimal code to make it pass, then improving the code structure while keeping tests green. This workflow enforces that cycle for every task and subtask in the story file.

Can it resume a story after a code review?▼

Yes. It detects a Senior Developer Review section in the story file, counts unresolved action items by severity, and prioritizes [AI-Review] follow-up tasks before continuing with remaining regular tasks.

What happens if tests fail during story implementation?▼

The workflow stops and fixes failures before continuing. Tasks are never marked complete unless all tests exist and pass, the full regression suite succeeds, and acceptance criteria are satisfied.

Which parts of the story file can be modified during development?▼

Only the Tasks/Subtasks checkboxes, Dev Agent Record (Debug Log and Completion Notes), File List, Change Log, and Status sections may be modified. All other story content remains untouched.

When does the workflow halt instead of completing a story?▼

It halts when the story file is inaccessible, requirements are ambiguous, new dependencies beyond the story spec are needed, configuration is missing, or three consecutive implementation failures occur.