bmad-dev-story

Implement developer stories end-to-end with tests and sprint status updates.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill bmad-dev-story-enigmaicon-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-dev-story
Source: https://github.com/enigmaicon-eng/AI-Enterprise-OS/tree/main/examples/BMAD-METHOD/src/bmm-skills/4-implementation/bmad-dev-story
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill bmad-dev-story-enigmaicon-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of turning a developer-ready story specification into a complete, test-validated implementation with correct sprint and review workflow updates.

Core Features & Use Cases

  • Story-driven, task-ordered implementation: Executes story Tasks/Subtasks strictly in the defined sequence using a red-green-refactor approach.
  • Context-aware development: Loads project context and story Dev Notes to guide architecture, technical requirements, and implementation decisions.
  • Validation-gated completion: Runs regressions and enforces a definition-of-done checklist before marking tasks complete and setting story status to review.
  • Sprint status orchestration: Updates sprint-status.yaml (when present) from ready-for-dev/in-progress to review in a controlled manner.
  • Review continuation support: Detects and prioritizes AI review follow-up tasks when a “Senior Developer Review (AI)” section is present.

Quick Start

Ask to run dev this story using the provided story spec file, for example: dev this story path/to/story.md.

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 developer story from a specification file?

Story implementation from a specification file executes tasks and subtasks in strict sequence using a red-green-refactor approach. It loads project context and Dev Notes to guide architecture decisions before running validation tests.

What is red-green-refactor test validation in story implementation?

Red-green-refactor test validation in story implementation requires writing failing tests first, making them pass with implementation code, then refactoring. This approach gates task completion behind successful regression runs and definition-of-done checklist enforcement.

How do I update sprint status after completing story implementation?

Sprint status updates happen automatically by modifying sprint-status.yaml from ready-for-dev or in-progress to review. This controlled status orchestration occurs only after definition-of-done validation passes successfully.

Can I continue development after a senior developer code review?

Review continuation is supported when a Senior Developer Review section is present in the story specification. The implementation detects and prioritizes AI review follow-up tasks to resolve feedback before completing the story.

Does story implementation work for ad-hoc development outside of sprints?

Story implementation applies to both sprint-based and ad-hoc development workflows. Sprint status orchestration only modifies sprint-status.yaml when the file is present, leaving standalone task execution unaffected otherwise.

What are the limitations of controlled story section modification?

Controlled story section modification limits edits to only allowed sections of the story specification, preventing unauthorized changes to task definitions or structural metadata while permitting Dev Notes and status updates.