bmad-agent-dev

Execute approved software stories with test-first discipline and acceptance mapping.

4|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/curdx/curdx-flow --skill bmad-agent-dev-curdx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-agent-dev
Source: https://github.com/curdx/curdx-flow/tree/main/.agents/skills/bmad-agent-dev
Command: npx skills add https://github.com/curdx/curdx-flow --skill bmad-agent-dev-curdx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps implement approved stories by enforcing a test-first workflow that produces verifiable, acceptance-checked code instead of unvalidated output.

Core Features & Use Cases

  • Resolution + execution pipeline: resolves the active agent configuration by merging customize.toml with project-level team and user overrides, then runs configured activation steps.
  • Persona and session invariants: locks Amelia’s identity, communication style, principles, and persistent facts so the implementation stays consistent across the whole session.
  • Acceptance-driven delivery: routes work via a structured menu (tests+code, quick flow, QA/E2E generation, code review, sprint planning, story creation, retrospective) to support story execution from specification to verification.

Quick Start

Invoke Amelia by starting with the story you want implemented, for example: "Amelia, implement the next approved story from the requirements with tests first, then deliver the verified code."

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 approved software stories with test-first discipline?▼

Test-first story implementation executes approved specifications by generating tests before code, producing verifiable, acceptance-mapped changes. It enforces TDD discipline to deliver validated output.

Can I generate E2E and QA tests from acceptance criteria automatically?▼

Yes, QA and E2E test generation routes directly from acceptance criteria. The system generates targeted tests to verify story implementation and ensure acceptance-mapped code changes.

What is the best way to sequence sprints and triage stories for implementation?▼

Sprint sequencing and story triage are supported through a structured routing menu. This allows planning, creating, and sequencing stories to determine execution order before test-first development.

How does multi-facet code review work during story implementation?▼

Multi-facet code review evaluates implemented stories against acceptance criteria and persistent project facts. This verifies code changes maintain session invariants and meet specified acceptance maps.

Do I need to resolve agent configuration files before implementing stories?▼

Yes, the pipeline merges customize.toml with project-level team and user overrides to resolve the active agent configuration. Pre and post activation steps must complete before executing stories.

How do I maintain consistent persona identity across a story implementation session?▼

Session invariants lock agent identity, communication style, principles, and persistent facts loaded from project files. This ensures test-first implementation stays consistent across the entire session.