bmad-agent-dev

Execute approved development stories using a test-first red-green-refactor workflow.

Updated Sep 27, 2025
One-click install
npx skills add https://github.com/Cbanzaime23/Booking-System --skill bmad-agent-dev-cbanzaime23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-agent-dev
Source: https://github.com/Cbanzaime23/Booking-System/tree/main/.agent/skills/bmad-agent-dev
Command: npx skills add https://github.com/Cbanzaime23/Booking-System --skill bmad-agent-dev-cbanzaime23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Amelia embodies a disciplined software engineer persona who executes approved stories using a test-first approach, delivering verifiable code.

Core Features & Use Cases

  • Persona-driven execution: adopts the Amelia identity to drive consistent development workflow.
  • Test-first delivery: enforces red-green-refactor in story implementation.
  • Context-driven activation: loads customization, persistent facts, and a stable execution environment.

Quick Start

Activate Amelia and begin executing the next approved story using the test-first workflow.

Frequently Asked Questions about bmad-agent-dev

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

FAQPage Schema
How do I automate story execution with test-driven development?

Automate story execution using a test-first discipline by activating a persona-driven workflow that enforces red-green-refactor. This ensures verifiable, deterministic code delivery for approved development stories.

What is test-first delivery in software engineering story implementation?

Test-first delivery is a development discipline enforcing red-green-refactor during story implementation. It requires writing tests before code, ensuring every approved story produces deterministic, verifiable outputs through a structured activation pipeline.

How do I load context from YAML frontmatter for AI-driven development workflows?

Load context from YAML frontmatter by satisfying frontmatter-driven context loading within your execution environment. This mechanism adapts personas and injects persistent facts to drive consistent software engineering workflows.

Does this test-driven story execution approach work for teams needing deterministic code delivery?

Yes, test-driven story execution is designed for teams adopting formal development workflows requiring deterministic, verifiable code delivery. It enforces a test-first discipline to guarantee structured and predictable software engineering outcomes.

Can I adapt AI personas dynamically when executing approved software stories?

Yes, you can adapt AI personas dynamically during story execution. The workflow supports persona adaptation, allowing the system to adopt specific identities like Amelia to drive consistent development and testing behaviors.

What are the limitations of persona-driven story execution in software engineering?

Persona-driven story execution is limited to approved stories within a formal development workflow. It requires a stable execution environment and strict adherence to test-first discipline, making it unsuitable for unstructured or exploratory coding tasks.