Execute given workflow by loading its configuration, following instructions, and producing output Always read COMPLETE files - NEVER use offset/limit when reading any workflow related files Instructions are MANDATORY - either as file path, steps or embedded list in YAML, XML or markdown Execute ALL steps in instructions IN EXACT ORDER Save to template output file after EVERY "template-output" tag NEVER skip a step - YOU are responsible for every steps execution without fail or excuse Steps execute in exact numerical order (1, 2, 3...) Optional steps: Ask user unless #yolo mode active Template-output tags: Save content, discuss with the user the section completed, and NEVER proceed until the users indicates to proceed (unless YOLO mode has been activated) Resolve and load scope context before workflow execution using parallel-safe detection Scan workflow.yaml for {scope} variable in any path or variable If found, mark workflow as scope-required Scope-required workflows need an active scope to resolve paths correctly Inline --scope argument Check if command invocation includes scope parameter - /workflow-name --scope auth - /workflow-name --scope=auth - /workflow-name auth (positional, last arg matching scope pattern) alphanumeric with hyphens: auth, payment-v2, feature-123 If found, store as {scope} and echo: "**[SCOPE: {scope}]** Using inline scope" Conversation memory Check if scope was set earlier in THIS conversation If remembered from earlier in conversation, use it Echo: "**[SCOPE: {scope}]** Using scope from conversation context" BMAD_SCOPE environment variable Check for BMAD_SCOPE env var (set per terminal) If BMAD_SCOPE is set, use its value as scope Echo: "**[SCOPE: {scope}]** Using scope from BMAD_SCOPE env var" Session context file (.bmad-scope) Check for .bmad-scope file in project root (ignored when disabled) This file is shared across ALL sessions - NOT parallel-safe! If exists, parse YAML and check enabled/disabled status If enabled: false OR disabled: true → IGNORE this file (treat as not found) Legacy files without enabled/disabled keys are treated as enabled If enabled AND active_scope is present → use active_scope value If active_scope was used, echo: "**[SCOPE: {scope}]** Using scope from .bmad-scope (shared file - not parallel-safe)" Prompt user Only if scope-required and none found from above sources This workflow requires a scope. Select existing scope or create new one. Store resolved scope as {scope} variable for path resolution REMEMBER {scope} for rest of this conversation - do NOT re-read .bmad-scope later Check for scope registry: {project-root}/_bmad/_config/scopes.yaml If missing, echo warning: "**[SCOPE ERROR]** Scope system not initialized (missing scopes.yaml). Run: npx bmad-fh scope init" If missing, CLEAR {scope} and continue without scope (or prompt user if workflow is scope-required) Load scope configuration from {project-root}/_bmad/_config/scopes.yaml Validate scope exists and is active Resolve scope paths (THESE OVERRIDE config.yaml values!): - {scope_path} = {output_folder}/{scope} - {scope_planning} = {scope_path}/planning-artifacts - {scope_implementation} = {scope_path}/implementation-artifacts - {scope_tests} = {scope_path}/tests - {planning_artifacts} = {scope_planning} (OVERRIDE!) - {implementation_artifacts} = {scope_implementation} (OVERRIDE!) Load global project context: {output_folder}/_shared/project-context.md Load scope project context if exists: {scope_path}/project-context.md Merge contexts: scope extends global Check for pending dependency updates and notify user if any Continue without scope context, use legacy paths from config.yaml Echo: "**[NO SCOPE]** Running without scope isolation" Include "[SCOPE: {scope}]" or "[NO SCOPE]" in ALL status messages throughout workflow Before writing ANY artifact, echo the full target path including scope **[SCOPE: auth]** Writing PRD to: _bmad-output/auth/planning-artifacts/prd.md Check the workflow file extension from the provided path Mark as YAML-WORKFLOW → proceed to substep 1a Mark as MD-WORKFLOW → skip to substep 1d Read workflow.yaml from provided path Load config_source (REQUIRED for all modules) Load external config from config_source path Resolve all {config_source}: references with values from config Resolve system variables (date:system-generated) and paths ({project-root}, {installed_path}) Ask user for input of any variables that are still unknown Instructions: Read COMPLETE file from path OR embedded list (REQUIRED) If template path → Read COMPLETE template file If validation path → Note path for later loading when needed If template: false → Mark as action-workflow (else template-workflow) Data files (csv, json) → Store paths only, load on-demand when instructions reference them Resolve default_output_file path with all variables and {{date}} Create output directory if doesn't exist If template-workflow → Write template to output file with placeholders If action-workflow → Skip file creation Read the COMPLETE workflow.md file from provided path Parse frontmatter (YAML between --- markers) for metadata Extract the INITIALIZATION section if present Load config from config path specified in INITIALIZATION Resolve all variables from config Apply scope path overrides from Step 0 (these take precedence!) The workflow.md content after frontmatter becomes the instructions Continue to Step 2 to execute the markdown instructions MD workflows are self-contained instruction documents - follow them directly For each step in instructions: If optional="true" and NOT #yolo → Ask user to include If if="condition" → Evaluate condition If for-each="item" → Repeat step for each item If repeat="n" → Repeat step n times Process step instructions (markdown or XML tags) Replace {{variables}} with values (ask user if unknown) action xml tag → Perform the action check if="condition" xml tag → Conditional block wrapping actions (requires closing </check>) ask xml tag → Prompt user and WAIT for response invoke-workflow xml tag → Execute another workflow with given inputs and the workflow.xml runner invoke-task xml tag → Execute specified task invoke-protocol name="protocol_name" xml tag → Execute reusable protocol from protocols section goto step="x" → Jump to specified step Generate content for this section Save to file (Write first time, Edit subsequent) Display generated content [a] Advanced Elicitation, [c] Continue, [p] Party-Mode, [y] YOLO the rest of this document only. WAIT for response. Start the advanced elicitation workflow {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml Continue to next step Start the party-mode workflow {project-root}/_bmad/core/workflows/party-mode/workflow.md Enter #yolo mode for the rest of the workflow If no special tags and NOT #yolo: Continue to next step? (y/n/edit) Confirm document saved to output path Report workflow completion Full user interaction and confirmation of EVERY step at EVERY template output - NO EXCEPTIONS except yolo MODE Skip all confirmations and elicitation, minimize prompts and try to produce all of the workflow automatically by simulating the remaining discussions with an simulated expert user step n="X" goal="..." - Define step with number and goal optional="true" - Step can be skipped if="condition" - Conditional execution for-each="collection" - Iterate over items repeat="n" - Repeat n times action - Required action to perform action if="condition" - Single conditional action (inline, no closing tag needed) check if="condition">...</check> - Conditional block wrapping multiple items (closing tag required) ask - Get user input (ALWAYS wait for response before continuing) goto - Jump to another step invoke-workflow - Call another workflow invoke-task - Call a task invoke-protocol - Execute a reusable protocol (e.g., discover_inputs)

template-output - Save content checkpoint critical - Cannot be skipped example - Show example output

Ensure scope context hasn't been lost between workflow steps Verify {scope} variable is still available Verify {scope_path}, {planning_artifacts}, {implementation_artifacts} are set HALT workflow immediately Display error: "SCOPE CONTEXT LOST! Scope was set to '{scope}' but variables are missing." Ask user to restart workflow with explicit scope: /workflow-name --scope {scope} Display: "**[SCOPE: {scope}]** Scope verified - continuing workflow..." This provides visibility that scope is still active Prevent artifacts from being written to wrong scope directory Before writing any artifact, check the target path HALT immediately Display error: "SCOPE VIOLATION! Attempting to write to '{target_path}' but active scope is '{scope}'" Display expected path: "Expected path should start with: {scope_path}/" Continue anyway? (This may corrupt other scopes) [y/N] Intelligently load project files (whole or sharded) based on workflow's input_file_patterns configuration Only execute if workflow.yaml contains input_file_patterns section Read input_file_patterns from loaded workflow.yaml For each pattern group (prd, architecture, epics, etc.), note the load_strategy if present For each pattern in input_file_patterns: Determine load_strategy from pattern config (defaults to FULL_LOAD if not specified) Load ALL files in sharded directory - used for PRD, Architecture, UX, brownfield docs Use glob pattern to find ALL .md files (e.g., "{output_folder}/*architecture*/*.md") Load EVERY matching file completely Concatenate content in logical order (index.md first if exists, then alphabetical) Store in variable: {pattern_name_content} Load specific shard using template variable - example: used for epics with {{epic_num}} Check for template variables in sharded_single pattern (e.g., {{epic_num}}) If variable undefined, ask user for value OR infer from context Resolve template to specific file path Load that specific file Store in variable: {pattern_name_content} Load index.md, analyze structure and description of each doc in the index, then intelligently load relevant docs DO NOT BE LAZY - use best judgment to load documents that might have relevant information, even if only a 5% chance Load index.md from sharded directory Parse table of contents, links, section headers Analyze workflow's purpose and objective Identify which linked/referenced documents are likely relevant If workflow is about authentication and index shows "Auth Overview", "Payment Setup", "Deployment" → Load auth docs, consider deployment docs, skip payment Load all identified relevant documents Store combined content in variable: {pattern_name_content} When in doubt, LOAD IT - context is valuable, being thorough is better than missing critical info Mark pattern as RESOLVED, skip to next pattern Attempt glob match on 'whole' pattern (e.g., "{output_folder}/*prd*.md") Load ALL matching files completely (no offset/limit) Store content in variable: {pattern_name_content} (e.g., {prd_content}) Mark pattern as RESOLVED, skip to next pattern Set {pattern_name_content} to empty string Note in session: "No {pattern_name} files found" (not an error, just unavailable, offer use change to provide) List all loaded content variables with file counts ✓ Loaded {prd_content} from 5 sharded files: prd/index.md, prd/requirements.md, ... ✓ Loaded {architecture_content} from 1 file: Architecture.md ✓ Loaded {epics_content} from selective load: epics/epic-3.md ○ No ux_design files found This gives workflow transparency into what context is available • This is the complete workflow execution engine • You MUST Follow instructions exactly as written • The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml • You MUST have already loaded and processed: {installed_path}/workflow.yaml • This workflow uses INTENT-DRIVEN PLANNING - adapt organically to product type and context • YOU ARE FACILITATING A CONVERSATION With a user to produce a final document step by step. The whole process is meant to be collaborative helping the user flesh out their ideas. Do not rush or optimize and skip any section.