bmad-dev-story

Implement BMAD stories with test-first changes and synchronized story records.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/mol4/BMAD-Board --skill bmad-dev-story-mol4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-dev-story
Source: https://github.com/mol4/BMAD-Board/tree/main/BMAD%20board/.agents/skills/bmad-dev-story
Command: npx skills add https://github.com/mol4/BMAD-Board --skill bmad-dev-story-mol4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers execute a BMAD story from start to finish without losing track of scope, status, or required documentation updates.

Core Features & Use Cases

  • Story-driven implementation: Follows the story spec in order, including tasks, subtasks, acceptance criteria, and dev notes.
  • Controlled updates: Limits edits to the approved story sections while keeping sprint status and completion tracking aligned.
  • Test-first delivery: Encourages red-green-refactor execution, validation, and regression checks before marking work complete.
  • Use Case: A developer can hand this Skill the next ready story and have it implemented, tested, documented, and prepared for review in one disciplined workflow.

Quick Start

Use this skill to implement the next ready BMAD story exactly as written and update the story file through to review readiness.

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 a sprint story while keeping the story record synchronized?

To implement a sprint story while keeping the record synchronized, you execute strict step sequencing and apply test-first changes, updating only the approved story file sections and sprint status to ensure documentation stays aligned.

What is test-first story implementation and how does it handle acceptance criteria?

Test-first story implementation applies red-green-refactor execution to fulfill acceptance criteria. It requires validation and regression checks before marking work complete, ensuring all specified tasks and subtasks pass final validation.

Can I use this workflow to process review follow-ups for an existing story file?

Yes, this workflow can process review follow-ups. It applies to sprint-based workflows where a specific story file, the next ready story, or review follow-ups must be completed in order with controlled updates.

How do I execute BMAD story tasks without losing track of sprint scope?

To execute BMAD story tasks without losing sprint scope, follow the story spec in order and limit edits to approved story sections. This controlled update mechanism keeps completion tracking and sprint status aligned.

Does this story implementation workflow enforce limitations on file edits?

Yes, this story implementation workflow enforces story-file-only edits. It limits changes to the approved story sections, preventing scope creep and ensuring final validation occurs before code review readiness.