bmad-build-auto

Runs one unattended development iteration from intent through planning, implementation, and multi-layer review.

52.5k|6.0k|Updated Apr 13, 2025
One-click install
npx skills add https://github.com/bmad-code-org/BMAD-METHOD --skill bmad-build-auto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-build-auto
Source: https://github.com/bmad-code-org/BMAD-METHOD/tree/main/src/bmm-skills/ship/bmad-build-auto
Command: npx skills add https://github.com/bmad-code-org/BMAD-METHOD --skill bmad-build-auto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Turning a change request into verified, reviewed code normally requires constant human supervision of an AI coding session. This Skill automates one full unattended development loop: it clarifies intent, writes a development-ready spec, implements it via a subagent, and runs multiple independent review layers before committing.

Core Features & Use Cases

  • Intent-to-Spec Planning: Resolves the invocation intent (free-form text, story ID, or existing spec file), loads planning artifacts like PRDs and architecture docs, and produces a structured spec with an intent contract, code map, tasks, and acceptance criteria.
  • Autonomous Implementation and Verification: Hands the spec to a context-free implementation subagent, stages a unified diff, runs the spec's verification commands, and audits that every I/O edge-case matrix row has a passing test.
  • Multi-Layer Automated Review: Launches parallel reviewer subagents (blind hunter, edge-case hunter, verification-gap reviewer, intent-alignment auditor), triages every finding into intent_gap, bad_spec, patch, or defer routes, and loops back to re-derive code when the spec is at fault.
  • Use Case: Point it at a story in an epic's stories.yaml file; it compiles epic context, plans, implements, reviews, fixes, and commits the change, halting with a structured status (done, blocked, ready-for-dev) and a full audit trail in the spec file.

Quick Start

Invoke bmad-build-auto with a description of the change you want, such as asking it to implement a specific story or fix, and let it run the full unattended loop to completion.

Frequently Asked Questions about bmad-build-auto

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

FAQPage Schema
How do I run an unattended AI development loop on a change request?

Invoke bmad-build-auto with your intent as the prompt — a free-form description, a story ID, or a path to an existing spec file. It clarifies the intent, writes a spec, implements it via a subagent, runs review layers, and commits the result without asking questions.

How does automated code review work in this workflow?

Step 4 stages a unified diff and launches parallel reviewer subagents: a blind hunter, an edge-case path tracer, a verification-gap reviewer, and an intent-alignment auditor. Every finding is verified against the code, assigned a verdict, and routed to patch, spec amendment, deferral, or rejection.

Can I dispatch a single story from an epic automatically?

Yes. Supply a spec folder and story ID; the skill reads stories.yaml, resolves the entry, loads the epic SPEC.md and cross-story context from sibling story files, and processes exactly that one story. It never advances to other story IDs.

What happens when the automated review finds problems?

Findings are triaged by root cause: trivial issues are auto-patched and re-verified, spec-level defects trigger a spec amendment and full code re-derivation, and pre-existing issues are deferred into the spec frontmatter. More than five repair loops halts the run as blocked.

When does the build loop stop and what statuses does it report?

The loop HALTs with an explicit terminal status: done after a clean reviewed commit, ready-for-dev if asked to stop after planning, or blocked with a specific blocking condition such as unclear intent, a dirty working tree, or failed verification. Results are written to the spec file's Auto Run Result section.