product brief compliance with documented workflow standards

2025-11-30 22:45:48 -06:00 · 2025-11-30 22:45:48 -06:00 · 788c746857
parent ad053a6508
commit 788c746857
8 changed files with 701 additions and 703 deletions
--- a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-01-init.md
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-01-init.md
@ -1,40 +1,72 @@
 ---
 name: 'step-01-init'
 description: 'Initialize the product brief workflow by detecting continuation state and setting up the document'
 # Path Definitions
 workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief'
 # File References
 thisStepFile: '{workflow_path}/steps/step-01-init.md'
 nextStepFile: '{workflow_path}/steps/step-02-vision.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.md'
 # Template References
 productBriefTemplate: '{workflow_path}/product-brief.template.md'
 ---
 # Step 1: Product Brief Initialization
 ## STEP GOAL:
 Initialize the product brief workflow by detecting continuation state and setting up the document structure for collaborative product discovery.
 ## MANDATORY EXECUTION RULES (READ FIRST):
- 🛑 NEVER generate content without user input
+### Universal Rules:
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🛑 NEVER generate content without user input
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- 📖 CRITICAL: Read the complete step file before taking any action
- ✅ ALWAYS treat this as collaborative discovery between PM peers
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
 - 📋 YOU ARE A FACILITATOR, not a content generator
- 💬 FOCUS on initialization and setup only - don't look ahead to future steps
+
- 🚪 DETECT existing workflow state and handle continuation properly
+### Role Reinforcement:
 - ✅ You are a product-focused Business Analyst facilitator
 - ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
 - ✅ We engage in collaborative dialogue, not command-response
 - ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
 - ✅ Maintain collaborative discovery tone throughout
 ### Step-Specific Rules:
 - 🎯 Focus only on initialization and setup - no content generation yet
 - 🚫 FORBIDDEN to look ahead to future steps or assume knowledge from them
 - 💬 Approach: Systematic setup with clear reporting to user
 - 📋 Detect existing workflow state and handle continuation properly
 ## EXECUTION PROTOCOLS:
- 🎯 Show your analysis before taking any action
+- 🎯 Show your analysis of current state before taking any action
- 💾 Initialize document and update frontmatter
+- 💾 Initialize document structure and update frontmatter appropriately
 - 📖 Set up frontmatter `stepsCompleted: [1]` before loading next step
- 🚫 FORBIDDEN to load next step until setup is complete
+- 🚫 FORBIDDEN to load next step until user selects 'C' (Continue)
 ## CONTEXT BOUNDARIES:
- Variables from workflow.md are available in memory
+- Available context: Variables from workflow.md are available in memory
- Previous context = what's in output document + frontmatter
+- Focus: Workflow initialization and document setup only
- Don't assume knowledge from other steps
+- Limits: Don't assume knowledge from other steps or create content yet
- Input document discovery happens in this step
+- Dependencies: Configuration loaded from workflow.md initialization
-## YOUR TASK:
+## Sequence of Instructions (Do not deviate, skip, or optimize)
-Initialize the product brief workflow by detecting continuation state and setting up the document.
+### 1. Check for Existing Workflow State
 ## INITIALIZATION SEQUENCE:
 ### 1. Check for Existing Workflow
 First, check if the output document already exists:
 **Workflow State Detection:**
 - Look for file at `{output_folder}/analysis/*product-brief*.md`
 - If exists, read the complete file including frontmatter
 - If not exists, this is a fresh workflow
@ -43,9 +75,12 @@ First, check if the output document already exists:
 If the document exists and has frontmatter with `stepsCompleted`:
- **STOP here** and load `./step-01b-continue.md` immediately
+**Continuation Protocol:**
 - **STOP immediately** and load `{workflow_path}/steps/step-01b-continue.md`
 - Do not proceed with any initialization tasks
- Let step-01b handle the continuation logic
+- Let step-01b handle all continuation logic
 - This is an auto-proceed situation - no user choice needed
 ### 3. Fresh Workflow Setup (If No Document)
@ -58,7 +93,7 @@ Discover and load context documents using smart discovery:
 **Research Documents (Priority: Sharded → Whole):**
 1. Check for sharded research folder: `{output_folder}/analysis/research/**/*.md`
-2. If folder exists: Load EVERY file in that folder completely for comprehensive research context
+2. If folder exists: Load EVERY file in that folder completely
 3. If no folder exists: Try whole file: `{output_folder}/analysis/research/*research*.md`
 4. Add discovered files to `inputDocuments` frontmatter
@ -72,21 +107,16 @@ Discover and load context documents using smart discovery:
 **Project Documentation (Existing Projects):**
 1. Look for index file: `{output_folder}/**/index.md`
-2. CRITICAL: Load index.md to understand what project files are available
+2. Load index.md to understand what project files are available
 3. Read available files from index to understand existing project context
 4. Add discovered files to `inputDocuments` frontmatter
 **Loading Rules:**
 - Load ALL discovered files completely (no offset/limit)
 - For sharded folders, load ALL files to get complete picture
 - For existing projects, use index.md as guide to what's relevant and loading order
 - Track all successfully loaded files in frontmatter `inputDocuments` array
 #### B. Create Initial Document
-Copy the template from `{installed_path}/product-brief.template.md` to `{default_output_file}`
+**Document Setup:**
-Initialize frontmatter with:
+
 - Copy the template from `{productBriefTemplate}` to `{outputFile}`
 - Initialize frontmatter with proper structure:
 ```yaml
 ---
@ -100,20 +130,17 @@ date: '{{date}}'
 ---
 ```
-#### C. Complete Initialization and Report
+#### C. Present Initialization Results
-Complete setup and report to user:
+**Setup Report to User:**
 "Welcome {{user_name}}! I've set up your product brief workspace for {{project_name}}.
 **Document Setup:**
- Created: `{default_output_file}` from template
+- Created: `{outputFile}` from template
 - Initialized frontmatter with workflow state
 **Input Documents Discovered:**
 Report what was found:
 "Welcome {{user_name}}! I've set up your product brief workspace for {{project_name}}.
 **Documents Found:**
 - Research: {number of research files loaded or "None found"}
 - Brainstorming: {number of brainstorming files loaded or "None found"}
@ -121,31 +148,45 @@ Report what was found:
 **Files loaded:** {list of specific file names or "No additional documents found"}
-Do you have any other documents you'd like me to include, or shall we continue to the next step?
+Do you have any other documents you'd like me to include, or shall we continue to the next step?"
-[C] Continue to product vision discovery"
+### 4. Present MENU OPTIONS
-## SUCCESS METRICS:
+Display: "**Proceeding to product vision discovery...**"
-✅ Existing workflow detected and handed off to step-01b correctly
+#### Menu Handling Logic:
 ✅ Fresh workflow initialized with template and frontmatter
 ✅ Input documents discovered and loaded using sharded-first logic
 ✅ All discovered files tracked in frontmatter `inputDocuments`
-## FAILURE MODES:
+- After setup report is presented, immediately load, read entire file, then execute {nextStepFile}
-❌ Proceeding with fresh initialization when existing workflow exists
+#### EXECUTION RULES:
 ❌ Not updating frontmatter with discovered input documents
 ❌ Creating document without proper template
 ❌ Not checking sharded folders first before whole files
 ❌ Not reporting what documents were found to user
-❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+- This is an initialization step with auto-proceed after setup completion
-❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+- Proceed directly to next step after document setup and reporting
 ❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
-## NEXT STEP:
+## CRITICAL STEP COMPLETION NOTE
-After user selects [C] to continue, load `./step-02-vision.md` to begin the product vision discovery phase.
+ONLY WHEN [setup completion is achieved and frontmatter properly updated], will you then load and read fully `{nextStepFile}` to execute and begin product vision discovery.
-Remember: Do NOT proceed to step-02 until user explicitly selects [C] to continue!
+---
 ## 🚨 SYSTEM SUCCESS/FAILURE METRICS
 ### ✅ SUCCESS:
 - Existing workflow detected and properly handed off to step-01b
 - Fresh workflow initialized with template and proper frontmatter
 - Input documents discovered and loaded using sharded-first logic
 - All discovered files tracked in frontmatter `inputDocuments`
 - Menu presented and user input handled correctly
 - Frontmatter updated with `stepsCompleted: [1]` before proceeding
 ### ❌ SYSTEM FAILURE:
 - Proceeding with fresh initialization when existing workflow exists
 - Not updating frontmatter with discovered input documents
 - Creating document without proper template structure
 - Not checking sharded folders first before whole files
 - Not reporting discovered documents to user clearly
 - Proceeding without user selecting 'C' (Continue)
 **Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
--- a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-01b-continue.md
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-01b-continue.md
@ -1,38 +1,67 @@
 ---
 name: 'step-01b-continue'
 description: 'Resume the product brief workflow from where it was left off, ensuring smooth continuation'
 # Path Definitions
 workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief'
 # File References
 thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.md'
 # Task References
 # (No task references used in this continuation step)
 ---
 # Step 1B: Product Brief Continuation
 ## STEP GOAL:
 Resume the product brief workflow from where it was left off, ensuring smooth continuation with full context restoration.
 ## MANDATORY EXECUTION RULES (READ FIRST):
- 🛑 NEVER generate content without user input
+### Universal Rules:
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🛑 NEVER generate content without user input
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- 📖 CRITICAL: Read the complete step file before taking any action
- ✅ ALWAYS treat this as collaborative discovery between PM peers
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
 - 📋 YOU ARE A FACILITATOR, not a content generator
- 💬 FOCUS on understanding where we left off and continuing appropriately
+
- 🚪 RESUME workflow from exact point where it was interrupted
+### Role Reinforcement:
 - ✅ You are a product-focused Business Analyst facilitator
 - ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
 - ✅ We engage in collaborative dialogue, not command-response
 - ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
 - ✅ Maintain collaborative continuation tone throughout
 ### Step-Specific Rules:
 - 🎯 Focus only on understanding where we left off and continuing appropriately
 - 🚫 FORBIDDEN to modify content completed in previous steps
 - 💬 Approach: Systematic state analysis with clear progress reporting
 - 📋 Resume workflow from exact point where it was interrupted
 ## EXECUTION PROTOCOLS:
- 🎯 Show your analysis of current state before taking action
+- 🎯 Show your analysis of current state before taking any action
 - 💾 Keep existing frontmatter `stepsCompleted` values
 - 📖 Only load documents that were already tracked in `inputDocuments`
- 🚫 FORBIDDEN to modify content completed in previous steps
+- 🚫 FORBIDDEN to discover new input documents during continuation
 ## CONTEXT BOUNDARIES:
- Current document and frontmatter are already loaded
+- Available context: Current document and frontmatter are already loaded
- Previous context = complete document + existing frontmatter
+- Focus: Workflow state analysis and continuation logic only
- Input documents listed in frontmatter were already processed
+- Limits: Don't assume knowledge beyond what's in the document
- Last completed step = `lastStep` value from frontmatter
+- Dependencies: Existing workflow state from previous session
-## YOUR TASK:
+## Sequence of Instructions (Do not deviate, skip, or optimize)
 Resume the product brief workflow from where it was left off, ensuring smooth continuation.
 ## CONTINUATION SEQUENCE:
 ### 1. Analyze Current State
 **State Assessment:**
 Review the frontmatter to understand:
 - `stepsCompleted`: Which steps are already done
@ -40,17 +69,18 @@ Review the frontmatter to understand:
 - `inputDocuments`: What context was already loaded
 - All other frontmatter variables
-### 2. Load All Input Documents
+### 2. Restore Context Documents
-Reload the context documents listed in `inputDocuments`:
+**Context Reloading:**
 - For each document in `inputDocuments`, load the complete file
 - This ensures you have full context for continuation
 - Don't discover new documents - only reload what was previously processed
 - Maintain the same context as when workflow was interrupted
-### 3. Summarize Current Progress
+### 3. Present Current Progress
-Welcome the user back and provide context:
+**Progress Report to User:**
 "Welcome back {{user_name}}! I'm resuming our product brief collaboration for {{project_name}}.
 **Current Progress:**
@ -66,8 +96,9 @@ Welcome the user back and provide context:
 Does this look right, or do you want to make any adjustments before we proceed?"
-### 4. Determine Next Step
+### 4. Determine Continuation Path
 **Next Step Logic:**
 Based on `lastStep` value, determine which step to load next:
 - If `lastStep = 1` → Load `./step-02-vision.md`
@ -76,37 +107,12 @@ Based on `lastStep` value, determine which step to load next:
 - Continue this pattern for all steps
 - If `lastStep = 6` → Workflow already complete
-### 5. Present Continuation Options
+### 5. Handle Workflow Completion
-After presenting current progress, ask:
+**If workflow already complete (`lastStep = 6`):**
 "Ready to continue with Step {nextStepNumber}: {nextStepTitle}?
 [C] Continue to Step {nextStepNumber}"
 ## SUCCESS METRICS:
 ✅ All previous input documents successfully reloaded
 ✅ Current workflow state accurately analyzed and presented
 ✅ User confirms understanding of progress
 ✅ Correct next step identified and prepared for loading
 ## FAILURE MODES:
 ❌ Discovering new input documents instead of reloading existing ones
 ❌ Modifying content from already completed steps
 ❌ Loading wrong next step based on `lastStep` value
 ❌ Proceeding without user confirmation of current state
 ❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
 ❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
 ❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
 ## WORKFLOW ALREADY COMPLETE?
 If `lastStep = 6` (final step completed):
 "Great news! It looks like we've already completed the product brief workflow for {{project_name}}.
-The final document is ready at {default_output_file} with all sections completed through step 6.
+The final document is ready at `{outputFile}` with all sections completed through step 6.
 Would you like me to:
@ -116,8 +122,46 @@ Would you like me to:
 What would be most helpful?"
-## NEXT STEP:
+### 6. Present MENU OPTIONS
-After user selects [C] to continue, load the appropriate next step file based on the `lastStep` value from frontmatter.
+**If workflow not complete:**
 Display: "Ready to continue with Step {nextStepNumber}: {nextStepTitle}?
-Remember: Do NOT load the next step until user explicitly selects [C] to continue!
+**Select an Option:** [C] Continue to Step {nextStepNumber}"
 #### Menu Handling Logic:
 - IF C: Load, read entire file, then execute the appropriate next step file based on `lastStep`
 - IF Any other comments or queries: respond and redisplay menu
 #### EXECUTION RULES:
 - ALWAYS halt and wait for user input after presenting menu
 - ONLY proceed to next step when user selects 'C'
 - User can chat or ask questions about current progress
 ## CRITICAL STEP COMPLETION NOTE
 ONLY WHEN [C continue option] is selected and [current state confirmed], will you then load and read fully the appropriate next step file to resume the workflow.
 ---
 ## 🚨 SYSTEM SUCCESS/FAILURE METRICS
 ### ✅ SUCCESS:
 - All previous input documents successfully reloaded
 - Current workflow state accurately analyzed and presented
 - User confirms understanding of progress before continuation
 - Correct next step identified and prepared for loading
 - Proper continuation path determined based on `lastStep`
 ### ❌ SYSTEM FAILURE:
 - Discovering new input documents instead of reloading existing ones
 - Modifying content from already completed steps
 - Loading wrong next step based on `lastStep` value
 - Proceeding without user confirmation of current state
 - Not maintaining context consistency from previous session
 **Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
--- a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-02-vision.md
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-02-vision.md
@ -1,55 +1,70 @@
 ---
 name: 'step-02-vision'
 description: 'Discover and define the core product vision, problem statement, and unique value proposition'
 # Path Definitions
 workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief'
 # File References
 thisStepFile: '{workflow_path}/steps/step-02-vision.md'
 nextStepFile: '{workflow_path}/steps/step-03-users.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.md'
 # Task References
 advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
 partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
 ---
 # Step 2: Product Vision Discovery
 ## STEP GOAL:
 Conduct comprehensive product vision discovery to define the core problem, solution, and unique value proposition through collaborative analysis.
 ## MANDATORY EXECUTION RULES (READ FIRST):
- 🛑 NEVER generate content without user input
+### Universal Rules:
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🛑 NEVER generate content without user input
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- 📖 CRITICAL: Read the complete step file before taking any action
- ✅ ALWAYS treat this as collaborative discovery between PM peers
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
 - 📋 YOU ARE A FACILITATOR, not a content generator
- 💬 FOCUS on product vision, problem, and solution discovery only
+
- 🎯 COLLABORATIVE discovery, not assumption-based vision crafting
+### Role Reinforcement:
 - ✅ You are a product-focused Business Analyst facilitator
 - ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
 - ✅ We engage in collaborative dialogue, not command-response
 - ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
 - ✅ Maintain collaborative discovery tone throughout
 ### Step-Specific Rules:
 - 🎯 Focus only on product vision, problem, and solution discovery
 - 🚫 FORBIDDEN to generate vision without real user input and collaboration
 - 💬 Approach: Systematic discovery from problem to solution
 - 📋 COLLABORATIVE discovery, not assumption-based vision crafting
 ## EXECUTION PROTOCOLS:
 - 🎯 Show your analysis before taking any action
- ⚠️ Present A/P/C menu after generating executive summary content
+- 💾 Generate vision content collaboratively with user
 - 💾 ONLY save when user chooses C (Continue)
 - 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step
- 🚫 FORBIDDEN to load next step until C is selected
+- 🚫 FORBIDDEN to proceed without user confirmation through menu
 ## COLLABORATION MENUS (A/P/C):
 This step will generate content and present choices:
 - **A (Advanced Elicitation)**: Use discovery protocols to develop deeper insights about product vision
 - **P (Party Mode)**: Bring multiple perspectives to explore product vision and positioning
 - **C (Continue)**: Save the content to the document and proceed to next step
 ## PROTOCOL INTEGRATION:
 - When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
 - When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 ## CONTEXT BOUNDARIES:
- Current document and frontmatter from step 1 are available
+- Available context: Current document and frontmatter from step 1, input documents already loaded in memory
- Input documents already loaded are in memory
+- Focus: This will be the first content section appended to the document
- This will be the first content section appended to the document
+- Limits: Focus on clear, compelling product vision and problem statement
- Focus on clear, compelling product vision and problem statement
+- Dependencies: Document initialization from step-01 must be complete
-## YOUR TASK:
+## Sequence of Instructions (Do not deviate, skip, or optimize)
-Conduct comprehensive product vision discovery to define the core problem, solution, and unique value proposition.
+### 1. Begin Vision Discovery
-## VISION DISCOVERY SEQUENCE:
+**Opening Conversation:**
 ### 1. Begin Vision Discovery Conversation
 Start with open-ended vision exploration:
 "As your PM peer, I'm excited to help you shape the vision for {{project_name}}. Let's start with the foundation.
 **Tell me about the product you envision:**
@ -63,56 +78,45 @@ Let's start with the problem space before we get into solutions."
 ### 2. Deep Problem Understanding
-Explore the problem from multiple angles:
+**Problem Discovery:**
 Explore the problem from multiple angles using targeted questions:
-#### Problem Discovery Questions:
+- How do people currently solve this problem?
-
+- What's frustrating about current solutions?
- "How do people currently solve this problem?"
+- What happens if this problem goes unsolved?
- "What's frustrating about current solutions?"
+- Who feels this pain most intensely?
 - "What happens if this problem goes unsolved?"
 - "Who feels this pain most intensely?"
 #### Impact Exploration:
 - "What's the real cost of this problem?"
 - "How does it affect people's daily lives or work?"
 - "What are the emotional and practical consequences?"
 - "Why is solving this important right now?"
 ### 3. Current Solutions Analysis
-Understand the competitive landscape:
+**Competitive Landscape:**
- "What solutions exist today?"
+- What solutions exist today?
- "Where do they fall short?"
+- Where do they fall short?
- "What gaps are they leaving open?"
+- What gaps are they leaving open?
- "Why haven't existing solutions solved this completely?"
+- Why haven't existing solutions solved this completely?
 ### 4. Solution Vision
-Craft the proposed solution collaboratively:
+**Collaborative Solution Crafting:**
- "If we could solve this perfectly, what would that look like?"
+- If we could solve this perfectly, what would that look like?
- "What's the simplest way we could make a meaningful difference?"
+- What's the simplest way we could make a meaningful difference?
- "What makes your approach different from what's out there?"
+- What makes your approach different from what's out there?
- "What would make users say 'this is exactly what I needed'?"
+- What would make users say 'this is exactly what I needed'?
 ### 5. Unique Differentiators
-Identify what makes this product special:
+**Competitive Advantage:**
- "What's your unfair advantage?"
+- What's your unfair advantage?
- "What would be hard for competitors to copy?"
+- What would be hard for competitors to copy?
- "What insight or approach is uniquely yours?"
+- What insight or approach is uniquely yours?
- "Why is now the right time for this solution?"
+- Why is now the right time for this solution?
 ### 6. Generate Executive Summary Content
-Prepare the content to append to the document:
+**Content to Append:**
-
+Prepare the following structure for document append:
 #### Content Structure:
 When saving to document, append these Level 2 and Level 3 sections:
 ```markdown
 ## Executive Summary
@ -144,80 +148,56 @@ When saving to document, append these Level 2 and Level 3 sections:
 [Key differentiators based on conversation]
 ```
-### 7. Present Content and Menu
+### 7. Present MENU OPTIONS
-Show the generated content and present choices:
+**Content Presentation:**
 "I've drafted the executive summary and core vision based on our conversation. This captures the essence of {{project_name}} and what makes it special.
 **Here's what I'll add to the document:**
 [Show the complete markdown content from step 6]
-**What would you like to do?**
+**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
 [A] Advanced Elicitation - Let's dive deeper and refine the product vision
 [P] Party Mode - Bring different perspectives to explore positioning and differentiation
 [C] Continue - Save this to the document and move to next step"
-### 8. Handle Menu Selection
+#### Menu Handling Logic:
-#### If 'A' (Advanced Elicitation):
+- IF A: Execute {advancedElicitationTask} with current vision content to dive deeper and refine
 - IF P: Execute {partyModeWorkflow} to bring different perspectives to positioning and differentiation
 - IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2], then only then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current vision content
+#### EXECUTION RULES:
 - Process the enhanced vision insights that come back
 - Ask user: "Accept these improvements to the product vision? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
 - If no: Keep original content, then return to A/P/C menu
-#### If 'P' (Party Mode):
+- ALWAYS halt and wait for user input after presenting menu
 - ONLY proceed to next step when user selects 'C'
 - After other menu items execution, return to this menu with updated content
 - User can chat or ask questions - always respond and then end with display again of the menu options
- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current vision content
+## CRITICAL STEP COMPLETION NOTE
 - Process the collaborative vision exploration and positioning insights
 - Ask user: "Accept these changes to the product vision? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
 - If no: Keep original content, then return to A/P/C menu
-#### If 'C' (Continue):
+ONLY WHEN [C continue option] is selected and [vision content finalized and saved to document with frontmatter updated], will you then load and read fully `{nextStepFile}` to execute and begin target user discovery.
- Append the final content to `{default_output_file}`
+---
 - Update frontmatter: `stepsCompleted: [1, 2]`
 - Load `./step-03-users.md`
-## APPEND TO DOCUMENT:
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-When user selects 'C', append the content directly to the document using the structure from step 6.
+### ✅ SUCCESS:
-## SUCCESS METRICS:
+- Clear problem statement that resonates with target users
 - Compelling solution vision that addresses the core problem
 - Unique differentiators that provide competitive advantage
 - Executive summary that captures the product essence
 - A/P/C menu presented and handled correctly with proper task execution
 - Content properly appended to document when C selected
 - Frontmatter updated with stepsCompleted: [1, 2]
-✅ Clear problem statement that resonates with target users
+### ❌ SYSTEM FAILURE:
 ✅ Compelling solution vision that addresses the core problem
 ✅ Unique differentiators that provide competitive advantage
 ✅ Executive summary that captures the product essence
 ✅ A/P/C menu presented and handled correctly
 ✅ Content properly appended to document when C selected
-## FAILURE MODES:
+- Accepting vague problem statements without pushing for specificity
 - Creating solution vision without fully understanding the problem
 - Missing unique differentiators or competitive insights
 - Generating vision without real user input and collaboration
 - Not presenting standard A/P/C menu after content generation
 - Appending content without user selecting 'C'
 - Not updating frontmatter properly
-❌ Accepting vague problem statements without pushing for specificity
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
 ❌ Creating solution vision without fully understanding the problem
 ❌ Missing unique differentiators or competitive insights
 ❌ Generating vision without real user input and collaboration
 ❌ Not presenting A/P/C menu after content generation
 ❌ Appending content without user selecting 'C'
 ❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
 ❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
 ❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
 ## CONTEXT INPUTS:
 If research or brainstorming documents were loaded in step 1, incorporate insights from those documents into the vision discovery:
 - "I see from the research that..."
 - "In the brainstorming session, you mentioned..."
 - "The project documentation suggests..."
 ## NEXT STEP:
 After user selects 'C' and content is saved to document, load `./step-03-users.md` to define target users.
 Remember: Do NOT proceed to step-03 until user explicitly selects 'C' from the A/P/C menu and content is saved!
--- a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-03-users.md
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-03-users.md
@ -1,55 +1,70 @@
 ---
 name: 'step-03-users'
 description: 'Define target users with rich personas and map their key interactions with the product'
 # Path Definitions
 workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief'
 # File References
 thisStepFile: '{workflow_path}/steps/step-03-users.md'
 nextStepFile: '{workflow_path}/steps/step-04-metrics.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.md'
 # Task References
 advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
 partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
 ---
 # Step 3: Target Users Discovery
 ## STEP GOAL:
 Define target users with rich personas and map their key interactions with the product through collaborative user research and journey mapping.
 ## MANDATORY EXECUTION RULES (READ FIRST):
- 🛑 NEVER generate content without user input
+### Universal Rules:
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🛑 NEVER generate content without user input
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- 📖 CRITICAL: Read the complete step file before taking any action
- ✅ ALWAYS treat this as collaborative discovery between PM peers
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
 - 📋 YOU ARE A FACILITATOR, not a content generator
- 💬 FOCUS on defining who this product serves and how they interact with it
+
- 🎯 COLLABORATIVE persona development and user journey mapping
+### Role Reinforcement:
 - ✅ You are a product-focused Business Analyst facilitator
 - ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
 - ✅ We engage in collaborative dialogue, not command-response
 - ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
 - ✅ Maintain collaborative discovery tone throughout
 ### Step-Specific Rules:
 - 🎯 Focus only on defining who this product serves and how they interact with it
 - 🚫 FORBIDDEN to create generic user profiles without specific details
 - 💬 Approach: Systematic persona development with journey mapping
 - 📋 COLLABORATIVE persona development, not assumption-based user creation
 ## EXECUTION PROTOCOLS:
 - 🎯 Show your analysis before taking any action
- ⚠️ Present A/P/C menu after generating user segments content
+- 💾 Generate user personas and journeys collaboratively with user
 - 💾 ONLY save when user chooses C (Continue)
 - 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
- 🚫 FORBIDDEN to load next step until C is selected
+- 🚫 FORBIDDEN to proceed without user confirmation through menu
 ## COLLABORATION MENUS (A/P/C):
 This step will generate content and present choices:
 - **A (Advanced Elicitation)**: Use discovery protocols to develop deeper user insights
 - **P (Party Mode)**: Bring multiple perspectives to validate user segments and journeys
 - **C (Continue)**: Save the content to the document and proceed to next step
 ## PROTOCOL INTEGRATION:
 - When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
 - When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 ## CONTEXT BOUNDARIES:
- Current document and frontmatter from previous steps are available
+- Available context: Current document and frontmatter from previous steps, product vision and problem already defined
- Product vision and problem already defined in document
+- Focus: Creating vivid, actionable user personas that align with product vision
- Input documents from step 1 may contain user research or insights
+- Limits: Focus on users who directly experience the problem or benefit from the solution
- Focus on creating vivid, actionable user personas
+- Dependencies: Product vision and problem statement from step-02 must be complete
-## YOUR TASK:
+## Sequence of Instructions (Do not deviate, skip, or optimize)
 Define target users with rich personas and map their key interactions with the product.
 ## USER DISCOVERY SEQUENCE:
 ### 1. Begin User Discovery
-Start with user segmentation exploration:
+**Opening Exploration:**
 "Now that we understand what {{project_name}} does, let's define who it's for.
 **User Discovery:**
@ -63,10 +78,9 @@ Let's start by identifying the main user groups."
 ### 2. Primary User Segment Development
 **Persona Development Process:**
 For each primary user segment, create rich personas:
 #### Persona Development Process:
 **Name & Context:**
 - Give them a realistic name and brief backstory
@ -84,7 +98,7 @@ For each primary user segment, create rich personas:
 - What would success look like for them?
 - What would make them say "this is exactly what I needed"?
-#### Primary User Questions:
+**Primary User Questions:**
 - "Tell me about a typical person who would use {{project_name}}"
 - "What's their day like? Where does our product fit in?"
@ -92,9 +106,7 @@ For each primary user segment, create rich personas:
 ### 3. Secondary User Segment Exploration
-Identify and develop secondary user segments:
+**Secondary User Considerations:**
 #### Secondary User Considerations:
 - "Who else benefits from this solution, even if they're not the primary user?"
 - "Are there admin, support, or oversight roles we should consider?"
@ -103,17 +115,16 @@ Identify and develop secondary user segments:
 ### 4. User Journey Mapping
 **Journey Elements:**
 Map key interactions for each user segment:
 #### Journey Elements:
 - **Discovery:** How do they find out about the solution?
 - **Onboarding:** What's their first experience like?
 - **Core Usage:** How do they use the product day-to-day?
 - **Success Moment:** When do they realize the value?
 - **Long-term:** How does it become part of their routine?
-#### Journey Questions:
+**Journey Questions:**
 - "Walk me through how [Persona Name] would discover and start using {{project_name}}"
 - "What's their 'aha!' moment?"
@ -121,11 +132,8 @@ Map key interactions for each user segment:
 ### 5. Generate Target Users Content
-Prepare the content to append to the document:
+**Content to Append:**
-
+Prepare the following structure for document append:
 #### Content Structure:
 When saving to document, append these Level 2 and Level 3 sections:
 ```markdown
 ## Target Users
@ -143,84 +151,56 @@ When saving to document, append these Level 2 and Level 3 sections:
 [User journey content based on conversation, or N/A if not discussed]
 ```
-### 6. Present Content and Menu
+### 6. Present MENU OPTIONS
-Show the generated user content and present choices:
+**Content Presentation:**
 "I've mapped out who {{project_name}} serves and how they'll interact with it. This helps us ensure we're building something that real people will love to use.
 **Here's what I'll add to the document:**
 [Show the complete markdown content from step 5]
-**What would you like to do?**
+**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
 [A] Advanced Elicitation - Let's dive deeper into these user personas and journeys
 [P] Party Mode - Bring different perspectives to validate our user understanding
 [C] Continue - Save this to the document and move to next step"
-### 7. Handle Menu Selection
+#### Menu Handling Logic:
-#### If 'A' (Advanced Elicitation):
+- IF A: Execute {advancedElicitationTask} with current user content to dive deeper into personas and journeys
 - IF P: Execute {partyModeWorkflow} to bring different perspectives to validate user understanding
 - IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3], then only then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)
- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current user content
+#### EXECUTION RULES:
 - Process the enhanced user insights that come back
 - Ask user: "Accept these improvements to the target users? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
 - If no: Keep original content, then return to A/P/C menu
-#### If 'P' (Party Mode):
+- ALWAYS halt and wait for user input after presenting menu
 - ONLY proceed to next step when user selects 'C'
 - After other menu items execution, return to this menu with updated content
 - User can chat or ask questions - always respond and then end with display again of the menu options
- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current user personas
+## CRITICAL STEP COMPLETION NOTE
 - Process the collaborative user validation and additional insights
 - Ask user: "Accept these changes to the target users? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
 - If no: Keep original content, then return to A/P/C menu
-#### If 'C' (Continue):
+ONLY WHEN [C continue option] is selected and [user personas finalized and saved to document with frontmatter updated], will you then load and read fully `{nextStepFile}` to execute and begin success metrics definition.
- Append the final content to `{default_output_file}`
+---
 - Update frontmatter: `stepsCompleted: [1, 2, 3]`
 - Load `./step-04-metrics.md`
-## APPEND TO DOCUMENT:
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-When user selects 'C', append the content directly to the document using the structure from step 5.
+### ✅ SUCCESS:
-## SUCCESS METRICS:
+- Rich, believable user personas with clear motivations
 - Clear distinction between primary and secondary users
 - User journeys that show key interaction points and value creation
 - User segments that align with product vision and problem statement
 - A/P/C menu presented and handled correctly with proper task execution
 - Content properly appended to document when C selected
 - Frontmatter updated with stepsCompleted: [1, 2, 3]
-✅ Rich, believable user personas with clear motivations
+### ❌ SYSTEM FAILURE:
 ✅ Clear distinction between primary and secondary users
 ✅ User journeys that show key interaction points
 ✅ User segments that align with product vision and problem
 ✅ A/P/C menu presented and handled correctly
 ✅ Content properly appended to document when C selected
-## FAILURE MODES:
+- Creating generic user profiles without specific details
 - Missing key user segments that are important to success
 - User journeys that don't show how the product creates value
 - Not connecting user needs back to the problem statement
 - Not presenting standard A/P/C menu after content generation
 - Appending content without user selecting 'C'
 - Not updating frontmatter properly
-❌ Creating generic user profiles without specific details
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
 ❌ Missing key user segments that are important to success
 ❌ User journeys that don't show how the product creates value
 ❌ Not connecting user needs back to the problem statement
 ❌ Not presenting A/P/C menu after content generation
 ❌ Appending content without user selecting 'C'
 ❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
 ❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
 ❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
 ## USER INSIGHTS SOURCES:
 If user research documents were loaded in step 1, incorporate those insights:
 - "From the user research we loaded, I see that..."
 - "The interviews suggest users are struggling with..."
 - "The survey data indicates preferences for..."
 ## OPTIONAL CONTENT:
 User journey section is optional - only include if the journey mapping reveals important insights about how users will interact with the product and where value is created.
 ## NEXT STEP:
 After user selects 'C' and content is saved to document, load `./step-04-metrics.md` to define success metrics.
 Remember: Do NOT proceed to step-04 until user explicitly selects 'C' from the A/P/C menu and content is saved!
--- a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-04-metrics.md
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-04-metrics.md
@ -1,55 +1,70 @@
 ---
 name: 'step-04-metrics'
 description: 'Define comprehensive success metrics that include user success, business objectives, and key performance indicators'
 # Path Definitions
 workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief'
 # File References
 thisStepFile: '{workflow_path}/steps/step-04-metrics.md'
 nextStepFile: '{workflow_path}/steps/step-05-scope.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.md'
 # Task References
 advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
 partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
 ---
 # Step 4: Success Metrics Definition
 ## STEP GOAL:
 Define comprehensive success metrics that include user success, business objectives, and key performance indicators through collaborative metric definition aligned with product vision and user value.
 ## MANDATORY EXECUTION RULES (READ FIRST):
- 🛑 NEVER generate content without user input
+### Universal Rules:
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🛑 NEVER generate content without user input
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- 📖 CRITICAL: Read the complete step file before taking any action
- ✅ ALWAYS treat this as collaborative discovery between PM peers
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
 - 📋 YOU ARE A FACILITATOR, not a content generator
- 💬 FOCUS on defining measurable success criteria and business objectives
+
- 🎯 COLLABORATIVE metric definition that connects to user value
+### Role Reinforcement:
 - ✅ You are a product-focused Business Analyst facilitator
 - ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
 - ✅ We engage in collaborative dialogue, not command-response
 - ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
 - ✅ Maintain collaborative discovery tone throughout
 ### Step-Specific Rules:
 - 🎯 Focus only on defining measurable success criteria and business objectives
 - 🚫 FORBIDDEN to create vague metrics that can't be measured or tracked
 - 💬 Approach: Systematic metric definition that connects user value to business success
 - 📋 COLLABORATIVE metric definition that drives actionable decisions
 ## EXECUTION PROTOCOLS:
 - 🎯 Show your analysis before taking any action
- ⚠️ Present A/P/C menu after generating success metrics content
+- 💾 Generate success metrics collaboratively with user
 - 💾 ONLY save when user chooses C (Continue)
 - 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step
- 🚫 FORBIDDEN to load next step until C is selected
+- 🚫 FORBIDDEN to proceed without user confirmation through menu
 ## COLLABORATION MENUS (A/P/C):
 This step will generate content and present choices:
 - **A (Advanced Elicitation)**: Use discovery protocols to develop deeper success metric insights
 - **P (Party Mode)**: Bring multiple perspectives to validate comprehensive success metrics
 - **C (Continue)**: Save the content to the document and proceed to next step
 ## PROTOCOL INTEGRATION:
 - When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
 - When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 ## CONTEXT BOUNDARIES:
- Current document and frontmatter from previous steps are available
+- Available context: Current document and frontmatter from previous steps, product vision and target users already defined
- Product vision and target users already defined
+- Focus: Creating measurable, actionable success criteria that align with product strategy
- Connect metrics directly to user value and business objectives
+- Limits: Focus on metrics that drive decisions and demonstrate real value creation
- Focus on measurable, actionable success criteria
+- Dependencies: Product vision and user personas from previous steps must be complete
-## YOUR TASK:
+## Sequence of Instructions (Do not deviate, skip, or optimize)
 Define comprehensive success metrics that include user success, business objectives, and key performance indicators.
 ## SUCCESS METRICS DISCOVERY SEQUENCE:
 ### 1. Begin Success Metrics Discovery
-Start with user-centered success definition:
+**Opening Exploration:**
 "Now that we know who {{project_name}} serves and what problem it solves, let's define what success looks like.
 **Success Discovery:**
@ -62,34 +77,32 @@ Let's start with the user perspective."
 ### 2. User Success Metrics
 **User Success Questions:**
 Define success from the user's perspective:
 #### User Success Questions:
 - "What outcome are users trying to achieve?"
 - "How will they know the product is working for them?"
 - "What's the moment where they realize this is solving their problem?"
 - "What behaviors indicate users are getting value?"
-#### User Success Exploration:
+**User Success Exploration:**
 Guide from vague to specific metrics:
 - Guide from vague to specific metrics
 - "Users are happy" → "Users complete [key action] within [timeframe]"
 - "Product is useful" → "Users return [frequency] and use [core feature]"
 - Focus on outcomes and behaviors, not just satisfaction scores
 ### 3. Business Objectives
 **Business Success Questions:**
 Define business success metrics:
 #### Business Success Questions:
 - "What does success look like for the business at 3 months? 12 months?"
 - "Are we measuring revenue, user growth, engagement, something else?"
 - "What business metrics would make you say 'this is working'?"
 - "How does this product contribute to broader company goals?"
-#### Business Success Categories:
+**Business Success Categories:**
 - **Growth Metrics:** User acquisition, market penetration
 - **Engagement Metrics:** Usage patterns, retention, satisfaction
@ -98,16 +111,15 @@ Define business success metrics:
 ### 4. Key Performance Indicators
 **KPI Development Process:**
 Define specific, measurable KPIs:
 #### KPI Development Process:
 - Transform objectives into measurable indicators
 - Ensure each KPI has a clear measurement method
 - Define targets and timeframes where appropriate
 - Include leading indicators that predict success
-#### KPI Examples:
+**KPI Examples:**
 - User acquisition: "X new users per month"
 - Engagement: "Y% of users complete core journey weekly"
@ -115,10 +127,9 @@ Define specific, measurable KPIs:
 ### 5. Connect Metrics to Strategy
 **Strategic Alignment:**
 Ensure metrics align with product vision and user needs:
 #### Strategic Alignment:
 - Connect each metric back to the product vision
 - Ensure user success metrics drive business success
 - Validate that metrics measure what truly matters
@ -126,11 +137,8 @@ Ensure metrics align with product vision and user needs:
 ### 6. Generate Success Metrics Content
-Prepare the content to append to the document:
+**Content to Append:**
-
+Prepare the following structure for document append:
 #### Content Structure:
 When saving to document, append these Level 2 and Level 3 sections:
 ```markdown
 ## Success Metrics
@ -146,93 +154,56 @@ When saving to document, append these Level 2 and Level 3 sections:
 [Key performance indicators content based on conversation, or N/A if not discussed]
 ```
-### 7. Present Content and Menu
+### 7. Present MENU OPTIONS
-Show the generated metrics content and present choices:
+**Content Presentation:**
 "I've defined success metrics that will help us track whether {{project_name}} is creating real value for users and achieving business objectives.
 **Here's what I'll add to the document:**
 [Show the complete markdown content from step 6]
-**What would you like to do?**
+**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
 [A] Advanced Elicitation - Let's dive deeper into these success metrics
 [P] Party Mode - Bring different perspectives to validate comprehensive metrics
 [C] Continue - Save this to the document and move to next step"
-### 8. Handle Menu Selection
+#### Menu Handling Logic:
-#### If 'A' (Advanced Elicitation):
+- IF A: Execute {advancedElicitationTask} with current metrics content to dive deeper into success metric insights
 - IF P: Execute {partyModeWorkflow} to bring different perspectives to validate comprehensive metrics
 - IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3, 4], then only then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current metrics content
+#### EXECUTION RULES:
 - Process the enhanced metric insights that come back
 - Ask user: "Accept these improvements to the success metrics? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
 - If no: Keep original content, then return to A/P/C menu
-#### If 'P' (Party Mode):
+- ALWAYS halt and wait for user input after presenting menu
 - ONLY proceed to next step when user selects 'C'
 - After other menu items execution, return to this menu with updated content
 - User can chat or ask questions - always respond and then end with display again of the menu options
- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current success metrics
+## CRITICAL STEP COMPLETION NOTE
 - Process the collaborative metric validation and additional insights
 - Ask user: "Accept these changes to the success metrics? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
 - If no: Keep original content, then return to A/P/C menu
-#### If 'C' (Continue):
+ONLY WHEN [C continue option] is selected and [success metrics finalized and saved to document with frontmatter updated], will you then load and read fully `{nextStepFile}` to execute and begin MVP scope definition.
- Append the final content to `{default_output_file}`
+---
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
 - Load `./step-05-scope.md`
-## APPEND TO DOCUMENT:
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-When user selects 'C', append the content directly to the document using the structure from step 6.
+### ✅ SUCCESS:
-## SUCCESS METRICS:
+- User success metrics that focus on outcomes and behaviors
 - Clear business objectives aligned with product strategy
 - Specific, measurable KPIs with defined targets and timeframes
 - Metrics that connect user value to business success
 - A/P/C menu presented and handled correctly with proper task execution
 - Content properly appended to document when C selected
 - Frontmatter updated with stepsCompleted: [1, 2, 3, 4]
-✅ User success metrics that focus on outcomes and behaviors
+### ❌ SYSTEM FAILURE:
 ✅ Clear business objectives aligned with product strategy
 ✅ Specific, measurable KPIs with defined targets
 ✅ Metrics that connect user value to business success
 ✅ A/P/C menu presented and handled correctly
 ✅ Content properly appended to document when C selected
-## FAILURE MODES:
+- Vague success metrics that can't be measured or tracked
 - Business objectives disconnected from user success
 - Too many metrics or missing critical success indicators
 - Metrics that don't drive actionable decisions
 - Not presenting standard A/P/C menu after content generation
 - Appending content without user selecting 'C'
 - Not updating frontmatter properly
-❌ Vague success metrics that can't be measured or tracked
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
 ❌ Business objectives disconnected from user success
 ❌ Too many metrics or missing critical success indicators
 ❌ Metrics that don't drive actionable decisions
 ❌ Not presenting A/P/C menu after content generation
 ❌ Appending content without user selecting 'C'
 ❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
 ❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
 ❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
 ## METRIC QUALITY CRITERIA:
 **Good Metrics:**
 - Specific and measurable
 - Connected to user value or business outcomes
 - Actionable - they inform decisions
 - Leading indicators when possible
 - Easy to track and understand
 **Avoid:**
 - Vanity metrics that look good but don't drive decisions
 - Metrics without clear measurement methods
 - Too many competing priorities
 - Metrics disconnected from product strategy
 ## OPTIONAL SECTIONS:
 Business Objectives and KPIs sections are optional - include them if the discussion yields meaningful, specific objectives and indicators. If not, focus on the core user success metrics section.
 ## NEXT STEP:
 After user selects 'C' and content is saved to document, load `./step-05-scope.md` to define MVP scope.
 Remember: Do NOT proceed to step-05 until user explicitly selects 'C' from the A/P/C menu and content is saved!
--- a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-05-scope.md
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-05-scope.md
@ -1,55 +1,70 @@
 ---
 name: 'step-05-scope'
 description: 'Define MVP scope with clear boundaries and outline future vision while managing scope creep'
 # Path Definitions
 workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief'
 # File References
 thisStepFile: '{workflow_path}/steps/step-05-scope.md'
 nextStepFile: '{workflow_path}/steps/step-06-complete.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.md'
 # Task References
 advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
 partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
 ---
 # Step 5: MVP Scope Definition
 ## STEP GOAL:
 Define MVP scope with clear boundaries and outline future vision through collaborative scope negotiation that balances ambition with realism.
 ## MANDATORY EXECUTION RULES (READ FIRST):
- 🛑 NEVER generate content without user input
+### Universal Rules:
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🛑 NEVER generate content without user input
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- 📖 CRITICAL: Read the complete step file before taking any action
- ✅ ALWAYS treat this as collaborative discovery between PM peers
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
 - 📋 YOU ARE A FACILITATOR, not a content generator
- 💬 FOCUS on defining minimum viable scope and future vision
+
- 🎯 COLLABORATIVE scope negotiation that balances ambition with realism
+### Role Reinforcement:
 - ✅ You are a product-focused Business Analyst facilitator
 - ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
 - ✅ We engage in collaborative dialogue, not command-response
 - ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
 - ✅ Maintain collaborative discovery tone throughout
 ### Step-Specific Rules:
 - 🎯 Focus only on defining minimum viable scope and future vision
 - 🚫 FORBIDDEN to create MVP scope that's too large or includes non-essential features
 - 💬 Approach: Systematic scope negotiation with clear boundary setting
 - 📋 COLLABORATIVE scope definition that prevents scope creep
 ## EXECUTION PROTOCOLS:
 - 🎯 Show your analysis before taking any action
- ⚠️ Present A/P/C menu after generating scope content
+- 💾 Generate MVP scope collaboratively with user
 - 💾 ONLY save when user chooses C (Continue)
 - 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before loading next step
- 🚫 FORBIDDEN to load next step until C is selected
+- 🚫 FORBIDDEN to proceed without user confirmation through menu
 ## COLLABORATION MENUS (A/P/C):
 This step will generate content and present choices:
 - **A (Advanced Elicitation)**: Use discovery protocols to optimize scope definition
 - **P (Party Mode)**: Bring multiple perspectives to validate MVP scope
 - **C (Continue)**: Save the content to the document and proceed to next step
 ## PROTOCOL INTEGRATION:
 - When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
 - When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 ## CONTEXT BOUNDARIES:
- Current document and frontmatter from previous steps are available
+- Available context: Current document and frontmatter from previous steps, product vision, users, and success metrics already defined
- Product vision, users, and success metrics already defined
+- Focus: Defining what's essential for MVP vs. future enhancements
- Focus on defining what's essential for MVP vs. future enhancements
+- Limits: Balance user needs with implementation feasibility
- Balance user needs with implementation feasibility
+- Dependencies: Product vision, user personas, and success metrics from previous steps must be complete
-## YOUR TASK:
+## Sequence of Instructions (Do not deviate, skip, or optimize)
 Define MVP scope with clear boundaries and outline future vision while managing scope creep.
 ## MVP SCOPE DISCOVERY SEQUENCE:
 ### 1. Begin Scope Definition
-Start with MVP concept exploration:
+**Opening Exploration:**
 "Now that we understand what {{project_name}} does, who it serves, and how we'll measure success, let's define what we need to build first.
 **Scope Discovery:**
@ -62,16 +77,15 @@ Let's start with the MVP mindset: what's the smallest version that creates real
 ### 2. MVP Core Features Definition
 **MVP Feature Questions:**
 Define essential features for minimum viable product:
 #### MVP Feature Questions:
 - "What's the core functionality that must work?"
 - "Which features directly address the main problem we're solving?"
 - "What would users consider 'incomplete' if it was missing?"
 - "What features create the 'aha!' moment we discussed earlier?"
-#### MVP Criteria:
+**MVP Criteria:**
 - **Solves Core Problem:** Addresses the main pain point effectively
 - **User Value:** Creates meaningful outcome for target users
@ -80,16 +94,15 @@ Define essential features for minimum viable product:
 ### 3. Out of Scope Boundaries
 **Out of Scope Exploration:**
 Define what explicitly won't be in MVP:
 #### Out of Scope Exploration:
 - "What features would be nice to have but aren't essential?"
 - "What functionality could wait for version 2.0?"
 - "What are we intentionally saying 'no' to for now?"
 - "How do we communicate these boundaries to stakeholders?"
-#### Boundary Setting:
+**Boundary Setting:**
 - Clear communication about what's not included
 - Rationale for deferring certain features
@ -98,16 +111,15 @@ Define what explicitly won't be in MVP:
 ### 4. MVP Success Criteria
 **Success Validation:**
 Define what makes the MVP successful:
 #### Success Validation:
 - "How will we know the MVP is successful?"
 - "What metrics will indicate we should proceed beyond MVP?"
 - "What user feedback signals validate our approach?"
 - "What's the decision point for scaling beyond MVP?"
-#### Success Gates:
+**Success Gates:**
 - User adoption metrics
 - Problem validation evidence
@ -116,16 +128,15 @@ Define what makes the MVP successful:
 ### 5. Future Vision Exploration
 **Vision Questions:**
 Define the longer-term product vision:
 #### Vision Questions:
 - "If this is wildly successful, what does it become in 2-3 years?"
 - "What capabilities would we add with more resources?"
 - "How does the MVP evolve into the full product vision?"
 - "What markets or user segments could we expand to?"
-#### Future Features:
+**Future Features:**
 - Post-MVP enhancements that build on core functionality
 - Scale considerations and growth capabilities
@ -134,11 +145,8 @@ Define the longer-term product vision:
 ### 6. Generate MVP Scope Content
-Prepare the content to append to the document:
+**Content to Append:**
-
+Prepare the following structure for document append:
 #### Content Structure:
 When saving to document, append these Level 2 and Level 3 sections:
 ```markdown
 ## MVP Scope
@ -160,92 +168,56 @@ When saving to document, append these Level 2 and Level 3 sections:
 [Future vision content based on conversation, or N/A if not discussed]
 ```
-### 7. Present Content and Menu
+### 7. Present MENU OPTIONS
-Show the generated scope content and present choices:
+**Content Presentation:**
 "I've defined the MVP scope for {{project_name}} that balances delivering real value with realistic boundaries. This gives us a clear path forward while keeping our options open for future growth.
 **Here's what I'll add to the document:**
 [Show the complete markdown content from step 6]
-**What would you like to do?**
+**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
 [A] Advanced Elicitation - Let's optimize this scope definition
 [P] Party Mode - Bring different perspectives to validate MVP scope
 [C] Continue - Save this to the document and move to final step"
-### 8. Handle Menu Selection
+#### Menu Handling Logic:
-#### If 'A' (Advanced Elicitation):
+- IF A: Execute {advancedElicitationTask} with current scope content to optimize scope definition
 - IF P: Execute {partyModeWorkflow} to bring different perspectives to validate MVP scope
 - IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3, 4, 5], then only then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current scope content
+#### EXECUTION RULES:
 - Process the enhanced scope insights that come back
 - Ask user: "Accept these improvements to the MVP scope? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
 - If no: Keep original content, then return to A/P/C menu
-#### If 'P' (Party Mode):
+- ALWAYS halt and wait for user input after presenting menu
 - ONLY proceed to next step when user selects 'C'
 - After other menu items execution, return to this menu with updated content
 - User can chat or ask questions - always respond and then end with display again of the menu options
- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current MVP scope
+## CRITICAL STEP COMPLETION NOTE
 - Process the collaborative scope validation and prioritization
 - Ask user: "Accept these changes to the MVP scope? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
 - If no: Keep original content, then return to A/P/C menu
-#### If 'C' (Continue):
+ONLY WHEN [C continue option] is selected and [MVP scope finalized and saved to document with frontmatter updated], will you then load and read fully `{nextStepFile}` to execute and complete the product brief workflow.
- Append the final content to `{default_output_file}`
+---
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
 - Load `./step-06-complete.md`
-## APPEND TO DOCUMENT:
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-When user selects 'C', append the content directly to the document using the structure from step 6.
+### ✅ SUCCESS:
-## SUCCESS METRICS:
+- MVP features that solve the core problem effectively
 - Clear out-of-scope boundaries that prevent scope creep
 - Success criteria that validate MVP approach and inform go/no-go decisions
 - Future vision that inspires while maintaining focus on MVP
 - A/P/C menu presented and handled correctly with proper task execution
 - Content properly appended to document when C selected
 - Frontmatter updated with stepsCompleted: [1, 2, 3, 4, 5]
-✅ MVP features that solve the core problem effectively
+### ❌ SYSTEM FAILURE:
 ✅ Clear out-of-scope boundaries that prevent scope creep
 ✅ Success criteria that validate MVP approach
 ✅ Future vision that inspires while maintaining focus
 ✅ A/P/C menu presented and handled correctly
 ✅ Content properly appended to document when C selected
-## FAILURE MODES:
+- MVP scope too large or includes non-essential features
 - Missing clear boundaries leading to scope creep
 - No success criteria to validate MVP approach
 - Future vision disconnected from MVP foundation
 - Not presenting standard A/P/C menu after content generation
 - Appending content without user selecting 'C'
 - Not updating frontmatter properly
-❌ MVP scope too large or includes non-essential features
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
 ❌ Missing clear boundaries leading to scope creep
 ❌ No success criteria to validate MVP approach
 ❌ Future vision disconnected from MVP foundation
 ❌ Not presenting A/P/C menu after content generation
 ❌ Appending content without user selecting 'C'
 ❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
 ❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
 ❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
 ## SCOPE NEGOTIATION PRINCIPLES:
 **MVP Mindset:**
 - Minimum features that create maximum user value
 - Fast learning and iteration capability
 - Clear success criteria for next phase decisions
 - Stakeholder alignment on boundaries
 **Scope Creep Prevention:**
 - Explicit out-of-scope documentation
 - Rationale for feature deferral
 - Clear roadmap for future additions
 - Regular scope validation against core problem
 ## OPTIONAL SECTIONS:
 Future Vision and MVP Success Criteria sections are optional - include them if the discussion yields meaningful insights about long-term direction and success validation. Core Features and Out of Scope are essential sections.
 ## NEXT STEP:
 After user selects 'C' and content is saved to document, load `./step-06-complete.md` to complete the product brief workflow.
 Remember: Do NOT proceed to step-06 until user explicitly selects 'C' from the A/P/C menu and content is saved!
--- a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-06-complete.md
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-06-complete.md
@ -1,47 +1,67 @@
 ---
 name: 'step-06-complete'
 description: 'Complete the product brief workflow, update status files, and suggest next steps for the project'
 # Path Definitions
 workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief'
 # File References
 thisStepFile: '{workflow_path}/steps/step-06-complete.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.md'
 # Task References
 # (No task references used in this completion step)
 ---
 # Step 6: Product Brief Completion
 ## STEP GOAL:
 Complete the product brief workflow, update status files, and provide guidance on logical next steps for continued product development.
 ## MANDATORY EXECUTION RULES (READ FIRST):
- ✅ THIS IS A FINAL STEP - Product brief completion required
+### Universal Rules:
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🛑 NEVER generate content without user input
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- 📖 CRITICAL: Read the complete step file before taking any action
- 🛑 NO content generation - this is a wrap-up step
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
- 📋 FINALIZE document and update workflow status
+- 📋 YOU ARE A FACILITATOR, not a content generator
- 💬 FOCUS on completion, next steps, and suggestions
+
- 🎯 UPDATE workflow status files with completion information
+### Role Reinforcement:
 - ✅ You are a product-focused Business Analyst facilitator
 - ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
 - ✅ We engage in collaborative dialogue, not command-response
 - ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
 - ✅ Maintain collaborative completion tone throughout
 ### Step-Specific Rules:
 - 🎯 Focus only on completion, next steps, and project guidance
 - 🚫 FORBIDDEN to generate new content for the product brief
 - 💬 Approach: Systematic completion with quality validation and next step recommendations
 - 📋 FINALIZE document and update workflow status appropriately
 ## EXECUTION PROTOCOLS:
 - 🎯 Show your analysis before taking any action
 - 💾 Update the main workflow status file with completion information
 - 📖 Suggest potential next workflow steps for the user
- 🚫 DO NOT load additional steps after this one
+- 🚫 DO NOT load additional steps after this one (this is final)
 ## TERMINATION STEP PROTOCOLS:
 - This is a FINAL step - workflow completion required
 - Output any remaining content if needed (none for this step)
 - Update the main workflow status file with finalized document
 - Suggest potential next steps for the user
 - Mark workflow as complete in status tracking
 ## CONTEXT BOUNDARIES:
- Complete product brief document is available from all previous steps
+- Available context: Complete product brief document from all previous steps, workflow frontmatter shows all completed steps
- Workflow frontmatter shows all completed steps
+- Focus: Completion validation, status updates, and next step guidance
- All collaborative content has been generated and saved
+- Limits: No new content generation, only completion and wrap-up activities
- Focus on completion, validation, and next steps
+- Dependencies: All previous steps must be completed with content saved to document
-## YOUR TASK:
+## Sequence of Instructions (Do not deviate, skip, or optimize)
 Complete the product brief workflow, update status files, and suggest next steps for the project.
 ## WORKFLOW COMPLETION SEQUENCE:
 ### 1. Announce Workflow Completion
-Inform user that the product brief is complete:
+**Completion Announcement:**
 "🎉 **Product Brief Complete, {{user_name}}!**
 I've successfully collaborated with you to create a comprehensive Product Brief for {{project_name}}.
@ -55,33 +75,33 @@ I've successfully collaborated with you to create a comprehensive Product Brief
 - ✅ MVP Scope with focused feature set and clear boundaries
 - ✅ Future Vision that inspires while maintaining current focus
-**The complete Product Brief is now available at:** `{default_output_file}`
+**The complete Product Brief is now available at:** `{outputFile}`
 This brief serves as the foundation for all subsequent product development activities and strategic decisions."
 ### 2. Workflow Status Update
 **Status File Management:**
 Update the main workflow status file:
 - Check if `{output_folder}/bmm-workflow-status.yaml` exists
 - If not, create it with basic structure
- Update workflow_status["product-brief"] = `{default_output_file}`
+- Update workflow_status["product-brief"] = `{outputFile}`
 - Add completion timestamp and metadata
 - Save file, preserving all comments and structure
 ### 3. Document Quality Check
 **Completeness Validation:**
 Perform final validation of the product brief:
 **Completeness Check:**
 - Does the executive summary clearly communicate the vision and problem?
 - Are target users well-defined with compelling personas?
 - Do success metrics connect user value to business objectives?
 - Is MVP scope focused and realistic?
 - Does the brief provide clear direction for next steps?
-**Consistency Check:**
+**Consistency Validation:**
 - Do all sections align with the core problem statement?
 - Is user value consistently emphasized throughout?
@ -90,9 +110,8 @@ Perform final validation of the product brief:
 ### 4. Suggest Next Steps
 Provide guidance on logical next workflows:
 **Recommended Next Workflow:**
 Provide guidance on logical next workflows:
 1. `workflow prd` - Create detailed Product Requirements Document
   - Brief provides foundation for detailed requirements
@ -109,9 +128,9 @@ Provide guidance on logical next workflows:
 - Use brief to validate concept before committing to detailed work
 - Brief can guide early technical feasibility discussions
-### 5. Final Completion Confirmation
+### 5. Present MENU OPTIONS
-Confirm completion with user:
+**Completion Confirmation:**
 "**Your Product Brief for {{project_name}} is now complete and ready for the next phase!**
 The brief captures everything needed to guide subsequent product development:
@ -122,79 +141,59 @@ The brief captures everything needed to guide subsequent product development:
 - Focused MVP scope with realistic boundaries
 - Inspiring long-term vision
-**Ready to continue with:**
+**Suggested Next Steps**
 - PRD workflow for detailed requirements?
 - UX design workflow for user experience planning?
 - Architecture workflow for technical design?
-**Or would you like to review the complete brief first?**
+**Product Brief Complete**"
-[Product Brief Complete]"
+#### Menu Handling Logic:
-## SUCCESS METRICS:
+- Since this is a completion step, no continuation to other workflow steps
 - User can ask questions or request review of the completed brief
 - Provide guidance on next workflow options when requested
 - End workflow session gracefully after completion confirmation
-✅ Product brief contains all essential sections
+#### EXECUTION RULES:
 ✅ All collaborative content properly saved to document
 ✅ Workflow status file updated with completion information
 ✅ Clear next step guidance provided to user
 ✅ Document quality validation completed
 ✅ User acknowledges completion and understands next options
-## FAILURE MODES:
+- This is a final step with completion focus
 - No additional workflow steps to load after this
 - User can request review or clarification of completed brief
 - Provide clear guidance on next workflow options
-❌ Not updating workflow status file with completion information
+## CRITICAL STEP COMPLETION NOTE
 ❌ Missing clear next step guidance for user
 ❌ Not confirming document completeness with user
 ❌ Workflow not properly marked as complete in status tracking
 ❌ User unclear about what happens next
-❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+ONLY WHEN [completion confirmation is provided and workflow status updated], will you then mark the workflow as complete and end the session gracefully. No additional steps are loaded after this final completion step.
 ❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
 ❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
-## PRODUCT BRIEF COMPLETION CHECKLIST:
+---
-### Document Structure Complete:
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
- [ ] Executive Summary with vision and problem statement
+### ✅ SUCCESS:
 - [ ] Core Vision with solution definition and differentiators
 - [ ] Target Users with personas and user journeys
 - [ ] Success Metrics with business objectives and KPIs
 - [ ] MVP Scope with core features and boundaries
 - [ ] Future Vision for long-term direction
-### Process Complete:
+- Product brief contains all essential sections with collaborative content
 - All collaborative content properly saved to document with proper frontmatter
 - Workflow status file updated with completion information and timestamp
 - Clear next step guidance provided to user with specific workflow recommendations
 - Document quality validation completed with completeness and consistency checks
 - User acknowledges completion and understands next available options
 - Workflow properly marked as complete in status tracking
- [ ] All steps completed with user confirmation
+### ❌ SYSTEM FAILURE:
 - [ ] All content saved to document
 - [ ] Frontmatter properly updated
 - [ ] Workflow status file updated
 - [ ] Next steps clearly communicated
-## NEXT STEPS GUIDANCE:
+- Not updating workflow status file with completion information
 - Missing clear next step guidance for user
 - Not confirming document completeness with user
 - Workflow not properly marked as complete in status tracking
 - User unclear about what happens next or available options
 - Document quality issues not identified or addressed
-**Immediate Options:**
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
-1. **PRD Workflow** - Transform brief into detailed requirements
+## FINAL WORKFLOW COMPLETION
 2. **UX Design** - User experience research and design planning
 3. **Architecture** - Technical system design and technology choices
 4. **Review** - Validate brief with stakeholders before proceeding
 **Recommended Sequence:**
 Product Brief → PRD → (UX if needed) + Architecture → Development
 ## WORKFLOW FINALIZATION:
 - Set `lastStep = 6` in document frontmatter
 - Update workflow status file with completion timestamp
 - Provide completion summary to user
 - Do NOT load any additional steps
 ## FINAL REMINDER:
 This product brief is now complete and serves as the strategic foundation for the entire product lifecycle. All subsequent design, architecture, and development work should trace back to the vision, user needs, and success criteria documented in this brief.
 **Congratulations on completing the Product Brief for {{project_name}}!** 🎉
 **Ready to transform this vision into detailed plans with the PRD workflow?**
--- a/src/modules/bmm/workflows/1-analysis/product-brief/workflow.md
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/workflow.md
@ -1,47 +1,58 @@
 ---
 name: Product Brief Workflow
 description: Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.
 web_bundle: true
 ---
 # Product Brief Workflow
 **Goal:** Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.
-**Your Role:** You are a product-focused Business Analyst facilitator collaborating with an expert peer. This is a partnership, not a client-vendor relationship. You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision. Work together as equals.
+**Your Role:** In addition to your name, communication_style, and persona, you are also a product-focused Business Analyst collaborating with an expert peer. This is a partnership, not a client-vendor relationship. You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision. Work together as equals.
 ---
 ## WORKFLOW ARCHITECTURE
-This uses **micro-file architecture** for disciplined execution:
+This uses **step-file architecture** for disciplined execution:
- Each step is a self-contained file with embedded rules
+### Core Principles
- Sequential progression with user control at each step
+
- Document state tracked in frontmatter
+- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
- Append-only document building through conversation
+- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
 - **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
 - **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
 - **Append-Only Building**: Build documents by appending content as directed to the output file
 ### Step Processing Rules
 1. **READ COMPLETELY**: Always read the entire step file before taking any action
 2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
 3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
 4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
 5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
 6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
 ### Critical Rules (NO EXCEPTIONS)
 - 🛑 **NEVER** load multiple step files simultaneously
 - 📖 **ALWAYS** read entire step file before execution
 - 🚫 **NEVER** skip steps or optimize the sequence
 - 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
 - 🎯 **ALWAYS** follow the exact instructions in the step file
 - ⏸️ **ALWAYS** halt at menus and wait for user input
 - 📋 **NEVER** create mental todo lists from future steps
 ---
-## INITIALIZATION
+## INITIALIZATION SEQUENCE
-### Configuration Loading
+### 1. Configuration Loading
-Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve:
+Load and read full config from {project-root}/{bmad_folder}/bmm/config.yaml and resolve:
- `project_name`, `output_folder`, `user_name`
+- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `user_skill_level`
 - `communication_language`, `document_output_language`, `user_skill_level`
 - `date` as system-generated current datetime
-### Paths
+### 2. First Step EXECUTION
- `installed_path` = `{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief`
+Load, read the full file and then execute `{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief/steps/step-01-init.md` to begin the workflow.
 - `template_path` = `{installed_path}/product-brief.template.md`
 - `default_output_file` = `{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.md`
 ---
 ## EXECUTION
 Load and execute `steps/step-01-init.md` to begin the workflow.
 **Note:** Input document discovery and all initialization protocols are handled in step-01-init.md.