BMad Glossary
Comprehensive terminology reference for the BMad Method.
Navigation
Section titled âNavigationâ- Core Concepts
- Scale and Complexity
- Planning Documents
- Workflow and Phases
- Agents and Roles
- Status and Tracking
- Project Types
- Implementation Terms
- Game Development Terms
Core Concepts
Section titled âCore ConceptsâBMad (Breakthrough Method of Agile AI Driven Development)
Section titled âBMad (Breakthrough Method of Agile AI Driven Development)âAI-driven agile development framework with specialized agents, guided workflows, and scale-adaptive intelligence.
BMM (BMad Method Module)
Section titled âBMM (BMad Method Module)âCore orchestration system for AI-driven agile development, providing comprehensive lifecycle management through specialized agents and workflows.
BMad Method
Section titled âBMad MethodâThe complete methodology for AI-assisted software development, encompassing planning, architecture, implementation, and quality assurance workflows that adapt to project complexity.
Scale-Adaptive System
Section titled âScale-Adaptive SystemâBMad Methodâs intelligent workflow orchestration that automatically adjusts planning depth, documentation requirements, and implementation processes based on project needs through three distinct planning tracks (Quick Flow, BMad Method, Enterprise Method).
A specialized AI persona with specific expertise (PM, Architect, SM, DEV, TEA) that guides users through workflows and creates deliverables. Agents have defined capabilities, communication styles, and workflow access.
Workflow
Section titled âWorkflowâA multi-step guided process that orchestrates AI agent activities to produce specific deliverables. Workflows are interactive and adapt to user context.
Scale and Complexity
Section titled âScale and ComplexityâQuick Flow Track
Section titled âQuick Flow TrackâFast implementation track using tech-spec planning only. Best for bug fixes, small features, and changes with clear scope. Typical range: 1-15 stories. No architecture phase needed. Examples: bug fixes, OAuth login, search features.
BMad Method Track
Section titled âBMad Method TrackâFull product planning track using PRD + Architecture + UX. Best for products, platforms, and complex features requiring system design. Typical range: 10-50+ stories. Examples: admin dashboards, e-commerce platforms, SaaS products.
Enterprise Method Track
Section titled âEnterprise Method TrackâExtended enterprise planning track adding Security Architecture, DevOps Strategy, and Test Strategy to BMad Method. Best for enterprise requirements, compliance needs, and multi-tenant systems. Typical range: 30+ stories. Examples: multi-tenant platforms, compliance-driven systems, mission-critical applications.
Planning Track
Section titled âPlanning TrackâThe methodology path (Quick Flow, BMad Method, or Enterprise Method) chosen for a project based on planning needs, complexity, and requirements rather than story count alone.
Note: Story counts are guidance, not definitions. Tracks are determined by what planning the project needs, not story math.
Planning Documents
Section titled âPlanning DocumentsâTech-Spec (Technical Specification)
Section titled âTech-Spec (Technical Specification)âQuick Flow track only. Comprehensive technical plan created upfront that serves as the primary planning document for small changes or features. Contains problem statement, solution approach, file-level changes, stack detection (brownfield), testing strategy, and developer resources.
PRD (Product Requirements Document)
Section titled âPRD (Product Requirements Document)âBMad Method/Enterprise tracks. Product-level planning document containing vision, goals, Functional Requirements (FRs), Non-Functional Requirements (NFRs), success criteria, and UX considerations. Replaces tech-spec for larger projects that need product planning. V6 Note: PRD focuses on WHAT to build (requirements). Epic+Stories are created separately AFTER architecture via create-epics-and-stories workflow.
Architecture Document
Section titled âArchitecture DocumentâBMad Method/Enterprise tracks. System-wide design document defining structure, components, interactions, data models, integration patterns, security, performance, and deployment.
Scale-Adaptive: Architecture complexity scales with track - BMad Method is lightweight to moderate, Enterprise Method is comprehensive with security/devops/test strategies.
High-level feature groupings that contain multiple related stories. Typically span 5-15 stories each and represent cohesive functionality (e.g., âUser Authentication Epicâ).
Product Brief
Section titled âProduct BriefâOptional strategic planning document created in Phase 1 (Analysis) that captures product vision, market context, user needs, and high-level requirements before detailed planning.
GDD (Game Design Document)
Section titled âGDD (Game Design Document)âGame development equivalent of PRD, created by Game Designer agent for game projects. Comprehensive document detailing all aspects of game design: mechanics, systems, content, and more.
Game Brief
Section titled âGame BriefâDocument capturing the gameâs core vision, pillars, target audience, and scope. Foundation for the GDD.
Workflow and Phases
Section titled âWorkflow and PhasesâPhase 0: Documentation (Prerequisite)
Section titled âPhase 0: Documentation (Prerequisite)âConditional phase for brownfield projects. Creates comprehensive codebase documentation before planning. Only required if existing documentation is insufficient for AI agents.
Phase 1: Analysis (Optional)
Section titled âPhase 1: Analysis (Optional)âDiscovery and research phase including brainstorming, research workflows, and product brief creation. Optional for Quick Flow, recommended for BMad Method, required for Enterprise Method.
Phase 2: Planning (Required)
Section titled âPhase 2: Planning (Required)âAlways required. Creates formal requirements and work breakdown. Routes to tech-spec (Quick Flow) or PRD (BMad Method/Enterprise) based on selected track.
Phase 3: Solutioning (Track-Dependent)
Section titled âPhase 3: Solutioning (Track-Dependent)âArchitecture design phase. Required for BMad Method and Enterprise Method tracks. Includes architecture creation, validation, and gate checks.
Phase 4: Implementation (Required)
Section titled âPhase 4: Implementation (Required)âSprint-based development through story-by-story iteration. Uses sprint-planning, create-story, dev-story, code-review, and retrospective workflows.
Quick Spec Flow
Section titled âQuick Spec FlowâFast-track workflow system for Quick Flow track projects that goes straight from idea to tech-spec to implementation, bypassing heavy planning. Designed for bug fixes, small features, and rapid prototyping.
Agents and Roles
Section titled âAgents and RolesâPM (Product Manager)
Section titled âPM (Product Manager)âAgent responsible for creating PRDs, tech-specs, and managing product requirements. Primary agent for Phase 2 planning.
Analyst (Business Analyst)
Section titled âAnalyst (Business Analyst)âAgent that initializes workflows, conducts research, creates product briefs, and tracks progress. Often the entry point for new projects.
Architect
Section titled âArchitectâAgent that designs system architecture, creates architecture documents, performs technical reviews, and validates designs. Primary agent for Phase 3 solutioning.
SM (Scrum Master)
Section titled âSM (Scrum Master)âAgent that manages sprints, creates stories, generates contexts, and coordinates implementation. Primary orchestrator for Phase 4 implementation.
DEV (Developer)
Section titled âDEV (Developer)âAgent that implements stories, writes code, runs tests, and performs code reviews. Primary implementer in Phase 4.
TEA (Test Architect)
Section titled âTEA (Test Architect)âAgent responsible for test strategy, quality gates, NFR assessment, and comprehensive quality assurance. Integrates throughout all phases.
Technical Writer
Section titled âTechnical WriterâAgent specialized in creating and maintaining high-quality technical documentation. Expert in documentation standards, information architecture, and professional technical writing.
UX Designer
Section titled âUX DesignerâAgent that creates UX design documents, interaction patterns, and visual specifications for UI-heavy projects.
Game Designer
Section titled âGame DesignerâSpecialized agent for game development projects. Creates game design documents (GDD) and game-specific workflows.
Game Architect
Section titled âGame ArchitectâAgent that designs game system architecture, creates technical architecture for games, and validates game-specific designs.
BMad Master
Section titled âBMad MasterâMeta-level orchestrator agent from BMad Core. Facilitates party mode, lists available tasks and workflows, and provides high-level guidance across all modules.
Party Mode
Section titled âParty ModeâMulti-agent collaboration feature where all installed agents discuss challenges together in real-time. BMad Master orchestrates, selecting 2-3 relevant agents per message for natural cross-talk and debate. Best for strategic decisions, creative brainstorming, cross-functional alignment, and complex problem-solving.
Status and Tracking
Section titled âStatus and Trackingâbmm-workflow-status.yaml
Section titled âbmm-workflow-status.yamlâPhases 1-3. Tracking file that shows current phase, completed workflows, progress, and next recommended actions. Created by workflow-init, updated automatically.
sprint-status.yaml
Section titled âsprint-status.yamlâPhase 4 only. Single source of truth for implementation tracking. Contains all epics, stories, and retrospectives with current status for each. Created by sprint-planning, updated by agents.
Story Status Progression
Section titled âStory Status Progressionâbacklog â ready-for-dev â in-progress â review â done- backlog - Story exists in epic but not yet created
- ready-for-dev - Story file created via create-story; validation is optional
- in-progress - DEV is implementing via dev-story
- review - Implementation complete, awaiting code-review
- done - Completed with DoD met
Epic Status Progression
Section titled âEpic Status Progressionâbacklog â in-progress â done- backlog - Epic not yet started
- in-progress - Epic actively being worked on
- done - All stories in epic completed
Retrospective
Section titled âRetrospectiveâWorkflow run after completing each epic to capture learnings, identify improvements, and feed insights into next epic planning. Critical for continuous improvement.
Project Types
Section titled âProject TypesâGreenfield
Section titled âGreenfieldâNew project starting from scratch with no existing codebase. Freedom to establish patterns, choose stack, and design from clean slate.
Brownfield
Section titled âBrownfieldâExisting project with established codebase, patterns, and constraints. Requires understanding existing architecture, respecting established conventions, and planning integration with current systems.
Critical: Brownfield projects should run document-project workflow BEFORE planning to ensure AI agents have adequate context about existing code.
document-project Workflow
Section titled âdocument-project WorkflowâBrownfield prerequisite. Analyzes and documents existing codebase, creating comprehensive documentation including project overview, architecture analysis, source tree, API contracts, and data models. Three scan levels: quick, deep, exhaustive.
Implementation Terms
Section titled âImplementation TermsâSingle unit of implementable work with clear acceptance criteria, typically 2-8 hours of development effort. Stories are grouped into epics and tracked in sprint-status.yaml.
Story File
Section titled âStory FileâMarkdown file containing story details: description, acceptance criteria, technical notes, dependencies, implementation guidance, and testing requirements.
Story Context
Section titled âStory ContextâImplementation guidance embedded within story files during the create-story workflow. Provides implementation-specific context, references existing patterns, suggests approaches, and helps maintain consistency with established codebase conventions.
Sprint Planning
Section titled âSprint PlanningâWorkflow that initializes Phase 4 implementation by creating sprint-status.yaml, extracting all epics/stories from planning docs, and setting up tracking infrastructure.
Time-boxed period of development work, typically 1-2 weeks.
Gate Check
Section titled âGate CheckâValidation workflow (implementation-readiness) run before Phase 4 to ensure PRD + Architecture + Epics + UX (optional) are aligned with no gaps or contradictions. Required for BMad Method and Enterprise Method tracks.
DoD (Definition of Done)
Section titled âDoD (Definition of Done)âCriteria that must be met before marking a story as done. Typically includes: implementation complete, tests written and passing, code reviewed, documentation updated, and acceptance criteria validated.
Shard / Sharding
Section titled âShard / ShardingâFor runtime LLM optimization only (NOT human docs). Splitting large planning documents (PRD, epics, architecture) into smaller section-based files to improve workflow efficiency. Phase 1-3 workflows load entire sharded documents transparently. Phase 4 workflows selectively load only needed sections for massive token savings.
Game Development Terms
Section titled âGame Development TermsâCore Fantasy
Section titled âCore FantasyâThe emotional experience players seek from your game. What they want to FEEL.
Core Loop
Section titled âCore LoopâThe fundamental cycle of actions players repeat throughout gameplay. The heart of your game.
Design Pillar
Section titled âDesign PillarâCore principle that guides all design decisions. Typically 3-5 pillars define a gameâs identity.
Game Type
Section titled âGame TypeâGenre classification that determines which specialized GDD sections are included.
Narrative Complexity
Section titled âNarrative ComplexityâHow central story is to the game experience:
- Critical - Story IS the game (visual novels)
- Heavy - Deep narrative with gameplay (RPGs)
- Moderate - Meaningful story supporting gameplay
- Light - Minimal story, gameplay-focused
Environmental Storytelling
Section titled âEnvironmental StorytellingâNarrative communicated through the game world itselfâvisual details, audio, found documentsârather than explicit dialogue.
MDA Framework
Section titled âMDA FrameworkâMechanics â Dynamics â Aesthetics. Framework for analyzing and designing games.
Procedural Generation
Section titled âProcedural GenerationâAlgorithmic creation of game content (levels, items, characters) rather than hand-crafted.
Roguelike
Section titled âRoguelikeâGenre featuring procedural generation, permadeath, and run-based progression.
Metroidvania
Section titled âMetroidvaniaâGenre featuring interconnected world exploration with ability-gated progression.
Meta-Progression
Section titled âMeta-ProgressionâPersistent progression that carries between individual runs or sessions.
Permadeath
Section titled âPermadeathâGame mechanic where character death is permanent, typically requiring a new run.
Player Agency
Section titled âPlayer AgencyâThe degree to which players can make meaningful choices that affect outcomes.
Additional Terms
Section titled âAdditional TermsâWorkflow Status
Section titled âWorkflow StatusâUniversal entry point workflow that checks for existing status file, displays current phase/progress, and recommends next action based on project state.
Workflow Init
Section titled âWorkflow InitâInitialization workflow that creates bmm-workflow-status.yaml, detects greenfield vs brownfield, determines planning track, and sets up appropriate workflow path.
Track Selection
Section titled âTrack SelectionâAutomatic analysis by workflow-init that uses keyword analysis, complexity indicators, and project requirements to suggest appropriate track (Quick Flow, BMad Method, or Enterprise Method). User can override suggested track.
Correct Course
Section titled âCorrect CourseâWorkflow run during Phase 4 when significant changes or issues arise. Analyzes impact, proposes solutions, and routes to appropriate remediation workflows.
Feature Flags
Section titled âFeature FlagsâImplementation technique for brownfield projects that allows gradual rollout of new functionality, easy rollback, and A/B testing. Recommended for BMad Method and Enterprise brownfield changes.
Integration Points
Section titled âIntegration PointsâSpecific locations where new code connects with existing systems. Must be documented explicitly in brownfield tech-specs and architectures.
Convention Detection
Section titled âConvention DetectionâQuick Spec Flow feature that automatically detects existing code style, naming conventions, patterns, and frameworks from brownfield codebases, then asks user to confirm before proceeding.