bmad-quick-dev

Convert coding requests into scoped specifications and working code artifacts.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/ncptuan/stock_backtest_project --skill bmad-quick-dev-ncptuan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-quick-dev
Source: https://github.com/ncptuan/stock_backtest_project/tree/main/.claude/skills/bmad-quick-dev
Command: npx skills add https://github.com/ncptuan/stock_backtest_project --skill bmad-quick-dev-ncptuan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a vague or detailed coding request into a disciplined implementation workflow that plans, builds, reviews, and presents production-ready code changes without skipping critical validation steps.

Core Features & Use Cases

  • Intent-to-Implementation Workflow: Routes requests into either a one-shot change or a full plan-code-review flow based on risk and scope.
  • Structured Spec Generation: Produces implementation specs with constraints, acceptance criteria, code maps, verification steps, and review guidance.
  • Built-in Review Loops: Uses adversarial, edge-case, and acceptance-focused review passes to catch gaps, bad specs, and patch-level issues before final presentation.
  • Use Case: When you need to add a feature, fix a bug, or refactor an existing component while preserving project conventions, this Skill helps create a scoped spec, implement the change, validate it against requirements, and prepare a reviewer-friendly handoff.

Quick Start

Ask the bmad-quick-dev skill to implement a specific feature or bug fix in the repository and follow its workflow to plan, code, review, and present the result.

Frequently Asked Questions about bmad-quick-dev

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

FAQPage Schema
How do I turn vague coding requests into reviewed code changes in an existing codebase?

Spec-driven development converts vague or detailed coding requests into scoped specifications, implements working code artifacts, and enforces review loops to produce reviewer-friendly changes in an existing codebase.

What is the best way to implement a feature while preserving project conventions and architecture alignment?

Implementation workflows enforce architecture alignment and project conventions by routing requests into structured spec generation with constraints, acceptance criteria, and code maps before building changes.

How do I plan and execute an epic-story implementation workflow for bug fixing or refactoring?

Eic-story implementation workflows route bug fixing, refactoring, or feature development requests into either a one-shot change or a full plan-code-review flow based on risk and scope assessment.

Does spec-driven development work for low-risk one-shot edits or only full feature development?

Spec-driven development supports both one-shot low-risk edits and full feature development by routing requests based on risk and scope, applying full review loops only when changes require deeper validation.

Why do I need adversarial and edge-case review passes before presenting completed code changes?

Adversarial, edge-case, and acceptance-focused review passes catch gaps, bad specs, and patch-level issues during code review before final reviewer-oriented presentation of completed changes.

How to validate implementation against acceptance criteria and prepare a developer handoff?

Diff-based validation and version-control checks verify implementation against acceptance criteria, producing reviewer-oriented presentation of completed changes for developer handoff workflows.