bmad-dev-story

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

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-dev-story-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-dev-story
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/bmad-dev-story
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-dev-story-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It automates the disciplined implementation of a development story by locating the next ready story, executing its tasks in order with test-driven development, and updating sprint tracking until the story is ready for review. ## Core Features & Use Cases - Story Discovery: Finds the next story marked ready-for-dev in sprint-status.yaml or scans story files directly. - TDD Execution: Implements each task following a red-green-refactor cycle with unit, integration, and end-to-end tests. - Review Continuation: Detects prior code review findings and resolves pending review follow-up tasks before continuing. - Use Case: A developer asks the agent to implement the next sprint story; the skill loads the story spec, writes failing tests, implements the code, runs the full regression suite, and marks the story as review in sprint-status.yaml. ## Quick Start Implement the next ready-for-dev story from my sprint status file using test-driven development.

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 skill and it reads sprint-status.yaml to find the first story marked ready-for-dev, loads its full specification, then implements each task using a red-green-refactor cycle until all acceptance criteria pass.

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

Each task follows red-green-refactor: write failing tests first, implement minimal code to pass them, then refactor while keeping tests green. The workflow halts if tests fail or regressions appear.

Can it resume a story after a code review?

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

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

The workflow stops and offers options: run create-story to draft the next story, run validate-create-story for a quality check, or provide a specific story file path to develop.

When should I not use this skill?

This skill is deprecated in favor of bmad-build, which is the official implementation method. Only use it when explicitly invoked by name for legacy BMAD workflows.