bmad-dev-story

Implements user stories from sprint status files using a red-green-refactor test-driven workflow.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-dev-story-tuanpa-nhg-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-dev-story
Source: https://github.com/tuanpa-nhg-eng/nhg-ipms/tree/main/.claude/skills/bmad-dev-story
Command: npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-dev-story-tuanpa-nhg-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill automates the disciplined implementation of development stories by discovering ready-for-dev stories, executing tasks in order with test-driven development, and enforcing a strict definition-of-done before marking work ready for review. ## Core Features & Use Cases - Story Discovery & Tracking: Finds the next ready-for-dev story from sprint-status.yaml or story files, updates statuses (in-progress → review), and records baseline git commits. - Test-Driven Implementation: Executes each task following a red-green-refactor cycle, writes unit/integration/e2e tests, and runs full regression suites before marking tasks complete. - Review Continuation: Detects prior code review findings, prioritizes unresolved review follow-up tasks, and tracks their resolution. - Use Case: A developer on a BMad-managed project invokes this Skill to pick up the next sprint story, implement all its tasks with passing tests, and hand it off for code review in a single uninterrupted run. ## Quick Start Ask the AI to run the bmad-dev-story workflow to implement the next ready-for-dev story from the sprint status file.

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 sprint story automatically?

Invoke the workflow and it reads sprint-status.yaml to find the first story marked ready-for-dev, loads its tasks and dev notes, then implements each task with tests until all acceptance criteria are satisfied and the status is set to review.

How does the dev story workflow handle test-driven development?

Each task follows a red-green-refactor cycle: failing tests are written first, minimal code makes them pass, then the code is refactored while keeping tests green. A task is only marked complete when all its tests exist and pass with no regressions.

Can I resume a story after a code review?

Yes. The workflow detects a Senior Developer Review section in the story file, counts unchecked review follow-up tasks by severity, and prioritizes resolving those items before continuing with remaining regular tasks.

What happens if no ready-for-dev story is found?

The workflow halts and offers options: run create-story to draft the next story, run validate-create-story for a quality check, provide a specific story file path, or review the current sprint status in detail.

When should I use bmad-dev-story versus bmad-build?

This skill is deprecated; bmad-build is the official implementation method. Only use bmad-dev-story when it is explicitly invoked by name, as stated in its own description.