Skip to content
🤖 AI-optimized docs: llms-full.txt

What Are BMad Workflows?

BMad Workflows are skills that guide users through a structured process to produce a specific output. They do most of the heavy lifting in the BMad ecosystem. Focused, composable, and generally stateless.

Like agents, workflows are ultimately skill files. The difference is in emphasis: workflows prioritize getting to an outcome over maintaining a persistent identity.

TraitWorkflowAgent
GoalComplete a defined process and produce an artifactBe an ongoing conversational partner
PersonaMinimal, enough to facilitate a good conversationCentral to the experience
MemoryGenerally stateless between sessionsPersistent agent memory
ScopeAll steps serve one cohesive purposeCan span loosely related capabilities

The BMad Builder classifies workflows into three tiers based on complexity.

TypeDescriptionExample
Simple UtilityA single-purpose tool that does one thing wellValidate a schema, convert a file format
Simple WorkflowA short guided process with a few sequential stepsCreate a quick tech spec
Complex WorkflowA multi-stage process with branching paths, progressive disclosure, and potentially multiple outputsCreate and manage PRDs (covering create, edit, validate, convert, and polish)

Complex workflows use progressive disclosure to handle multiple operations within a single skill. Rather than building five separate skills for create, edit, validate, convert, and polish, you build one workflow that detects the user’s intent (from how they talk to it or what arguments they pass) and routes internally to the right path.

This is the same pattern that powers BMad’s own multi-capability agents and workflows. It keeps the user’s experience simple while the skill handles routing behind the scenes.

Both the Agent Builder and the Workflow Builder support two interaction styles when creating skills.

ModeHow It WorksBest For
YOLOYou brain-dump your idea; the builder guesses its way to a finished skill, asking only when truly stuckQuick prototypes, experienced builders
GuidedThe builder walks you through decisions, clarifies ambiguities, and ensures nothing is overlookedProduction workflows, first-time builders

Guided mode is no longer the slow multi-step process of earlier BMad versions. It is conversational and adaptive, but produces significantly better results than YOLO for complex workflows.

Like agents, workflows can support a Headless Mode. When invoked headless (through a scheduler, orchestrator, or another skill) the workflow skips interactive prompts and completes its process end-to-end without waiting for user input.

Choose a Workflow WhenChoose an Agent When
The process has a clear start and endThe user will return to it across sessions
No need to remember past interactionsRemembering context adds value
All steps serve one cohesive goalCapabilities are loosely related
You want a composable building blockYou want a persistent conversational partner

Workflows are also excellent as the internal capabilities of an agent. Build the workflow first, then wrap it in an agent if you need persona and memory on top.

Workflow customization is fully opt-in. If you don’t need users to override anything, don’t ship a customize.toml at all; the workflow runs with hardcoded paths and defaults. If you do opt in, the builder walks you through Configurability Discovery, where you name the scalars (templates, output paths, hooks) you want to expose. Users override them through the three-layer model: your shipped defaults at {skill-root}/customize.toml, team overrides at _bmad/custom/{skill-name}.toml, and personal overrides at _bmad/custom/{skill-name}.user.toml.

See Customization for Authors for the decision guide and How to Make a Skill Customizable for the build-time steps.

The BMad Workflow Builder (bmad-workflow-builder) uses the same six-phase conversational discovery as the Agent Builder (intent, classification, requirements, drafting, building, and quality optimization) and produces a ready-to-use skill folder.

See the Builder Commands Reference for details on the build process phases and capabilities.