bmad-dev-story

Implements sprint stories from spec files using red-green-refactor cycles and definition-of-done validation.

1|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/SevWren/Daily-Motivation-Brain-Helper --skill bmad-dev-story-sevwren
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-dev-story
Source: https://github.com/SevWren/Daily-Motivation-Brain-Helper/tree/main/.claude/skills/bmad-dev-story
Command: npx skills add https://github.com/SevWren/Daily-Motivation-Brain-Helper --skill bmad-dev-story-sevwren

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It automates the disciplined execution of a development story: finding the next ready story in sprint status, implementing each task with tests, and marking the story ready for review without skipping steps or stopping early. ## Core Features & Use Cases - Story Discovery & Status Tracking: Locates the next ready-for-dev story from sprint-status.yaml or story files and updates statuses through in-progress to review. - Test-Driven Implementation: Executes each task following a red-green-refactor cycle, runs full regression suites, and enforces strict validation gates before checking off tasks. - Review Continuation: Detects prior senior developer review sections and prioritizes unresolved review follow-up items before continuing regular tasks. - Use Case: A developer on a BMad-managed project invokes the workflow to pick up the next sprint story, implement all tasks with tests, and hand it off for code review in one continuous run. ## 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 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 full context, then implements every task in order with tests until all acceptance criteria are satisfied.

How does the 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 checked off after all tests exist and pass.

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 by severity, and prioritizes resolving those items before continuing with remaining regular tasks.

What happens if no ready-for-dev story exists?

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.

When does the workflow stop before completing a story?

It halts only on explicit conditions: ambiguous task requirements, missing configuration, new dependencies needing approval, three consecutive implementation failures, or failing validation gates. It does not pause for milestones or session boundaries.