bmad-dev-story

Execute story implementation from a spec file with red-green-refactor and validation gates.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/cassioalexandre/agf --skill bmad-dev-story-cassioalexandre
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-dev-story
Source: https://github.com/cassioalexandre/agf/tree/main/_bmad/bmm/4-implementation/bmad-dev-story
Command: npx skills add https://github.com/cassioalexandre/agf --skill bmad-dev-story-cassioalexandre

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of turning an AI-authored or context-rich story specification into a correctly implemented sprint story with consistent validation, testing, and strict edit boundaries.

Core Features & Use Cases

  • Guided story execution: Follows a workflow to locate the next “ready-for-dev” story (or use an explicitly provided story file) and implement tasks in order.
  • Red-green-refactor implementation discipline: Drives development via failing tests first, minimal code to pass, then refactoring while keeping tests green.
  • Governed completion workflow: Enforces story-ready validation gates (tests exist and pass, acceptance criteria satisfied, file list and change log updated, and only permitted story sections modified).
  • Review continuation support: Detects “Senior Developer Review (AI)” context and prioritizes unresolved “Review Follow-ups (AI)” items.

Quick Start

Use the bmad-dev-story skill when you say "dev this story path/to/story.md" to execute the full implementation workflow from the story’s Dev Notes and tasks.

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 sprint stories from a spec file without missing acceptance criteria?

Implement sprint stories by executing ordered tasks directly from a context-filled spec file, ensuring acceptance criteria and developer notes are satisfied. This guided workflow reduces ambiguity and enforces strict edit boundaries to prevent unauthorized changes.

What is the red-green-refactor workflow for story implementation?

Red-green-refactor is a development discipline that drives story implementation by writing failing tests first, adding minimal code to pass them, then refactoring while keeping tests green. This ensures robust test coverage throughout the sprint workflow.

How do I validate that a story meets the definition of done before merging?

Validate the definition of done by enforcing completion gates that check if tests exist and pass, acceptance criteria are satisfied, the file list and change log are updated, and only permitted story sections were modified during implementation.

Can I use this workflow for standalone development outside of a sprint?

Yes, this story implementation workflow applies to both sprint-based and standalone development. You can explicitly provide a story file path to execute the full implementation workflow regardless of sprint planning context.

How do I handle unresolved review follow-ups from a senior developer?

Handle unresolved review follow-ups by detecting the Senior Developer Review context and prioritizing outstanding Review Follow-ups items. The workflow automatically identifies these items and addresses them during story implementation.

How do I start implementing a story using a markdown spec file?

Start story implementation by providing the path to your story markdown file. The workflow locates the next ready-for-dev story or uses your explicitly provided file to execute tasks in order from the story's Dev Notes.