DEV Community

JackTT
JackTT

Posted on

BMAD Quick Flow

BMAD Quick Flow

Quick Flow is the lean path inside the BMAD Method. It skips the full planning ceremony (PRD → Architecture → Epics → Sprint Planning) and gets you from idea to shipped code in as few steps as possible. Use it for small changes, isolated features, or brownfield additions where the full workflow would be overkill.


The Three Commands

1. /bmad-agent-bmm-quick-flow-solo-dev — The Hub Agent

What it is: Loads Barry, an AI persona acting as an Elite Full-Stack Developer and Quick Flow specialist. Barry presents an interactive menu of all Quick Flow operations in one place.

Barry's menu:

Code Action
QS Quick Spec — create a tech spec
QD Quick Dev — implement a spec
CR Code Review
PM Party Mode (multi-agent discussion)
DA Dismiss Agent

When to use it:

  • You want a single entry point and prefer to pick your next step interactively
  • You're new to Quick Flow and want guidance on what to do next

When to skip it:

  • You already know what you want — call /bmad-bmm-quick-spec or /bmad-bmm-quick-dev directly instead

2. /bmad-bmm-quick-spec — Write a Technical Spec

What it is: A conversational workflow that produces an implementation-ready technical specification. It asks you sharp questions about the feature, investigates existing code, and outputs a complete, self-contained spec file.

What "ready for development" means:

Criterion Requirement
Actionable Every task has a specific file path and a clear action
Logical Tasks are ordered by dependency (lowest level first)
Testable All acceptance criteria follow Given / When / Then
Complete All investigation results are inlined — no placeholders or TBDs
Self-contained A fresh agent can implement the feature without reading the conversation history

When to use it:

  • The change is small to medium in scope and does not need a full PRD
  • You are adding to a well-established codebase pattern
  • You want to plan before you code — produce the spec first, implement later
  • You need a written record of exactly what will be changed and why

When to skip it:

  • The task is so simple it fits in one sentence — just tell Quick Dev directly
  • The change is large and complex — use the full BMM workflow instead

3. /bmad-bmm-quick-dev — Implement the Spec

What it is: A step-by-step implementation workflow. The AI acts as an autonomous developer: it reads the tech spec (or takes direct instructions), follows existing code patterns, writes the code, and runs tests.

How it works internally:

  1. Mode detection — Did you provide a tech spec file, or are you giving direct instructions?
  2. Code investigation — AI reads relevant files to understand the existing patterns
  3. Implementation — Tasks are executed sequentially, one at a time
  4. Verification — Tests are run and output is confirmed after each change

When to use it:

  • You have a spec from /bmad-bmm-quick-spec and are ready to implement
  • The task is small enough to describe directly without a formal spec
  • You need a one-off change that is not part of the current sprint plan

When to skip it:

  • The change spans multiple stories or epics — use the full Dev Story workflow (/bmad-bmm-dev-story) instead

Typical Workflows

Spec first, then implement (recommended for anything non-trivial)

/bmad-bmm-quick-spec
  → Discover requirements through conversation
  → AI investigates existing code
  → Outputs a tech-spec file

/bmad-bmm-quick-dev
  → Point it at the spec file
  → AI implements all tasks sequentially
  → Tests run after each change
Enter fullscreen mode Exit fullscreen mode

Direct implementation (for trivial changes)

/bmad-bmm-quick-dev
  → Describe what you want in plain language
  → AI implements immediately
Enter fullscreen mode Exit fullscreen mode

Using the hub agent

/bmad-agent-bmm-quick-flow-solo-dev
  → Barry loads and shows the menu
  → Select QS to create a spec
  → Select QD to implement it
Enter fullscreen mode Exit fullscreen mode

Quick Flow vs. Full BMM Workflow

Situation Use
New product, complex feature, needs PRD + Architecture Full BMM flow
Small feature, brownfield addition, well-known pattern Quick Flow
One-off fix or change during an active sprint /bmad-bmm-quick-dev directly
Unsure what to do next /bmad-help or load Barry via /bmad-agent-bmm-quick-flow-solo-dev

Rule of thumb: If you'd feel uncomfortable skipping a PRD and architecture doc, use the full flow. If the change fits on one page of notes, Quick Flow is the right tool.

This content is summarized by /bmad-help, the agent that helps us with anything about BMAD. You can also ask it for more details about BMAD usage.

Top comments (0)