bmad-dev-story

Automate story implementation with a red-green-refactor workflow until acceptance criteria pass.

36|16|Updated May 1, 2026
One-click install
npx skills add https://github.com/tronghieu/lumina-wiki --skill bmad-dev-story-tronghieu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-dev-story
Source: https://github.com/tronghieu/lumina-wiki/tree/main/.agents/skills/bmad-dev-story
Command: npx skills add https://github.com/tronghieu/lumina-wiki --skill bmad-dev-story-tronghieu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of turning a structured “story spec” into a correctly implemented, fully tested change set that meets acceptance criteria and is ready for review.

Core Features & Use Cases

  • Story-driven implementation: Executes tasks strictly in the order defined by the story’s Tasks/Subtasks and gates progress on completion and passing tests.
  • Sprint-aware workflow: Discovers the next “ready-for-dev” story from sprint-status.yaml (when available) or from story files (when not).
  • Review-continuation support: Resumes after code review by prioritizing unresolved [AI-Review] follow-ups from the story and review sections.
  • Traceable, auditable outputs: Updates only permitted story sections (checkboxes, Dev Agent Record, File List, Change Log, Status) and summarizes actual changes and tests for review readiness.
  • Quality and DoD validation: Enforces a definition-of-done checklist, including regression checks and documentation/tracking completeness.

Quick Start

Use the command “dev this story <full-path-to-story-file>.md” to implement the story described by the spec, run validations, and mark it ready for review.

Frequently Asked Questions about bmad-dev-story

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

FAQPage Schema
How do I automate story implementation from acceptance criteria using test-first development?

Automating story implementation requires driving a red-green-refactor workflow from a structured story specification, ensuring tests exist and pass before marking tasks complete. It enforces strict modification boundaries and deterministic step ordering to meet all acceptance criteria.

How does sprint status tracking find the next ready-for-dev story for implementation?

Sprint status tracking discovers the next ready-for-dev story by reading sprint-status.yaml files when available, or by scanning story files directly when sprint configuration is absent. It then executes tasks strictly in the order defined by the story's subtasks.

Can I resume story implementation after code review follow-ups?

Resuming story implementation after code review involves prioritizing unresolved [AI-Review] follow-ups from the story and review sections. The workflow resumes by applying changes strictly within permitted story sections until all review tasks pass validation.

What is the best way to enforce definition-of-done validation during dev workflow automation?

Definition-of-done validation enforces regression checks and documentation completeness by verifying that all tests pass without regressions before marking tasks complete. It updates only permitted story sections like checkboxes and Dev Agent Records for auditable outputs.

Does task tracking during story implementation restrict modifications to specific story sections?

Task tracking during story implementation requires strict modification boundaries limited to permitted story sections, including checkboxes, File List, Change Log, and Status. This ensures traceable, auditable outputs ready for review without altering the core specification.