bmad-dev-story

Implement software stories from a story spec with red-green-refactor cycles.

Updated Sep 27, 2025

Search Tags:#automation #code-review #test-driven-development #story-implementation #dev-story #sprint-management

Ready to run

npx skills add https://github.com/Cbanzaime23/Booking-System --skill bmad-dev-story-cbanzaime23

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-dev-story
Source: https://github.com/Cbanzaime23/Booking-System/tree/main/.agent/skills/bmad-dev-story
Command: npx skills add https://github.com/Cbanzaime23/Booking-System --skill bmad-dev-story-cbanzaime23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the development workflow by loading a complete, context-rich story spec and guiding developers through a deterministic, audit-ready implementation process.

Core Features & Use Cases

Context-driven workflow: loads architecture guidance, acceptance criteria, and DoD to drive implementation.
Sprint-aware tracking: updates sprint-status and maintains a traceable change log and Dev Agent Record.
Test-first discipline: enforces red-green-refactor cycles, test creation, and documentation updates to ensure quality.

Quick Start

Provide the story file path and say "start this story" to begin implementation.

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 software stories from contextual specs using test-driven development?▼

Story implementation from contextual specs is executed by loading architecture guidance and acceptance criteria, then enforcing a red-green-refactor cycle to produce verifiable code changes. This ensures test-first discipline and quality throughout the workflow.

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

A red-green-refactor cycle in story implementation is a test-driven development process where failing tests are written first, code is written to pass them, and then the code is refactored. This Skill enforces this cycle alongside documentation updates.

How do I automate sprint management and story implementation together?▼

Sprint management and story implementation are automated by updating sprint-status tracking and maintaining a traceable change log and Dev Agent Record. This integrates task tracking directly into the implementation workflow for audit-ready results.

Does this story implementation workflow validate against acceptance criteria and Definition of Done?▼

Yes, story implementation validates changes against acceptance criteria and Definition of Done (DoD). The workflow loads this context from the story spec to drive implementation and ensures artifact creation aligns with these validation requirements.

Can I use this for automated code review during story implementation?▼

Automated code review during story implementation is supported through structured workflow execution and DoD validation. By enforcing test creation and maintaining a Dev Agent Record, it produces verifiable, audit-ready changes aligned with acceptance criteria.

What do I need to start a story implementation with this workflow?▼

To start a story implementation, you need to provide the story file path and initiate the workflow. The system then loads the complete context-rich story spec, including architecture guidance and acceptance criteria, to drive the implementation process.