bmad-master_skill

This skill orchestrates BMAD Method workflows, manages phases, and coordinates agents to streamline agile AI-driven development.

Shell

215

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill aj-geddes/claude-code-bmad-skills --skill bmad-master

SKILL.md5.9 KB

Overview

This skill is the core BMAD Method orchestrator and workflow manager that sets up, monitors, and advances projects through the BMAD v6 phases. It initializes project structure, maintains status files, and routes work to specialized agents so teams can follow a consistent, trackable AI-driven development process.

How this skill works

The orchestrator inspects project configuration and a workflow status file, then determines the current phase and recommended next steps using built-in helpers. It can initialize BMAD layout and config, update and report status, and hand off tasks to specialized agents (Analyst, PM, Architect, Developer, Scrum Master) to execute phase-specific workflows. Commands include /workflow-status to view project state and recommendations, and /workflow-init to bootstrap BMAD for a repository.

When to use it

Starting a new project and you need a BMAD-compliant directory, config, and status tracking.
Checking project progress to know which BMAD phase and workflows are next.
Routing work to the right specialist agent (product, architecture, sprint, development).
Enforcing consistent methodology for multi-stage AI-driven development efforts.
Recovering from missing or invalid configuration and needing guided reinitialization.

Best practices

Run /workflow-init at project start to create bmad/, docs/, and initial status files.
Keep project level accurate (0–4) so conditional workflows and requirements are applied correctly.
Use helpers for config and status operations to minimize token usage and keep responses concise.
Confirm recommended workflow before execution and let specialized agents handle detailed tasks.
Treat the status file as the single source of truth and update it after each completed workflow.

Example use cases

Initialize BMAD for a new web app, then run the Planning workflows to generate a PRD.
Query /workflow-status on a Level 2 project to reveal that PRD is required and trigger /prd.
Hand off architecture work to the System Architect when a project reaches Solutioning.
Start sprint planning and create stories via the Scrum Master after Implementation is unlocked.
Recover from invalid YAML by offering reinitialization or targeted fixes and continuing setup.

FAQ

Use /workflow-status (or /status) to check progress and recommendations, and /workflow-init (or /init) to initialize BMAD in the current project.

How does project level affect workflows?

Project level (0–4) controls which artifacts are required or optional—e.g., higher levels require PRDs and architecture steps, while smaller levels may only recommend them.

What happens if templates or config are missing?

The orchestrator uses inline fallbacks, logs a warning, and offers reinitialization or guidance to fix missing templates or invalid YAML.