bmad-dev-story

Implement story tasks via red-green-refactor with test and acceptance-criteria validation.

4|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/curdx/curdx-flow --skill bmad-dev-story-curdx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-dev-story
Source: https://github.com/curdx/curdx-flow/tree/main/.agents/skills/bmad-dev-story
Command: npx skills add https://github.com/curdx/curdx-flow --skill bmad-dev-story-curdx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It prevents Claude Code story implementations from drifting across restarts and from falsely claiming completion without tests and acceptance-criteria verification.

Core Features & Use Cases

  • Sprint-aware story discovery & routing: Selects the next ready-for-dev story from sprint-status.yaml (or discovers candidates when sprint tracking is absent) and loads the full story context.
  • Red-green-refactor implementation loop: Drives each task/subtask through failing tests first, minimal implementation to pass, then refactoring while staying aligned to the story’s Dev Notes.
  • Strict completion validation: Blocks task completion unless tests exist and pass, acceptance criteria are satisfied, file lists are updated, and definition-of-done checks succeed.
  • Code-review continuation support: Detects “Senior Developer Review (AI)” follow-ups and prioritizes unresolved review items labeled for follow-up.

Quick Start

Say: dev this story path/to/your-story.md, and the workflow will implement the next incomplete task until the story is fully complete and marked 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 prevent story implementation drift across Claude Code sessions?

Story implementation drift is prevented by executing tasks using a context-filled story spec with strict red-green-refactor sequencing and mandatory test validation. This ensures incomplete handoffs and falsely claimed completions are blocked across restarts.

How do I automate test-driven development for story tasks using a sprint plan?

Automate test-driven development by selecting the next ready-for-dev story from sprint-status.yaml and driving each subtask through a failing test first, minimal implementation to pass, then refactoring aligned to Dev Notes.

Does story implementation enforce acceptance criteria validation before completion?

Yes, strict completion validation blocks task completion unless tests exist and pass, acceptance criteria are satisfied, file lists are updated, and definition-of-done checks succeed.

How do I handle code review follow-ups within the story implementation workflow?

Code review follow-ups are handled by detecting Senior Developer Review items and prioritizing unresolved review items labeled for follow-up, ensuring continuation support within the story workflow.

Can I restrict code modifications to specific story sections during implementation?

Yes, the workflow enforces controlled, story-section-only file modifications, ensuring changes remain scoped strictly to the story being implemented and preventing unintended edits outside the story boundaries.