What problem does it solve? Turning a feature request, bug fix, or change request into working code often skips planning, review, and verification, producing inconsistent results. This Skill enforces a disciplined multi-step workflow that converts any user intent into a reviewed, tested, and committed code change that follows the project's existing architecture and conventions. ## Core Features & Use Cases - Spec-driven implementation: Clarifies intent, investigates the codebase, and writes a structured spec file with a code map, tasks, and acceptance criteria before any code changes. - Dual routing: Routes zero-blast-radius changes through a fast one-shot path and everything else through a full plan-code-review pipeline with human approval checkpoints. - Adversarial review layers: Runs parallel review subagents (blind hunter, edge-case hunter, verification-gap reviewer) and triages findings into intent gaps, spec fixes, patches, or deferred work. - Use Case: Ask it to add a new API endpoint; it drafts a spec, gets your approval, implements via a subagent, reviews the diff for edge cases and missing tests, then commits with a suggested review order. ## Quick Start Ask the assistant to implement a feature or fix a bug, for example: use bmad-build to add pagination to the project list endpoint.
