bmad-agent-dev

Implement approved enterprise stories using a test-first red/green/refactor workflow.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill bmad-agent-dev-enigmaicon-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-agent-dev
Source: https://github.com/enigmaicon-eng/AI-Enterprise-OS/tree/main/examples/BMAD-METHOD/src/bmm-skills/4-implementation/bmad-agent-dev
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill bmad-agent-dev-enigmaicon-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps users delegate story implementation to a disciplined developer persona that turns approved work into verified code that satisfies the acceptance criteria.

Core Features & Use Cases

  • Test-first story execution: Applies a red/green/refactor workflow while implementing the requested story.
  • Deterministic customization-driven activation: Resolves an agent configuration block from customize.toml plus layered team/user overrides to shape persona and execution steps.
  • Citable implementation planning: Uses file paths and acceptance-criterion (AC) IDs as its primary vocabulary to keep work traceable.
  • Context grounding via persistent facts and config: Loads session-long facts from configured file globs and uses config.yaml for language and planning artifact locations.

Quick Start

Invoke the bmad-agent-dev skill and ask it to implement the next story described in the repository context.

Frequently Asked Questions about bmad-agent-dev

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

FAQPage Schema
How do I implement user stories using test-first development?

Test-first development implements approved stories by applying a red, green, refactor workflow to ensure code satisfies acceptance criteria. A developer persona executes this workflow, iterating against acceptance-criterion IDs until all tests pass.

What is test-first story implementation and how does it keep code traceable?

Test-first story implementation is a workflow that turns approved work into verified code by writing tests before features. It keeps work traceable by using file paths and acceptance-criterion IDs as primary vocabulary throughout the process.

How do I resolve agent configuration and persona activation for story implementation?

Agent configuration is resolved by reading an agent configuration block from customize.toml and applying layered team or user overrides. This shapes the developer persona and execution steps before story work begins.

Do I need a customization file to activate the developer persona?

Yes, you need a customize.toml file to provide the agent configuration block. The system requires resolving this configuration plus layered overrides to shape the developer persona and execution steps before implementing stories.

How does persistent facts and config grounding work during story implementation?

Persistent facts and config grounding load session-long facts from configured file globs and use config.yaml. This provides language settings and planning artifact locations to the developer persona during story execution.