bmad-dev-story

Implements BMad story files through a test-driven development workflow with sprint status tracking.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill bmad-dev-story-watchthelight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-dev-story
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/bmad-dev-story
Command: npx skills add https://github.com/watchthelight/shatterfish --skill bmad-dev-story-watchthelight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It automates the execution of BMad story specifications, taking a ready-for-dev story file and driving it to completion with tests, validation gates, and status updates, without losing track of tasks or acceptance criteria. ## Core Features & Use Cases - Story Discovery and Loading: Finds the next ready-for-dev story from sprint-status.yaml or the implementation artifacts directory, or accepts an explicit story path. - Red-Green-Refactor Implementation: Executes each task and subtask with failing tests first, minimal passing implementation, then refactoring, with HALT conditions for failures. - Review Continuation: Detects prior Senior Developer Review sections and prioritizes unresolved review follow-up items before regular tasks. - Definition-of-Done Validation: Applies a strict checklist covering tests, file lists, change logs, and acceptance criteria before marking the story as review. - Use Case: A developer on a BMad-managed project invokes the workflow to pick up the next sprint story, implement all tasks with tests, update sprint-status.yaml to review, and receive a completion summary. ## Quick Start Ask the assistant 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 a BMad story file automatically?

Invoke the workflow with an explicit story path or let it discover the first ready-for-dev story in sprint-status.yaml. It loads the story's tasks, Dev Notes, and acceptance criteria, then implements each task with tests until all are checked complete.

How does the dev story workflow handle code review follow-ups?

It detects a Senior Developer Review section in the story file, counts unchecked action items by severity, and prioritizes those review follow-up tasks before regular tasks. Resolved items are marked in both the review section and the task list.

Does the workflow support projects without sprint-status.yaml?

Yes. When no sprint status file exists, it searches the implementation artifacts directory for story files with ready-for-dev status and tracks progress only within the story file itself.

What happens when story implementation fails repeatedly?

The workflow halts after three consecutive implementation failures and requests user guidance. It also halts on missing configuration, unapproved new dependencies, or failing regression tests rather than marking tasks complete.

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

This skill is deprecated in favor of bmad-build, which is the official implementation method. Use bmad-dev-story only when explicitly invoked by name for legacy BMad workflows.