bmad-build

Implements features and fixes through a spec-driven workflow with multi-layer code review.

Updated Sep 4, 2026
One-click install
npx skills add https://github.com/Joao-Victor-Medeiros/save-sc --skill bmad-build-joao-victor-medeiros
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-build
Source: https://github.com/Joao-Victor-Medeiros/save-sc/tree/main/.agents/skills/bmad-build
Command: npx skills add https://github.com/Joao-Victor-Medeiros/save-sc --skill bmad-build-joao-victor-medeiros

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a feature request or bug report into verified, reviewed code requires disciplined planning, implementation, and review that ad-hoc prompting rarely sustains. This Skill enforces a structured build pipeline so delegated work ships as hardened, reviewable changes instead of unverified edits. ## Core Features & Use Cases - Spec-driven planning: Clarifies intent, investigates the codebase, and writes a token-bounded spec with code maps, open questions, and acceptance criteria before any code changes. - Dual execution routes: Routes small clean changes through a oneshot path and larger work through a dispatch path with human approval checkpoints. - Multi-layer review: Runs blind-hunter, edge-case-hunter, and verification-gap reviewer subagents against the staged diff, then triages every finding into patch, loopback, or defer. - Use Case: Hand it a story like "implement story 3-2 digest delivery" and it compiles epic context, drafts a spec, implements via subagent, reviews the diff, and commits the verified result. ## Quick Start Ask the agent to implement a feature, story, or bug fix and let bmad-build plan, build, review, and commit the change.

Frequently Asked Questions about bmad-build

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

FAQPage Schema
How do I implement a feature or bug fix with bmad-build?▼

Invoke the skill with your intent, such as a feature description, story id, or issue link. It clarifies the intent, investigates the codebase, writes a spec, implements the change, runs multi-layer review on the diff, and commits the verified result.

What is the difference between the oneshot and dispatch routes?▼

The oneshot route handles small changes with no intent gaps, no irreversibles, and a small footprint, implementing directly without a checkpoint. The dispatch route writes a full spec, halts for human approval, then implements and reviews through separate steps.

How does the multi-layer code review work?▼

Three reviewer subagents run against the staged unified diff: a blind hunter, an edge-case hunter, and a verification-gap reviewer. Every finding is verified against the code, assigned a verdict, and routed to patch, spec loopback, intent-gap escalation, or deferral.

Does bmad-build work without subagent support?▼

Yes. When subagents are unavailable, it implements directly from the spec and writes standalone reviewer prompts for the user to run in separate sessions, then halts until findings are pasted back.

When should I not use bmad-build for a change?▼

Skip it for obvious low-risk mechanical maintenance such as ignore-file tweaks, typo-only or formatting-only edits, and configuration hygiene. It is also not meant for user-directed interactive edits or version-control operations that only record existing work.