bmad-agent-dev

Executes approved development stories with test-driven implementation and acceptance criteria tracking.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Wizarck/nexandro --skill bmad-agent-dev-wizarck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-agent-dev
Source: https://github.com/Wizarck/nexandro/tree/main/skills/bmad-agent-dev
Command: npx skills add https://github.com/Wizarck/nexandro --skill bmad-agent-dev-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Development stories often get implemented inconsistently, with skipped tasks, missing tests, or undocumented changes. This Skill embodies Amelia, a senior software engineer persona that executes approved stories with strict adherence to task order, test coverage, and documentation requirements. ## Core Features & Use Cases - Story Execution: Reads the full story file and implements tasks/subtasks in exact order, marking each complete only when code and tests pass. - Test-Driven Discipline: Runs the full test suite after each task and refuses to proceed with failing tests. - Capability Routing: Dispatches to related workflows like story creation, code review, sprint planning, and E2E test generation via menu codes. - Use Case: A developer finishes sprint planning and asks the agent to implement the next story; the agent loads project config, executes each task with tests, and updates the story file's Dev Agent Record and File List. ## Quick Start Ask the agent to implement the next approved story from the sprint plan and run all tests before marking tasks complete.

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 a development story with an AI agent?▼

Provide an approved story file containing ordered tasks and acceptance criteria. The agent reads the entire story first, implements tasks in sequence, writes unit tests for each, and marks items complete only when all tests pass.

What is test-driven story execution in agile workflows?▼

Test-driven story execution means every task or subtask gets comprehensive unit tests before being marked complete, and the full test suite runs after each task. The agent never proceeds with failing tests or claims tests pass when they do not.

Can this agent generate E2E tests and do code reviews?▼

Yes, the capabilities table routes to related workflows: QA generates API and E2E tests for existing features, and CR initiates a comprehensive code review across multiple quality facets. These are invoked via menu codes.

What configuration does the developer agent need to start?▼

The agent loads config from _bmad/bmm/config.yaml at the project root, resolving user name, communication language, output language, and planning artifact locations. It also searches for project-context.md for standards and conventions.

What are the limitations of automated story execution?▼

The agent depends on well-written story files with clear task sequencing and acceptance criteria. Ambiguous or incomplete stories reduce execution quality, and the agent will not invent capabilities beyond its registered skill list.