bmad-bmm-dev-story

Execute a structured dev-story workflow from a story spec file.

1|1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/LucaDeLeo/ASTN --skill bmad-bmm-dev-story-lucadeleo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-bmm-dev-story
Source: https://github.com/LucaDeLeo/ASTN/tree/main/.agents/skills/bmad-bmm-dev-story
Command: npx skills add https://github.com/LucaDeLeo/ASTN --skill bmad-bmm-dev-story-lucadeleo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute story implementations from a context-filled story spec file to automate sprint workflows and ensure consistent delivery.

Core Features & Use Cases

  • Load and run the full core OS workflow defined in {project-root}/_bmad/core/tasks/workflow.xml.
  • Apply the specific dev-story workflow config located at _bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml.
  • Save outputs after each section to preserve traceability and reproducibility.

Quick Start

Dev this story <story-file> by loading the full workflow and applying the workflow configuration.

Frequently Asked Questions about bmad-bmm-dev-story

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

FAQPage Schema
How do I automate story implementation from a spec file for sprint execution?

To automate story implementation, you load a story spec file and execute a structured dev-story workflow. This applies deterministic execution to story-driven development tasks, ensuring consistent sprint delivery and automated quality checks.

What is a dev-story workflow and how does it guide automated project execution?

A dev-story workflow is a structured execution process driven by a story spec file. It guides automated project execution by loading core workflow configurations and applying specific implementation rules to ensure deterministic task completion.

Do I need specific workflow configuration files to run automated story implementation?

Yes, automated story implementation requires loading core workflow XML and specific dev-story workflow YAML configuration files. These files must be located in the project root directory to define the execution rules and output saving behavior.

Can I use this automated dev-story workflow for sprint implementation and quality checks?

Yes, the dev-story workflow is designed for story-driven development tasks including sprint implementation and quality checks. It executes the workflow deterministically from a spec file and saves outputs after each section.

How are workflow outputs preserved during automated story execution?

Workflow outputs are preserved by saving them after each section of the dev-story workflow completes. This approach maintains traceability and reproducibility throughout the automated sprint implementation process.

What's the best way to execute a structured development story from a specification document?

The best way to execute a development story is to load the full core workflow and apply the specific dev-story workflow configuration. This automates the implementation process from the spec file while ensuring consistent delivery.