bmad-quick-dev

Implement user intents into code artifacts with spec files and review order.

Updated Apr 2, 2026

Search Tags:#automation #git #workflow #spec-driven #review #implement #code-generation

Ready to run

npx skills add https://github.com/amitmishra-byldd/Bmad-Note-Maker --skill bmad-quick-dev-amitmishra-byldd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-quick-dev
Source: https://github.com/amitmishra-byldd/Bmad-Note-Maker/tree/main/_bmad/bmm/4-implementation/bmad-quick-dev
Command: npx skills add https://github.com/amitmishra-byldd/Bmad-Note-Maker --skill bmad-quick-dev-amitmishra-byldd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts loosely-specified user intents, bug reports, or change requests into a disciplined, reviewable implementation by producing a spec, executing a stepwise implementation plan, and preparing a human-friendly review trail.

Core Features & Use Cases

Spec-driven implementation: Generates or fills a spec from the provided intent, enforces the Ready-for-Development standard, and tracks status through the workflow steps.
Structured implementation & review: Walks through planning, implementation, adversarial review, and presentation steps including diffs, suggested review order, and commit guidance without auto-pushing.
Use Case: Turn a user story or bug report into a spec-wip, implement code changes with baseline metadata, run review loops, and produce a final spec ready for human review and merging.

Quick Start

Implement the user's intent by creating a ready-for-review spec, following the Quick Dev workflow, and producing the corresponding code changes and suggested review order for human reviewers.

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 a feature request into production-ready code with a spec file?▼

Spec-driven implementation converts feature requests into production-ready code by generating a spec file, executing a stepwise implementation plan, and preparing a human-friendly review trail with diffs and suggested review order.

What is the step-file workflow for planning and reviewing code changes?▼

The step-file workflow is a structured process for planning, implementing, and reviewing code changes. It walks through baseline metadata tracking, adversarial review loops, and presentation steps to produce a final spec ready for merging.

How do I implement code changes from bug reports without auto-pushing to git?▼

You can implement code changes from bug reports without auto-pushing by using a workflow that enforces version-control checks and non-pushing safety constraints, preparing diffs and commit guidance for human review instead.

Can I use spec-driven development for refactors and small change requests?▼

Yes, spec-driven development applies to feature requests, bug fixes, refactors, and small change requests. It enforces a Ready-for-Development standard and tracks status through implementation workflow steps.

Does the code generation workflow follow existing project architecture and conventions?▼

The code generation workflow implements user intents into production-ready code artifacts that strictly follow the repository's existing architecture and conventions, ensuring consistency across all generated changes.

What is included in the suggested review order for generated code?▼

The suggested review order includes prepared diffs, commit guidance, and a human-friendly review trail. It presents the implementation steps and adversarial review results without automatically pushing changes to version control.