bmad-build

Implements features and bug fixes through a spec-driven plan, implement, and review workflow.

1|Updated Sep 18, 2026
One-click install
npx skills add https://github.com/PastaSus/egg-defender --skill bmad-build-pastasus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-build
Source: https://github.com/PastaSus/egg-defender/tree/main/.agents/skills/bmad-build
Command: npx skills add https://github.com/PastaSus/egg-defender --skill bmad-build-pastasus

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 usually requires juggling planning, implementation, and review by hand. This Skill structures that entire cycle: it clarifies intent, writes a bounded specification, delegates implementation, and runs multi-layer code review before committing. ## Core Features & Use Cases - Spec-driven implementation: Converts user intent into a token-bounded spec file with intent, boundaries, I/O edge-case matrices, tasks, and acceptance criteria, then implements from that spec as the sole source of truth. - Multi-layer automated review: Runs parallel review layers (blind hunter, edge-case hunter, verification-gap) over the staged diff, triages every finding with verdicts, and routes fixes through patch, spec amendment, or deferral. - Epic story support: Compiles focused epic context from planning artifacts (PRD, architecture, UX) and syncs sprint status for story-based work. - Use Case: Hand the Skill a story like "implement story 3-2 digest delivery" and it loads the epic context, drafts a spec for your approval, implements via a subagent, reviews the diff with three reviewer passes, and commits the verified result. ## Quick Start Ask the assistant to use the bmad-build skill to implement your feature request, story, or bug fix and let it guide you through spec approval and review.

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, drafts a spec for your approval, implements it via a subagent, runs review layers over the diff, and commits the verified result.

How does the automated code review work in this workflow?

Step 4 stages a unified diff of all changes and launches parallel review layers: 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 an auto-patch, a spec amendment loop, or a deferred-work log.

Can bmad-build work with epic stories and sprint status?

Yes. When the intent is an epic story, it compiles a focused epic context file from planning artifacts like the PRD and architecture docs, and it updates sprint-status.yaml to in-progress or review as the story moves through the workflow.

What happens if the implementation review finds problems?

Findings are triaged by root cause. Trivial issues are auto-patched by re-engaging the implementation subagent, spec-level problems trigger a loopback that amends the spec and re-derives the code, and pre-existing issues are recorded in deferred-work.md.

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

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