bmad-agent-dev

Execute approved software development stories with test-driven validation and documentation.

1|Updated Aug 3, 2025
One-click install
npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-agent-dev-mazenmrad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-agent-dev
Source: https://github.com/MazenMrad/Obsidio/tree/main/.cursor/skills/bmad-agent-dev
Command: npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-agent-dev-mazenmrad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a dedicated developer agent that executes approved software stories with strict adherence to given details, team standards, and test-driven expectations.

Core Features & Use Cases

  • End-to-end story execution and validation against acceptance criteria.
  • Test-driven development workflow with rigorous unit tests and automatic verification before marking tasks complete.
  • Documentation and decision-tracking updates to the story file after each task, ensuring traceability.

Quick Start

Tell Amelia to execute the next approved story, run the tests, and report results before proceeding.

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?

Automated story execution applies test-driven development by implementing approved tasks, writing rigorous unit tests, and running full test-suite verification before marking tasks complete.

What is the best way to ensure code implementation meets acceptance criteria?

End-to-end story execution validates code implementation against acceptance criteria by enforcing strict adherence to story details, team standards, and test-driven expectations.

How do I document decisions and track changes during story execution?

Story execution tracks changes by updating the story file with documentation and decision evidence after each task, ensuring full traceability across the development lifecycle.

Does test-driven development work for automating approved software development stories?

Test-driven development automates approved software stories by requiring rigorous unit tests and automatic verification, ensuring full test-suite validation before task completion.

Why does story execution require full test-suite verification after each task?

Full test-suite verification after each task ensures code implementation maintains strict quality assurance and adheres to test-driven development expectations before proceeding.