bmad-quick-dev

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

Updated May 22, 2026
One-click install
npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-quick-dev-asygnuz-s-a-s
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-quick-dev
Source: https://github.com/Asygnuz-S-A-S/one-star/tree/main/.claude/skills/bmad-quick-dev
Command: npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-quick-dev-asygnuz-s-a-s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature request or bug fix into reviewed, working code often skips planning and review discipline, producing unreviewable diffs and scope creep. This Skill enforces a structured workflow that converts user intent into an approved specification, implements it, and runs multi-agent adversarial review before presenting results. ## Core Features & Use Cases - Spec-Driven Planning: Clarifies intent, investigates the codebase, and writes a token-bounded specification with tasks, acceptance criteria, and a code map before any code changes. - Multi-Agent Adversarial Review: Runs blind, edge-case, and acceptance-auditor review subagents on the diff, classifying findings as patches, spec fixes, or deferred work with loopback handling. - Sprint & Epic Integration: Syncs story status with sprint-status.yaml, compiles epic context from planning artifacts, and generates a clickable Suggested Review Order for human reviewers. - Use Case: A developer asks to add a checkout validation feature; the Skill drafts a spec, gets approval, implements it via sub-agent, runs three review passes, commits the change, and opens an annotated review trail in VS Code. ## Quick Start Ask the agent to implement a specific feature or bug fix, for example: implement server-side validation for the checkout form following the quick dev workflow.

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 workflow?▼

Provide your intent to the workflow, which clarifies requirements, investigates the codebase, and writes a specification with tasks and acceptance criteria. After you approve the spec, it implements the changes, runs adversarial review, and presents a clickable review order.

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

The one-shot route handles changes with zero blast radius, implementing directly with a single adversarial review. The plan-code-review route covers everything else, requiring a full specification, human approval checkpoint, implementation, and three-reviewer adversarial review.

How does the adversarial code review classify findings?▼

Findings are deduplicated and classified as intent_gap, bad_spec, patch, defer, or reject. Patches are auto-fixed, deferred items go to a deferred-work file, and intent or spec problems trigger loopbacks that re-run planning or implementation.

Does this workflow work without sub-agent support?▼

Yes. When sub-agents are unavailable, the workflow falls back to inline execution for planning and writes review prompt files for each reviewer role. You then run those prompts in separate sessions and paste the findings back.

How does the skill sync with sprint-status.yaml?▼

When the spec corresponds to an epic story, the workflow resolves the story key and updates its development_status to in-progress or review at the appropriate steps. It never regresses a status and lifts the parent epic from backlog to in-progress when work begins.