bmad-quick-dev

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

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Wizarck/nexandro --skill bmad-quick-dev-wizarck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-quick-dev
Source: https://github.com/Wizarck/nexandro/tree/main/skills/bmad-quick-dev
Command: npx skills add https://github.com/Wizarck/nexandro --skill bmad-quick-dev-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature request or bug fix into reviewed, mergeable code often skips planning discipline, producing unreviewed diffs and scope creep. This Skill enforces a structured workflow that converts user intent into a token-bounded specification, implements it, and runs multi-agent adversarial review before presenting results. ## Core Features & Use Cases - Intent Clarification & Routing: Clarifies the request, checks git state, detects multi-goal scope, and routes work to either a one-shot path or a full plan-code-review pipeline. - Spec-Driven Planning: Generates a frozen-intent specification with boundaries, I/O edge-case matrices, code maps, and Given/When/Then acceptance criteria, kept within a 900-1600 token budget. - Adversarial Review Loop: Launches three independent reviewers (blind hunter, edge-case hunter, acceptance auditor), classifies findings as intent_gap, bad_spec, patch, defer, or reject, and loops back when needed. - Use Case: A developer asks to add pagination to an API endpoint. The Skill drafts a spec, gets human approval, implements the change, runs three review passes, fixes patches, and presents a clickable Suggested Review Order for final human review. ## Quick Start Ask the agent to implement a specific feature or bug fix, for example: implement JWT refresh token support in the auth module following the project conventions.

Frequently Asked Questions about bmad-quick-dev

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

FAQPage Schema
How do I implement a feature using a spec-driven AI workflow?▼

State your intent clearly and the workflow clarifies it, drafts a specification with boundaries and acceptance criteria, waits for your approval, then implements and reviews the code. You approve the spec at a checkpoint before any code is written.

What is the difference between the one-shot and plan-code-review routes?▼

The one-shot route handles zero-blast-radius changes by implementing directly with a single adversarial review. The plan-code-review route runs the full pipeline: planning, approval checkpoint, implementation, three-reviewer adversarial review, and presentation.

How does the adversarial code review work?▼

Three subagents review the diff without conversation context: a blind hunter sees only the diff, an edge case hunter gets project access, and an acceptance auditor checks against the spec. Findings are classified as intent_gap, bad_spec, patch, defer, or reject.

Can it resume work from an existing draft specification?▼

Yes. It scans the implementation artifacts directory for specs with status draft, ready-for-dev, in-progress, or in-review, and resumes at the matching step. Passing a spec file path directly also routes to the correct step.

What happens when a specification exceeds the token limit?▼

Specs target 900-1600 tokens. Above 1600, the workflow halts and asks whether to split secondary goals into a deferred-work file or keep the full spec, since oversized specs risk context rot in implementation agents.

Does the workflow push code or create pull requests automatically?▼

No. It creates only a local commit with a conventional message after review passes. Pushing and pull request creation are offered to the human at the end but never executed automatically.