bmad-build

Implements code changes through a spec-driven plan, implement, and review workflow.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-build-tuanpa-nhg-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-build
Source: https://github.com/tuanpa-nhg-eng/nhg-ipms/tree/main/.claude/skills/bmad-build
Command: npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-build-tuanpa-nhg-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a feature request, bug fix, or refactor intent into working code often skips planning and review, producing inconsistent or unverified changes. This Skill enforces a disciplined workflow that clarifies intent, writes a bounded implementation spec, dispatches implementation, and runs adversarial multi-layer code review before committing. ## Core Features & Use Cases - Spec-driven implementation: Clarifies intent, investigates the codebase, and writes a token-bounded spec file with a code map, tasks, and acceptance criteria before any code changes. - Adversarial review loop: Runs parallel review layers (blind hunter, edge-case hunter, verification-gap reviewer) over the diff, triages findings into intent gaps, spec fixes, patches, or deferred work, and loops back automatically. - Epic story support: Compiles focused epic context from planning artifacts and syncs sprint-status.yaml as stories move through in-progress, review, and done states. - Use Case: Ask it to add a new API endpoint; it drafts a spec for your approval, implements via a subagent, reviews the diff with three independent reviewers, fixes findings, and commits with a suggested review order. ## Quick Start Ask the assistant to implement a feature or fix a bug, for example: build a password reset endpoint following the project's existing patterns.

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 with an AI coding workflow?

Describe the feature intent and the workflow clarifies requirements, investigates the codebase, and writes a bounded spec for your approval. After approval it implements the change, runs parallel review passes over the diff, fixes findings, and commits locally.

How does the automated code review step work?

The review step launches parallel context-free reviewer subagents: a blind hunter, an edge-case hunter, and a verification-gap reviewer. Findings are deduplicated, severity-rated, and triaged into intent gaps, spec fixes, auto-patches, deferred work, or rejections.

Can it handle stories from an epic breakdown?

Yes. It compiles a focused epic context file from planning artifacts like the PRD and architecture docs, loads continuity from previously completed stories, and syncs sprint-status.yaml as the story moves through in-progress, review, and done.

What happens if the implementation spec is too large?

Specs exceeding 1600 tokens trigger a checkpoint asking whether to split or keep the full scope. On split, secondary goals are recorded in deferred-work.md and the spec is regenerated for the narrowed scope.

Does it work without subagent support in my AI runtime?

Yes. When subagents are unavailable it falls back to inline execution for context compilation and implementation. For review layers requiring subagents, it writes the exact reviewer prompts to disk and asks you to run them in separate sessions.

When should I use the one-shot route instead of full planning?

Use the one-shot route only for zero-blast-radius changes with clear intent and no architectural decisions. It implements directly, runs a lighter review, writes a minimal trace spec, and commits without the plan-approve cycle.