bmad-quick-dev

Convert user intent into implementation artifacts and a reviewable plan.

36|16|Updated May 1, 2026
One-click install
npx skills add https://github.com/tronghieu/lumina-wiki --skill bmad-quick-dev-tronghieu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-quick-dev
Source: https://github.com/tronghieu/lumina-wiki/tree/main/.agents/skills/bmad-quick-dev
Command: npx skills add https://github.com/tronghieu/lumina-wiki --skill bmad-quick-dev-tronghieu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill converts a user’s requested change into a hardened, reviewable implementation plan and code-creation workflow that follows the project’s architecture and conventions.

Core Features & Use Cases

  • Workflow-to-Artifact Pipeline: Resolves a configured activation workflow, loads persistent facts and planning context, and drives planning → implementation → review → presentation.
  • Spec-Driven Delivery with Guardrails: Generates a READY FOR DEVELOPMENT spec template (testable ACs, clear boundaries, token limits) and enforces frozen intent during implementation.
  • Epic Context Compilation: Compiles epic-specific developer context from planning artifacts into a focused context file used during planning.
  • Change Discipline & Review Loop: Constructs diffs, runs structured reviewer roles, classifies findings, and loops only when intent/spec issues require re-derivation.

Quick Start

Ask your AI to run the bmad-quick-dev workflow to implement your described feature, bug fix, or refactor in a way that matches the existing project patterns and outputs a ready-for-review spec.

Frequently Asked Questions about bmad-quick-dev

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

FAQPage Schema
How do I convert a feature intent into review-ready code?

To convert feature intent into review-ready code, an agent workflow generates a developer-ready plan with testable acceptance criteria, enforces architecture conventions, and outputs a structured diff for review.

What is spec-driven delivery for code generation?

Spec-driven delivery for code generation creates a READY FOR DEVELOPMENT template with testable acceptance criteria and token limits, enforcing frozen intent during implementation to ensure code matches project boundaries.

How do I plan an epic-driven story workflow with compiled context?

Planning an epic-driven story workflow involves compiling epic-specific developer context from planning artifacts into a focused context file, which then drives the sequencing of planning, implementation, and structured review.

How does structured code review classification handle loopbacks?

Structured code review classification runs reviewer roles on constructed diffs, classifies findings, and triggers controlled loopbacks only when intent or spec issues require re-derivation of the implementation artifacts.

Can I use this workflow for refactoring and modifying existing components?

Yes, you can use this workflow for refactoring and modifying components, as it applies to building, fixing, tweaking, or modifying code by resolving workflow customization and loading persistent facts to match existing project patterns.