bmad-build-auto

Executes one unattended development loop from intent through planning, implementation, and multi-layer review.

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-build-auto-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-build-auto
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/bmad-build-auto
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-build-auto-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a raw feature request or story into reviewed, verified code normally requires constant human supervision across planning, coding, and review. This Skill runs one full unattended development iteration: it clarifies intent, writes a development-ready spec, implements it via a subagent, and runs layered code reviews with automated triage and repair loops. ## Core Features & Use Cases - Intent-to-Spec Planning: Resolves intent from prompts, epic stories, or existing spec files, compiles epic context from planning artifacts, and produces a structured spec with code maps, acceptance criteria, and verification commands. - Autonomous Implementation: Hands the spec to a context-free implementation subagent, then runs the spec's verification commands and audits edge-case matrix test coverage. - Multi-Layer Review with Triage: Runs parallel review layers (blind hunter, edge-case hunter, verification-gap, intent-alignment), classifies findings into intent_gap/bad_spec/patch/defer/reject, and loops repairs up to five iterations before committing. - Use Case: Point it at a story in stories.yaml or describe a feature; it produces a committed, reviewed change with a spec file recording the full run result, triage log, and deferred findings. ## Quick Start Invoke bmad-build-auto with a feature description or a spec folder and story id to run one unattended plan-implement-review iteration.

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 development loop on a story?

Invoke the skill with a spec folder and story id, or with free-form intent. It routes through clarify, plan, implement, and review steps, writing results and status into the story's spec file before halting with a terminal status.

How does automated code review work in this workflow?

Step 04 builds a diff from the baseline revision and runs parallel review layers: blind hunter, edge-case hunter, verification-gap, and intent-alignment. Findings are triaged into intent_gap, bad_spec, patch, defer, or reject, with patches auto-fixed and bad_spec triggering spec repair loopbacks.

What happens when the review finds spec problems?

bad_spec findings trigger a repair loop: code is reverted, the spec is amended outside the read-only intent-contract with KEEP instructions logged, and implementation re-runs. The loop halts as blocked after more than five iterations.

Does this skill require subagents and version control?

Yes. Subagents are mandatory for implementation and reviews; if unavailable the workflow halts with status blocked. Version control is used for baseline capture, clean-tree checks, and final commits, with a NO_VCS fallback path.

What are the limitations of unattended development loops?

The workflow halts with status blocked on unclear intent, intent gaps, verification failures, dirty repositories, or non-converging review loops. It never asks questions mid-run, so ambiguous requests end as blocked rather than being guessed.