bmad-dev-story

Execute end-to-end story implementation from spec loading through review.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/mschuerig/peach-ios --skill bmad-dev-story-mschuerig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-dev-story
Source: https://github.com/mschuerig/peach-ios/tree/main/_bmad/bmm/workflows/4-implementation/bmad-dev-story
Command: npx skills add https://github.com/mschuerig/peach-ios --skill bmad-dev-story-mschuerig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The workflow enables automatic end-to-end story implementation by loading a context-rich story spec and applying a repeatable Dev Story Workflow to execute tasks from initialization to review.

Core Features & Use Cases

  • Guided end-to-end story execution following a context-filled spec
  • Strict adherence to story structure, DoD requirements, and sprint status updates
  • Supports loading the next ready story from sprint-status or direct story files

Quick Start

Load the next ready story file and execute the full Dev Story Workflow from initialization to completion.

Frequently Asked Questions about bmad-dev-story

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate end-to-end story implementation from a sprint backlog?

You can automate story implementation by loading a context-rich story spec and executing the Dev Story Workflow to handle tasks from initialization through review and sprint-status updates.

What is the Dev Story Workflow process for ready-for-dev stories?

The Dev Story Workflow is an automated process that executes story implementation steps from initialization to completion, ensuring strict adherence to story structure, DoD requirements, and sprint status updates.

How do I ensure test scaffolding and change logs align with story specifications?

Automated story implementation ensures alignment by applying the workflow to execute test scaffolding, track file changes, generate change logs, and update sprint status according to the loaded story spec.

Do I need a specific story file format to start automated story implementation?

You need a context-rich story spec file; the workflow can load the next ready story directly from sprint-status files or from specific story files to begin the end-to-end implementation process.

Can I use this workflow for both story authoring and validation steps?

Yes, the workflow applies to scenarios where a sprint contains ready-for-dev stories and supports both authoring and validation steps required from initialization through Definition of Done and review.

What's the best way to handle code review and DoD requirements during story implementation?

Guided end-to-end story execution follows a context-filled spec to enforce strict adherence to Definition of Done requirements, code review steps, and sprint status updates throughout the workflow.