bmad-dev-story

Execute the BMAD Dev Story workflow for planning, coding, testing, and status updates.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/KatTate/Bmad-for-Replit --skill bmad-dev-story
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-dev-story
Source: https://github.com/KatTate/Bmad-for-Replit/tree/main/.agents/skills/bmad-dev-story
Command: npx skills add https://github.com/KatTate/Bmad-for-Replit --skill bmad-dev-story

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the entire workflow for implementing a development story, from planning and coding to testing and final status updates, ensuring all project management artifacts are kept current.

Core Features & Use Cases

  • End-to-End Workflow: Manages the complete lifecycle of a development story implementation.
  • Automated Tracking: Ensures story and sprint statuses are consistently updated.
  • Use Case: When a new story is assigned, this Skill guides the agent through building, testing, and verifying the implementation, then automatically updates the project board and notifies stakeholders.

Quick Start

Use the bmad-dev-story skill to implement the story described in the attached file 'story-123.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 automate the development story implementation workflow from planning to testing?

Automating development story implementation requires a structured workflow that handles planning, coding, testing, and verification. This Skill executes an 11-step process to manage the complete lifecycle and automatically update sprint and story statuses.

What is the BMAD Dev Story process for agile project management?

The BMAD Dev Story process is a strict 11-step workflow defined in configuration files for implementing development tasks. It ensures all project management artifacts are kept current by automating tracking from coding to final sprint status updates.

How do I update sprint and story statuses automatically after coding and testing?

Updating sprint and story statuses automatically is handled by executing the development workflow's verification phase. Once coding and testing are complete, the workflow updates the project board and notifies stakeholders of the implementation results.

Do I need workflow configuration files to implement development stories?

Workflow configuration files are required to implement development stories using this Skill. Adherence to a strict 11-step process defined in these configuration files ensures proper planning, coding, testing, and status updates throughout the implementation lifecycle.

Can I use this workflow for end-to-end agile story implementation and stakeholder notification?

End-to-end agile story implementation is supported by this workflow, covering the complete lifecycle from planning to final status updates. It automatically updates the project board and notifies stakeholders upon successful verification of the implementation.

What are the limitations of automating development story workflows with a strict step process?

The limitation of automating development story workflows with a strict 11-step process is the required adherence to the defined configuration files. Deviating from the structured planning, coding, testing, and verification sequence may disrupt the automated sprint and story status updates.