bmad-dev

Automate dev agent activation and configuration via a predefined script.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables reliable activation and management of a dev agent persona, ensuring consistent behavior and adherence to activation steps.

Core Features & Use Cases

  • Activation flow: deterministic and repeatable provisioning of the dev agent persona.
  • Persona fidelity: maintains the agent's developer-centric behavior across sessions.
  • Guided interaction: presents a structured menu and waits for user input to proceed.

Quick Start

Load the full agent file from {project-root}/_bmad/bmm/agents/dev.md and follow the activation steps exactly.

Frequently Asked Questions about bmad-dev

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

FAQPage Schema
How do I automate the activation of a development agent persona?

You can automate dev agent activation by loading a predefined persona file and following a deterministic activation script that presents a menu and solicits user input. This ensures the agent follows consistent provisioning steps.

What is a menu-guided workflow for dev agents?

A menu-guided workflow is a deterministic activation process where a dev agent presents a structured menu and waits for user input. It ensures persona fidelity and repeatable behavior across software development automation sessions.

How do I maintain consistent behavior for a dev agent across sessions?

To maintain dev agent consistency, use an activation flow that loads external persona data from a Markdown file. This enforces deterministic, repeatable provisioning so the developer-centric behavior remains stable across sessions.

Can I use a YAML frontmatter script to configure a dev agent?

Yes, the activation workflow uses a YAML frontmatter containing the name and description to define the dev agent. This configuration automates the loading of external persona data and initiates a menu-guided interaction.

Do I need a specific project structure to load an agent persona file?

You need to load the agent file from your project's root directory, specifically the _bmad/bmm/agents/dev.md path. The activation workflow relies on this external persona file to function correctly.

What are the limitations of using a deterministic activation script for dev agents?

The deterministic activation script requires a fixed project file path and follows a rigid menu-guided flow. It cannot adapt if the external persona Markdown file is missing or moved from the expected project root location.