bmad-dev-story

Execute end-to-end software development tasks using a test-driven workflow.

Updated May 13, 2026
One-click install
npx skills add https://github.com/Markuson/ivo_corr --skill bmad-dev-story-markuson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-dev-story
Source: https://github.com/Markuson/ivo_corr/tree/main/.agents/skills/bmad-dev-story
Command: npx skills add https://github.com/Markuson/ivo_corr --skill bmad-dev-story-markuson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the challenge of maintaining consistency and rigor during software development by enforcing a strict, step-by-step implementation workflow that ensures all acceptance criteria are met and documented.

Core Features & Use Cases

  • Structured Workflow: Executes a predefined, multi-step development process including context loading, test-driven development, and validation.
  • Sprint Integration: Automatically tracks story progress within sprint status files to maintain project-wide visibility.
  • Quality Assurance: Enforces a rigorous definition-of-done checklist, ensuring that every task is validated, tested, and documented before completion.

Quick Start

Invoke the bmad-dev-story skill to begin implementing the next story in the sprint plan by providing the path to your story 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 automate test-driven development for sprint stories?

Automated test-driven development for sprint stories is achieved by executing a structured, multi-step implementation workflow that loads story context, implements tasks, and updates sprint status files to ensure all acceptance criteria are met.

What is a structured workflow for managing story lifecycle and definition of done?

A structured story lifecycle workflow manages development from initial context loading through test-driven implementation to final validation. It enforces a rigorous definition-of-done checklist, ensuring every task is validated, tested, and documented before sprint completion.

Can I enforce acceptance criteria and quality assurance checks during automated coding?

Enforcing acceptance criteria during automated coding is handled by a strict step-by-step implementation process. It validates every task against a definition-of-done checklist, ensuring all requirements are tested and documented before marking the story complete.

Does this automated development workflow require specific project configuration files?

Yes, automated development workflow requires adherence to specific project-wide configuration files. Strict compliance with these defined development steps and configurations is necessary to maintain consistency and execute the end-to-end software tasks properly.

How do I integrate automated task execution with sprint status tracking?

Integrating automated task execution with sprint tracking is done by automatically updating sprint status files as stories progress. This maintains project-wide visibility by linking the test-driven implementation workflow directly to sprint management.