bmad-dev

Automate story implementation by writing code and running tests from story files.

67|11|Updated Oct 28, 2025
One-click install
npx skills add https://github.com/bacoco/BMad-Skills --skill bmad-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-dev
Source: https://github.com/bacoco/BMad-Skills/tree/main/.claude/skills/bmad-dev
Command: npx skills add https://github.com/bacoco/BMad-Skills --skill bmad-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the development process by automating code implementation, rigorous testing, and transparent progress updates. It ensures that stories are completed efficiently, correctly, and in strict adherence to defined criteria, reducing manual effort and errors.

Core Features & Use Cases

  • Iterative Implementation: Writes code patches, following architectural patterns and strict acceptance criteria, ensuring consistency and quality.
  • Relentless Testing: Executes unit, integration, and end-to-end tests, capturing command outputs verbatim to prove functionality.
  • Transparent Documentation: Continuously updates the Dev Agent Record within story files, detailing changes, learnings, and follow-ups for full traceability.
  • Use Case: A product manager has a "ready" story in the sprint tracker. This Skill takes the story, implements the necessary code changes, writes and runs all required tests, and updates the story's status and development log, making it ready for review or deployment.

Quick Start

Implement story "1-2-user-authentication" using the provided architecture and acceptance criteria.

Frequently Asked Questions about bmad-dev

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

FAQPage Schema
How do I automate story implementation with code generation and testing?

Story automation implements code patches from developer-ready story files, executes unit and integration tests, and captures outputs to validate acceptance criteria. The Skill handles end-to-end implementation when architecture references and test scenarios are defined in the story file.

What's required before I can use this Skill to implement a story?

Your story file must be in Phase 4 with defined acceptance criteria, architecture references, test scenarios, and planning details. The Skill requires an existing story structure; it does not create stories or design architecture from scratch.

How does this Skill track development progress and changes?

The Skill continuously updates the Dev Agent Record within your story file, logging code changes, test results, learnings, and follow-ups. All command outputs are captured verbatim to provide full traceability of implementation decisions.

Can this automate testing across all acceptance criteria?

Yes. The Skill writes and executes tests for each acceptance criterion, enforcing test coverage and running unit, integration, and end-to-end tests. It validates functionality against criteria before marking implementation complete.

What happens after the Skill completes code implementation?

The story is ready for code review or deployment with a fully updated Dev Agent Record. All tests pass, coverage is documented, and implementation notes are logged for handoff to review or release processes.

Does this Skill follow existing architectural patterns in my codebase?

Yes. The Skill enforces strict adherence to defined architectural patterns and quality references supplied in your story file, ensuring consistency across code patches and reuse of existing interfaces.