bmad-quick-dev

Convert user intent into a review-ready code change spec via BMAD workflow checkpoints.

Updated May 17, 2026
One-click install
npx skills add https://github.com/thuantan2060/facebook-sale-tracking --skill bmad-quick-dev-thuantan2060
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-quick-dev
Source: https://github.com/thuantan2060/facebook-sale-tracking/tree/main/.agents/skills/bmad-quick-dev
Command: npx skills add https://github.com/thuantan2060/facebook-sale-tracking --skill bmad-quick-dev-thuantan2060

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps convert a developer’s intent (feature, bug fix, refactor, or change request) into a hardened, reviewable implementation spec that follows the project’s BMAD workflow and architectural conventions.

Core Features & Use Cases

  • Workflow-driven execution: Routes work through clarify → plan → implement → review → present checkpoints.
  • Spec generation with guardrails: Produces a Ready-for-Development spec using a frozen intent block and an explicit acceptance-criteria task list.
  • Epic/story context compilation: Compiles focused epic context for consistent implementation continuity.
  • Human control at critical checkpoints: HALTs for approvals and editing when intent is unclear or scope is too large.

Quick Start

Run the bmad-quick-dev workflow with your intent and let it generate a review-ready spec you can click through in your editor.

Frequently Asked Questions about bmad-quick-dev

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

FAQPage Schema
How do I generate a review-ready development spec from a feature intent?

You generate a development spec by routing intent through a structured workflow that creates a frozen intent block, compiles epic context, and produces a review-ready spec with explicit acceptance criteria.

What is the best way to maintain architecture adherence during code implementation?

Maintaining architecture adherence during code implementation requires deterministic planning and multi-stage review checkpoints that validate the generated spec against project conventions before and after the code is written.

How does a structured workflow handle bug fixes and refactoring requests?

A structured workflow handles bug fixes and refactoring by converting the change request into a hardened implementation spec, applying acceptance-testable outcomes and strict sequencing to ensure consistent architectural continuity.

Can I edit the implementation plan if the scope is too large or intent is unclear?

Yes, you can edit the implementation plan because the workflow halts at critical checkpoints for human approval, allowing you to clarify intent and adjust scope before proceeding to the code implementation stage.

When do I need a spec generation process with human approval gates?

You need a spec generation process with human approval gates when executing feature development or change requests that require deterministic planning, strict sequencing, and acceptance-testable outcomes to ensure review-ready code.