diff --git a/src/modules/bmm/agents/analyst.agent.yaml b/src/modules/bmm/agents/analyst.agent.yaml
index acdc0a17..27ce9233 100644
--- a/src/modules/bmm/agents/analyst.agent.yaml
+++ b/src/modules/bmm/agents/analyst.agent.yaml
@@ -23,15 +23,15 @@ agent:
description: Get workflow status or initialize a workflow if not already done (optional)
- trigger: brainstorm-project
- workflow: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml"
+ exec: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/brainstorm-project/workflow.md"
description: Guided Brainstorming session with final report (optional)
- trigger: research
- workflow: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/research/workflow.yaml"
- description: Guided Research scoped to market and competitive analysis (optional)
+ exec: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/research/workflow.md"
+ description: Guided Research scoped to market, domain, competitive analysis, or technical research (optional)
- trigger: product-brief
- workflow: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief/workflow.yaml"
+ exec: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief/workflow.md"
description: Create a Product Brief (recommended input for PRD)
- trigger: document-project
diff --git a/src/modules/bmm/workflows/1-analysis/brainstorm-project/brainstorming-focus.md b/src/modules/bmm/workflows/1-analysis/brainstorm-project/brainstorming-focus.md
index 4229385b..39573cc7 100644
--- a/src/modules/bmm/workflows/1-analysis/brainstorm-project/brainstorming-focus.md
+++ b/src/modules/bmm/workflows/1-analysis/brainstorm-project/brainstorming-focus.md
@@ -23,3 +23,49 @@ Brainstorming sessions typically feed into:
- **PRDs** - Detailed requirements documents
- **Technical Specifications** - Architecture and implementation plans
- **Research Activities** - Areas requiring further investigation
+
+## Brainstorming Techniques for Projects
+
+### Problem-Solution Mapping
+
+- Identify core user problems
+- Brainstorm multiple solution approaches
+- Evaluate feasibility and impact
+
+### Feature Ideation
+
+- Must-have vs nice-to-have features
+- User journey mapping
+- Competitive differentiation opportunities
+
+### Technical Architecture Thinking
+
+- High-level system design considerations
+- Technology stack possibilities
+- Integration challenges and opportunities
+
+### Business Model Canvas
+
+- Value proposition identification
+- Customer segments and channels
+- Revenue streams and cost structures
+
+## Output Structure Guidance
+
+Brainstorming results should capture:
+
+1. **Problem Statements** - Clearly defined user challenges
+2. **Solution Concepts** - High-level approach descriptions
+3. **Feature Priorities** - Categorized by importance and feasibility
+4. **Technical Considerations** - Architecture and implementation thoughts
+5. **Next Steps** - Actions needed to advance concepts
+6. **Integration Points** - Connections to downstream workflows
+
+## Session Facilitation Notes
+
+This context will be passed to the core CIS brainstorming workflow to:
+
+- Provide project-specific framing for ideation techniques
+- Ensure results align with BMAD workflow expectations
+- Maintain focus on software/product development considerations
+- Facilitate smooth integration with subsequent workflows
diff --git a/src/modules/bmm/workflows/1-analysis/brainstorm-project/instructions.md b/src/modules/bmm/workflows/1-analysis/brainstorm-project/instructions.md
deleted file mode 100644
index 726bfa4d..00000000
--- a/src/modules/bmm/workflows/1-analysis/brainstorm-project/instructions.md
+++ /dev/null
@@ -1,112 +0,0 @@
-# Brainstorm Project - Workflow Instructions
-
-```xml
-The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml
-You MUST have already loaded and processed: {installed_path}/workflow.yaml
-Communicate all responses in {communication_language}
-This is a meta-workflow that orchestrates the CIS brainstorming workflow with project-specific context
-⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.
-⚠️ CHECKPOINT PROTOCOL: After EVERY tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.
-
-
-
-
- Check if {output_folder}/bmm-workflow-status.yaml exists
-
-
-
- Set standalone_mode = true
-
-
-
- Load the FULL file: {output_folder}/bmm-workflow-status.yaml
- Parse workflow_status section
- Check status of "brainstorm-project" workflow
- Get project_level from YAML metadata
- Find first non-completed workflow (next expected workflow)
-
-
-
- Re-running will create a new session. Continue? (y/n)
-
-
- Exit workflow
-
-
-
-
-
- Continue with brainstorming anyway? (y/n)
-
-
- Exit workflow
-
-
-
- Set standalone_mode = false
-
-
-
-
- Read the project context document from: {project_context}
- This context provides project-specific guidance including:
- - Focus areas for project ideation
- - Key considerations for software/product projects
- - Recommended techniques for project brainstorming
- - Output structure guidance
-
-
-
-
- Execute the CIS brainstorming workflow with project context
-
- The CIS brainstorming workflow will:
- - Present interactive brainstorming techniques menu
- - Guide the user through selected ideation methods
- - Generate and capture brainstorming session results
- - Save output to: {output_folder}/brainstorming-session-results-{{date}}.md
-
-
-
-
-
- Load the FULL file: {output_folder}/bmm-workflow-status.yaml
- Find workflow_status key "brainstorm-project"
- ONLY write the file path as the status value - no other text, notes, or metadata
- Update workflow_status["brainstorm-project"] = "{output_folder}/bmm-brainstorming-session-{{date}}.md"
- Save file, preserving ALL comments and structure including STATUS DEFINITIONS
-
- Find first non-completed workflow in workflow_status (next workflow to do)
- Determine next agent from path file based on next workflow
-
-
-
-
-
-
-```
diff --git a/src/modules/bmm/workflows/1-analysis/brainstorm-project/steps/step-01-project-brainstorming.md b/src/modules/bmm/workflows/1-analysis/brainstorm-project/steps/step-01-project-brainstorming.md
new file mode 100644
index 00000000..bdd22486
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/brainstorm-project/steps/step-01-project-brainstorming.md
@@ -0,0 +1,194 @@
+# Project Brainstorming Step 1: Orchestrated Brainstorming Session
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🎯 This is a meta-workflow that orchestrates the core brainstorming workflow
+- 📋 YOU ARE A BRAINSTORMING FACILITATOR, Guiding the user to get the best ideas out of them through facilitated suggestion
+- 💬 FOCUS on project-specific context and workflow integration
+- 🔗 CRITICAL: Must pass context to core brainstorming workflow correctly
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Validate workflow status and execution context before proceeding
+- 📖 Load project context from brainstorming-focus.md
+- 🔗 Invoke core brainstorming workflow with project context
+- 💾 Save results to specified output location
+- 📊 Update workflow status in integrated mode
+
+## CONTEXT BOUNDARIES:
+
+- Project context from brainstorming-focus.md is available
+- Core brainstorming workflow path: `{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml`
+- Output location: `{output_folder}/analysis/brainstorming/project-{{topic}}-brainstorming-{{date}}.md`
+- Status file: `{output_folder}/bmm-workflow-status.yaml` (if in integrated mode)
+
+## YOUR TASK:
+
+Orchestrate a project brainstorming session using the core brainstorming workflow with project-specific context.
+
+## PROJECT BRAINSTORMING SEQUENCE:
+
+### 1. Workflow Status Validation
+
+Begin with status validation approach:
+"Now I'll set up your **project brainstorming session** by validating the workflow context and preparing the core brainstorming workflow.
+
+**Status Validation Focus:**
+
+- Check for existing workflow status file
+- Validate execution mode (standalone vs integrated)
+- Ensure brainstorming is appropriate next step in sequence
+- Prepare workflow integration context
+
+**Let me check the current workflow status.**"
+
+#### Status File Check
+
+- Check if `{output_folder}/bmm-workflow-status.yaml` exists
+- If no status file: Set standalone_mode = true
+- If status file exists: Load and validate workflow sequence
+- Check if brainstorm-project is next expected workflow
+- Validate project_level from metadata
+
+### 2. Project Context Loading
+
+Load project-specific brainstorming guidance:
+"**Loading Project Brainstorming Context...**
+
+**Project Focus Areas for Today's Session:**
+
+- User Problems and Pain Points identification
+- Feature Ideas and Capabilities exploration
+- Technical Approaches and feasibility consideration
+- User Experience design thinking
+- Business Model and Value creation strategies
+- Market Differentiation opportunities
+- Technical Risks and Challenges assessment
+- Success Metrics definition
+
+**Integration Pathways:**
+This brainstorming session will feed into:
+
+- Product Briefs for initial product vision
+- PRDs for detailed requirements
+- Technical Specifications for architecture plans
+- Research Activities for validation needs"
+
+### 3. Core Brainstorming Workflow Orchestration
+
+Invoke the core brainstorming workflow with project context:
+
+**Orchestration Approach:**
+"I'll now orchestrate the **core brainstorming workflow** with your project-specific context.
+
+**What to Expect:**
+
+- Interactive brainstorming techniques menu tailored for projects
+- Project-focused ideation methods and guidance
+- Structured capture of all generated ideas and insights
+- Results saved to your project's brainstorming folder
+
+**The core workflow will provide:**
+
+- Multiple brainstorming technique options
+- Guided ideation sessions based on your selections
+- Real-time capture and organization of ideas
+- Project-specific prompting and context awareness
+
+**Let me launch the core brainstorming workflow with your project context...**"
+
+#### Workflow Invocation
+
+- Execute: `{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml`
+- Pass: `brainstorming-focus.md` context as input data
+- Ensure: Output saves to `{output_folder}/analysis/brainstorming/project-{{topic}}-brainstorming-{{date}}.md`
+- Monitor: Session progress and results generation
+
+### 4. Session Completion and Status Update
+
+Complete the orchestrated session:
+
+**Completion Process:**
+"**✅ Project Brainstorming Session Complete!**
+
+**Session Results:**
+
+- Brainstorming session successfully orchestrated
+- Core workflow executed with project context
+- Results captured in: `{output_folder}/analysis/brainstorming/project-{{topic}}-brainstorming-{{date}}.md`
+- All ideas and insights organized for downstream workflows
+
+{{#if standalone_mode != true}}
+**Workflow Status Updated:**
+
+- Progress tracking updated in BMAD workflow system
+- Ready for next workflow in sequence
+
+**Next Steps:**
+
+- **Next required:** [Will determine from workflow status]
+- **Recommended:** Review results before proceeding to next workflow
+- **Optional:** Run additional analysis workflows (research, product-brief)
+
+{{else}}
+**Next Steps:**
+Since no workflow sequence is active:
+
+- Review brainstorming results and identify key concepts
+- Consider running `workflow-init` to create a guided workflow path
+- Refer to BMAD workflow guide for next steps
+ {{/if}}
+
+**Integration Opportunities:**
+Your brainstorming results are ready to feed into:
+
+- **Product Brief** workflow for initial product vision
+- **PRD** workflow for detailed requirements
+- **Research** workflows for market/technical validation
+- **Architecture** workflows for technical design"
+
+#### Status Update (Integrated Mode Only)
+
+- Load: `{output_folder}/bmm-workflow-status.yaml`
+- Update: `workflow_status["brainstorm-project"] = "{output_folder}/analysis/brainstorming/project-{{topic}}-brainstorming-{{date}}.md"`
+- Preserve: ALL comments and structure in status file
+- Determine: Next workflow and agent for progression
+
+## SUCCESS METRICS:
+
+✅ Workflow status validated and execution context confirmed
+✅ Project context loaded and prepared for core workflow
+✅ Core brainstorming workflow successfully orchestrated
+✅ Project-specific context passed correctly to core workflow
+✅ Session results captured in specified output location
+✅ Workflow status updated (in integrated mode)
+✅ Integration guidance provided for next steps
+
+## FAILURE MODES:
+
+❌ Not validating workflow status before execution
+❌ Failing to pass project context to core workflow
+❌ Core brainstorming workflow execution failure
+❌ Results not saved to correct output location
+❌ Status not updated in integrated mode
+❌ Not providing integration guidance for next steps
+
+## CRITICAL WORKFLOW INTEGRATION:
+
+- **Context Passing**: Must pass brainstorming-focus.md intact to core workflow
+- **Output Management**: Ensure core workflow saves to correct location
+- **Status Consistency**: Update workflow status file only in integrated mode
+- **Path Recording**: Record only file paths as status values (no extra text)
+
+## NEXT STEPS:
+
+After completion, users can:
+
+- Review brainstorming session results
+- Brainstorm something else
+- Proceed with recommended next workflow (integrated mode)
+- Run product-brief or PRD workflows to develop concepts further
+- Conduct research workflows to validate brainstormed ideas
+- Begin architecture workflows for technical design concepts
+
+This meta-workflow successfully bridges project-specific brainstorming needs with the powerful core brainstorming workflow while maintaining seamless integration with the broader BMAD methodology.
diff --git a/src/modules/bmm/workflows/1-analysis/brainstorm-project/workflow.md b/src/modules/bmm/workflows/1-analysis/brainstorm-project/workflow.md
new file mode 100644
index 00000000..2b41c992
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/brainstorm-project/workflow.md
@@ -0,0 +1,191 @@
+---
+name: Brainstorm Project Workflow
+description: Facilitate project brainstorming sessions by orchestrating the CIS brainstorming workflow with project-specific context and guidance.
+---
+
+# Brainstorm Project Workflow
+
+**Goal:** Facilitate project brainstorming sessions by orchestrating the CIS brainstorming workflow with project-specific context and guidance.
+
+**Your Role:** You are a brainstorming facilitator who guides project ideation sessions using structured techniques while ensuring the results integrate seamlessly with the broader BMAD project workflow.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **meta-workflow orchestration** with **step-based execution**:
+
+- Orchestrates the core CIS brainstorming workflow with project context
+- Step-based progression through project-specific preparation
+- Integrates results with the broader BMAD workflow system
+- Handles workflow status tracking and progression
+
+---
+
+## INITIALIZATION
+
+### Configuration Loading
+
+Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve:
+
+- `project_name`, `output_folder`, `user_name`
+- `communication_language`, `document_output_language`, `user_skill_level`
+- `date`, `current_year`, `current_month` as system-generated values
+
+### Paths
+
+- `installed_path` = `{project-root}/{bmad_folder}/bmm/workflows/1-analysis/brainstorm-project`
+- `context_path` = `{installed_path}/brainstorming-focus.md`
+- `core_brainstorming` = `{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml`
+- `output_file` = `{output_folder}/analysis/brainstorming/project-{{topic}}-brainstorming-{{date}}.md`
+
+### Workflow Status Integration
+
+- `status_file` = `{output_folder}/bmm-workflow-status.yaml`
+- Tracks progress within the broader BMAD workflow system
+- Handles both standalone and integrated execution modes
+
+---
+
+## EXECUTION
+
+Execute project brainstorming with workflow orchestration:
+
+### Step 1: Workflow Status Validation
+
+**Goal:** Validate workflow readiness and execution context
+
+**Status Check Process:**
+
+1. **Status File Detection**: Check if `{status_file}` exists
+2. **Standalone Mode**: If no status file, proceed in standalone mode
+3. **Integrated Mode**: If status file found, validate workflow sequence
+4. **Completion Check**: Verify if brainstorming already completed
+5. **Sequence Validation**: Ensure brainstorming is appropriate next step
+
+**Integrated Mode Logic:**
+
+- Load full status file and parse workflow_status section
+- Check status of "brainstorm-project" workflow
+- Validate project_level from YAML metadata
+- Determine next expected workflow in sequence
+
+### Step 2: Project Context Loading
+
+**Goal:** Load project-specific brainstorming guidance
+
+**Context Areas:**
+
+- User Problems and Pain Points identification
+- Feature Ideas and Capabilities exploration
+- Technical Approaches consideration
+- User Experience design thinking
+- Business Model and Value creation
+- Market Differentiation strategies
+- Technical Risks and Challenges assessment
+- Success Metrics definition
+
+**Integration Pathways:**
+
+- Product Briefs - Initial product vision and strategy
+- PRDs - Detailed requirements documents
+- Technical Specifications - Architecture and implementation plans
+- Research Activities - Areas requiring further investigation
+
+### Step 3: Core Brainstorming Orchestration
+
+**Goal:** Execute CIS brainstorming workflow with project context
+
+**Orchestration Process:**
+
+1. **Context Passing**: Transfer project context to core workflow
+2. **Workflow Invocation**: Execute `{core_brainstorming}` with enriched context
+3. **Session Guidance**: Provide project-specific framing for brainstorming techniques
+4. **Result Capture**: Ensure output saves to specified location
+
+**Core Workflow Integration:**
+
+- Present interactive brainstorming techniques menu
+- Guide user through selected ideation methods
+- Generate and capture brainstorming session results
+- Save output to: `{output_folder}/brainstorming/brainstorming-session-{{date}}.md`
+
+### Step 4: Status Update and Completion
+
+**Goal:** Update workflow status and provide completion guidance
+
+**Status Update Process:**
+
+1. **Integrated Mode**: Update workflow status file with completion path
+2. **Path Recording**: Save brainstorming session file path as status value
+3. **Next Workflow**: Determine next required workflow in sequence
+4. **Agent Identification**: Identify next agent for workflow progression
+
+**Completion Output:**
+
+- Session results location and summary
+- Status update confirmation (integrated mode)
+- Next workflow steps and agent guidance
+- Optional workflow recommendations
+
+---
+
+## OUTPUT STRUCTURE
+
+### Brainstorming Session Output
+
+```
+{output_folder}/analysis/brainstorming/project-{{topic}}-brainstorming-{{date}}.md
+```
+
+Contains:
+
+- Brainstorming session techniques used
+- Generated ideas and concepts
+- Project-specific insights and recommendations
+- Integration guidance for downstream workflows
+
+### Status Integration
+
+Updates `{output_folder}/bmm-workflow-status.yaml`:
+
+```yaml
+workflow_status:
+ brainstorm-project: '{output_folder}/analysis/brainstorming/project-{{topic}}-brainstorming-{{date}}.md'
+ # Next workflow will be automatically determined
+```
+
+---
+
+## WORKFLOW INTEGRATION CRITICAL POINTS
+
+### Context Preservation
+
+- Project context must be passed intact to core brainstorming workflow
+- Maintain project focus areas throughout session
+- Ensure integration pathways are considered during ideation
+
+### Status Consistency
+
+- Only update status file in integrated mode
+- Preserve ALL comments and structure in status file
+- Record only file paths as status values (no additional text)
+
+### Output Location Management
+
+- Brainstorming results go to dedicated `/brainstorming` subfolder
+- Maintain consistent naming convention with date stamps
+- Ensure accessibility for downstream workflows
+
+---
+
+## NEXT WORKFLOW INTEGRATION
+
+After brainstorming completion, typical progression:
+
+1. **Product Brief** - Transform ideas into structured product vision
+2. **PRD** - Develop detailed requirements from brainstormed concepts
+3. **Research** - Investigate ideas requiring market/technical validation
+4. **Architecture** - Design technical approaches for selected concepts
+
+The brainstorming session results provide the foundational ideation input for these subsequent workflows.
diff --git a/src/modules/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml b/src/modules/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml
deleted file mode 100644
index 84efaf10..00000000
--- a/src/modules/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml
+++ /dev/null
@@ -1,39 +0,0 @@
-# Brainstorm Project Workflow Configuration
-name: "brainstorm-project"
-description: "Facilitate project brainstorming sessions by orchestrating the CIS brainstorming workflow with project-specific context and guidance."
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-document_output_language: "{config_source}:document_output_language"
-user_skill_level: "{config_source}:user_skill_level"
-date: system-generated
-
-# Module path and component files
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/brainstorm-project"
-template: false
-instructions: "{installed_path}/instructions.md"
-
-# Context document for project brainstorming
-project_context: "{installed_path}/brainstorming-focus.md"
-
-# CORE brainstorming workflow to invoke
-core_brainstorming: "{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml"
-
-standalone: true
-
-web_bundle:
- name: "brainstorm-project"
- description: "Facilitate project brainstorming sessions by orchestrating the CIS brainstorming workflow with project-specific context and guidance."
- author: "BMad"
- instructions: "{bmad_folder}/bmm/workflows/1-analysis/brainstorm-project/instructions.md"
- template: false
- web_bundle_files:
- - "{bmad_folder}/bmm/workflows/1-analysis/brainstorm-project/instructions.md"
- - "{bmad_folder}/bmm/workflows/1-analysis/brainstorm-project/brainstorming-focus.md"
- - "{bmad_folder}/core/workflows/brainstorming/workflow.yaml"
- existing_workflows:
- - core_brainstorming: "{bmad_folder}/core/workflows/brainstorming/workflow.yaml"
diff --git a/src/modules/bmm/workflows/1-analysis/domain-research/instructions.md b/src/modules/bmm/workflows/1-analysis/domain-research/instructions.md
deleted file mode 100644
index 35ce2614..00000000
--- a/src/modules/bmm/workflows/1-analysis/domain-research/instructions.md
+++ /dev/null
@@ -1,425 +0,0 @@
-# Domain Research - Collaborative Domain Exploration
-
-The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml
-You MUST have already loaded and processed: {installed_path}/workflow.yaml
-This is COLLABORATIVE RESEARCH - engage the user as a partner, not just a data source
-The goal is PRACTICAL UNDERSTANDING that directly informs requirements and architecture
-Communicate all responses in {communication_language} and adapt deeply to {user_skill_level}
-Generate all documents in {document_output_language}
-LIVING DOCUMENT: Write to domain-brief.md continuously as you discover - never wait until the end
-⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.
-⚠️ CHECKPOINT PROTOCOL: After EVERY tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.
-
-
-
-
-Welcome {user_name} to collaborative domain research
-
-Check for context:
-
-- Was this triggered from PRD workflow?
-- Is there a workflow-status.yaml with project context?
-- Did user provide initial domain/project description?
-
-If context exists, reflect it back:
-"I understand you're building [description]. Let's explore the [domain] aspects together to ensure we capture all critical requirements."
-
-If no context:
-"Let's explore your project's domain together. Tell me about what you're building and what makes it unique or complex."
-
-
-
-Through conversation, identify the domain and its complexity
-
-Listen for domain signals and explore:
-
-- "Is this in a regulated industry?"
-- "Are there safety or compliance concerns?"
-- "What could go wrong if this fails?"
-- "Who are the stakeholders beyond direct users?"
-- "Are there industry standards we need to follow?"
-
-Based on responses, identify primary domain(s):
-
-- Healthcare/Medical
-- Financial Services
-- Government/Public Sector
-- Education
-- Aerospace/Defense
-- Automotive
-- Energy/Utilities
-- Legal
-- Insurance
-- Scientific/Research
-- Other specialized domain
-
-Share your understanding:
-"Based on our discussion, this appears to be a [domain] project with [key characteristics]. The main areas we should research are:
-
-- [Area 1]
-- [Area 2]
-- [Area 3]
-
-What concerns you most about building in this space?"
-
-domain_overview
-
-
-
-Work WITH the user to identify critical concerns
-
-"Let's map out the important considerations together. I'll share what I typically see in [domain], and you tell me what applies to your case."
-
-For detected domain, explore relevant areas:
-
-HEALTHCARE:
-"In healthcare software, teams often worry about:
-
-- FDA approval pathways (510k, De Novo, PMA)
-- HIPAA compliance for patient data
-- Clinical validation requirements
-- Integration with hospital systems (HL7, FHIR, DICOM)
-- Patient safety and liability
-
-Which of these apply to you? What else concerns you?"
-
-FINTECH:
-"Financial software typically deals with:
-
-- KYC/AML requirements
-- Payment processing regulations (PCI DSS)
-- Regional compliance (US, EU, specific countries?)
-- Fraud prevention
-- Audit trails and reporting
-
-What's your situation with these? Any specific regions?"
-
-AEROSPACE:
-"Aerospace software often requires:
-
-- DO-178C certification levels
-- Safety analysis (FMEA, FTA)
-- Simulation validation
-- Real-time performance guarantees
-- Export control (ITAR)
-
-Which are relevant for your project?"
-
-[Continue for other domains...]
-
-Document concerns as the user shares them
-Ask follow-up questions to understand depth:
-
-- "How critical is this requirement?"
-- "Is this a must-have for launch or can it come later?"
-- "Do you have expertise here or need guidance?"
-
-concern_mapping
-
-
-
-Conduct research WITH the user watching and contributing
-
-"Let me research the current requirements for [specific concern]. You can guide me toward what's most relevant."
-
-{specific_requirement} requirements {date}
-
-Share findings immediately:
-"Here's what I found about [requirement]:
-
-- [Key point 1]
-- [Key point 2]
-- [Key point 3]
-
-Does this match your understanding? Anything surprising or concerning?"
-
-For each major concern:
-
-1. Research current standards/regulations
-2. Share findings with user
-3. Get their interpretation
-4. Note practical implications
-
-If user has expertise:
-"You seem knowledgeable about [area]. What should I know that might not be in public documentation?"
-
-If user is learning:
-"This might be new territory. Let me explain what this means practically for your development..."
-
-regulatory_requirements
-industry_standards
-
-
-
-Translate research into practical development impacts
-
-"Based on what we've learned, here's what this means for your project:
-
-ARCHITECTURE IMPLICATIONS:
-
-- [How this affects system design]
-- [Required components or patterns]
-- [Performance or security needs]
-
-DEVELOPMENT IMPLICATIONS:
-
-- [Additional development effort]
-- [Special expertise needed]
-- [Testing requirements]
-
-TIMELINE IMPLICATIONS:
-
-- [Certification/approval timelines]
-- [Validation requirements]
-- [Documentation needs]
-
-COST IMPLICATIONS:
-
-- [Compliance costs]
-- [Required tools or services]
-- [Ongoing maintenance]
-
-Does this align with your expectations? Any surprises we should dig into?"
-
-practical_implications
-
-
-
-Explore how others solve similar problems
-
-"Let's look at how successful [domain] products handle these challenges."
-
-best {domain} software architecture patterns {date}
-{domain} software case studies {date}
-
-Discuss patterns:
-"I found these common approaches in [domain]:
-
-Pattern 1: [Description]
-
-- Pros: [Benefits]
-- Cons: [Tradeoffs]
-- When to use: [Conditions]
-
-Pattern 2: [Description]
-
-- Pros: [Benefits]
-- Cons: [Tradeoffs]
-- When to use: [Conditions]
-
-Which resonates with your vision? Or are you thinking something different?"
-
-If user proposes novel approach:
-"That's interesting and different from the standard patterns. Let's explore:
-
-- What makes your approach unique?
-- What problem does it solve that existing patterns don't?
-- What are the risks?
-- How do we validate it?"
-
-domain_patterns
-innovation_notes
-
-
-
-Collaboratively identify and address risks
-
-"Every [domain] project has risks. Let's think through yours:
-
-REGULATORY RISKS:
-
-- What if regulations change during development?
-- What if approval/certification takes longer?
-- What if we misinterpret requirements?
-
-TECHNICAL RISKS:
-
-- What if the domain requirements conflict with user experience?
-- What if performance requirements are harder than expected?
-- What if integrations are more complex?
-
-MARKET RISKS:
-
-- What if competitors move faster?
-- What if domain experts are hard to find?
-- What if users resist domain-mandated workflows?
-
-For each risk you're concerned about, let's identify:
-
-1. How likely is it?
-2. What's the impact if it happens?
-3. How can we mitigate it?
-4. What's our plan B?"
-
-risk_assessment
-
-
-
-Plan how to ensure domain requirements are met
-
-"Let's plan how to validate that we're meeting [domain] requirements:
-
-COMPLIANCE VALIDATION:
-
-- How do we verify regulatory compliance?
-- Who needs to review/approve?
-- What documentation is required?
-
-TECHNICAL VALIDATION:
-
-- How do we prove the system works correctly?
-- What metrics matter?
-- What testing is required?
-
-DOMAIN EXPERT VALIDATION:
-
-- Who are the domain experts to involve?
-- When should they review?
-- What are their success criteria?
-
-USER VALIDATION:
-
-- How do we ensure it's still usable despite constraints?
-- What user testing is needed?
-- How do we balance domain requirements with UX?
-
-What validation is most critical for your confidence?"
-
-validation_strategy
-
-
-
-Capture key decisions and rationale
-
-"Let's document the important decisions we've made:
-
-DOMAIN APPROACH:
-
-- We're choosing [approach] because [rationale]
-- We're prioritizing [requirement] over [requirement] because [reason]
-- We're deferring [requirement] to Phase 2 because [justification]
-
-COMPLIANCE STRATEGY:
-
-- We'll pursue [pathway] for regulatory approval
-- We'll implement [standard] for industry compliance
-- We'll handle [requirement] by [approach]
-
-RISK DECISIONS:
-
-- We accept [risk] because [reason]
-- We'll mitigate [risk] through [approach]
-- We'll monitor [risk] by [method]
-
-Any decisions you want to revisit or rationale to add?"
-
-key_decisions
-
-
-
-Synthesize research into specific recommendations
-
-"Based on our research, here are my recommendations for your PRD and development:
-
-MUST HAVE (Domain Critical):
-
-1. [Specific requirement with why it's critical]
-2. [Specific requirement with why it's critical]
-3. [Specific requirement with why it's critical]
-
-SHOULD HAVE (Domain Important):
-
-1. [Requirement that's important but not blocking]
-2. [Requirement that's important but not blocking]
-
-CONSIDER (Domain Nice-to-Have):
-
-1. [Enhancement that would differentiate]
-2. [Enhancement that would differentiate]
-
-DEVELOPMENT SEQUENCE:
-
-1. First: [What to build first and why]
-2. Then: [What comes next and why]
-3. Later: [What can wait and why]
-
-EXPERTISE NEEDED:
-
-- [Domain expert role]: For [specific areas]
-- [Technical expert role]: For [specific requirements]
-
-TIMELINE CONSIDERATIONS:
-
-- Allow [time] for [process/approval]
-- Start [requirement] early because [reason]
-- [Requirement] can be parallel with development
-
-Do these recommendations feel right? What would you adjust?"
-
-recommendations
-
-
-
-Create clear handoff to PRD workflow
-
-"I've captured everything in domain-brief.md. Here's the summary for your PRD:
-
-DOMAIN: {identified_domain}
-COMPLEXITY: {high|medium}
-
-KEY REQUIREMENTS TO INCORPORATE:
-
-- [Requirement 1 - critical for domain]
-- [Requirement 2 - critical for domain]
-- [Requirement 3 - important consideration]
-
-IMPACTS ON:
-
-- Functional Requirements: [How domain affects features]
-- Non-Functional Requirements: [Performance, security, etc.]
-- Architecture: [System design considerations]
-- Development: [Process and timeline impacts]
-
-REFERENCE DOCS:
-
-- Full domain analysis: domain-brief.md
-- Regulations researched: [List with links]
-- Standards referenced: [List with links]
-
-When you return to PRD, reference this brief for domain context.
-
-Any final questions before we wrap up the domain research?"
-
-summary_for_prd
-
-
-
-
-
-
-
diff --git a/src/modules/bmm/workflows/1-analysis/domain-research/template.md b/src/modules/bmm/workflows/1-analysis/domain-research/template.md
deleted file mode 100644
index 37e50bf7..00000000
--- a/src/modules/bmm/workflows/1-analysis/domain-research/template.md
+++ /dev/null
@@ -1,180 +0,0 @@
-# Domain Brief - {project_name}
-
-Generated: {date}
-Domain: {primary_domain}
-Complexity: {complexity_level}
-
-## Executive Summary
-
-{brief_overview_of_domain_research_findings}
-
-## Domain Overview
-
-### Industry Context
-
-{domain_overview}
-
-### Regulatory Landscape
-
-{regulatory_environment}
-
-### Key Stakeholders
-
-{stakeholder_analysis}
-
-## Critical Concerns
-
-### Compliance Requirements
-
-{concern_mapping}
-
-### Technical Constraints
-
-{technical_limitations_from_domain}
-
-### Safety/Risk Considerations
-
-{safety_risk_factors}
-
-## Regulatory Requirements
-
-{regulatory_requirements}
-
-## Industry Standards
-
-{industry_standards}
-
-## Practical Implications
-
-### Architecture Impact
-
-{architecture_implications}
-
-### Development Impact
-
-{development_implications}
-
-### Timeline Impact
-
-{timeline_implications}
-
-### Cost Impact
-
-{cost_implications}
-
-## Domain Patterns
-
-### Established Patterns
-
-{domain_patterns}
-
-### Innovation Opportunities
-
-{innovation_notes}
-
-## Risk Assessment
-
-### Identified Risks
-
-{risk_assessment}
-
-### Mitigation Strategies
-
-{mitigation_approaches}
-
-## Validation Strategy
-
-### Compliance Validation
-
-{compliance_validation_approach}
-
-### Technical Validation
-
-{technical_validation_approach}
-
-### Domain Expert Validation
-
-{expert_validation_approach}
-
-## Key Decisions
-
-{key_decisions}
-
-## Recommendations
-
-### Must Have (Critical)
-
-{critical_requirements}
-
-### Should Have (Important)
-
-{important_requirements}
-
-### Consider (Nice-to-Have)
-
-{optional_enhancements}
-
-### Development Sequence
-
-{recommended_sequence}
-
-### Required Expertise
-
-{expertise_needed}
-
-## PRD Integration Guide
-
-### Summary for PRD
-
-{summary_for_prd}
-
-### Requirements to Incorporate
-
-- {requirement_1}
-- {requirement_2}
-- {requirement_3}
-
-### Architecture Considerations
-
-- {architecture_consideration_1}
-- {architecture_consideration_2}
-
-### Development Considerations
-
-- {development_consideration_1}
-- {development_consideration_2}
-
-## References
-
-### Regulations Researched
-
-- {regulation_1_with_link}
-- {regulation_2_with_link}
-
-### Standards Referenced
-
-- {standard_1_with_link}
-- {standard_2_with_link}
-
-### Additional Resources
-
-- {resource_1}
-- {resource_2}
-
-## Appendix
-
-### Research Notes
-
-{detailed_research_notes}
-
-### Conversation Highlights
-
-{key_discussion_points_with_user}
-
-### Open Questions
-
-{questions_requiring_further_research}
-
----
-
-_This domain brief was created through collaborative research between {user_name} and the AI facilitator. It should be referenced during PRD creation and updated as new domain insights emerge._
diff --git a/src/modules/bmm/workflows/1-analysis/domain-research/workflow.yaml b/src/modules/bmm/workflows/1-analysis/domain-research/workflow.yaml
deleted file mode 100644
index 6592ed9a..00000000
--- a/src/modules/bmm/workflows/1-analysis/domain-research/workflow.yaml
+++ /dev/null
@@ -1,56 +0,0 @@
-# Domain Research Workflow Configuration
-name: domain-research
-description: "Collaborative exploration of domain-specific requirements, regulations, and patterns for complex projects"
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-document_output_language: "{config_source}:document_output_language"
-user_skill_level: "{config_source}:user_skill_level"
-date: system-generated
-
-# Module path and component files
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/domain-research"
-instructions: "{installed_path}/instructions.md"
-template: "{installed_path}/template.md"
-
-# Optional knowledge base (if exists)
-domain_knowledge_base: "{installed_path}/domain-knowledge-base.md"
-
-# Output configuration
-default_output_file: "{output_folder}/domain-brief.md"
-
-standalone: true
-
-# Web bundle configuration for standalone deployment
-web_bundle:
- name: "domain-research"
- description: "Collaborative exploration of domain-specific requirements, regulations, and patterns for complex projects"
- author: "BMad"
-
- # Core workflow files ({bmad_folder}/-relative paths)
- instructions: "{bmad_folder}/bmm/workflows/1-analysis/domain-research/instructions.md"
- template: "{bmad_folder}/bmm/workflows/1-analysis/domain-research/template.md"
-
- # Default configuration values (can be overridden during bundle setup)
- defaults:
- user_name: "User"
- communication_language: "English"
- document_output_language: "English"
- user_skill_level: "intermediate"
- output_folder: "./output"
-
- # Input/output configuration for web deployment
- default_output_file: "{output_folder}/domain-brief.md"
-
- # Complete file list - ALL files this workflow depends on
- web_bundle_files:
- # Core workflow files
- - "{bmad_folder}/bmm/workflows/1-analysis/domain-research/instructions.md"
- - "{bmad_folder}/bmm/workflows/1-analysis/domain-research/template.md"
-
- # Task dependencies (referenced in instructions.md)
- - "{bmad_folder}/core/tasks/workflow.xml"
diff --git a/src/modules/bmm/workflows/1-analysis/product-brief/checklist.md b/src/modules/bmm/workflows/1-analysis/product-brief/checklist.md
deleted file mode 100644
index d582d037..00000000
--- a/src/modules/bmm/workflows/1-analysis/product-brief/checklist.md
+++ /dev/null
@@ -1,115 +0,0 @@
-# Product Brief Validation Checklist
-
-## Document Structure
-
-- [ ] All required sections are present (Executive Summary through Appendices)
-- [ ] No placeholder text remains (e.g., [TODO], [NEEDS CONFIRMATION], {{variable}})
-- [ ] Document follows the standard brief template format
-- [ ] Sections are properly numbered and formatted with headers
-- [ ] Cross-references between sections are accurate
-
-## Executive Summary Quality
-
-- [ ] Product concept is explained in 1-2 clear sentences
-- [ ] Primary problem is clearly identified
-- [ ] Target market is specifically named (not generic)
-- [ ] Value proposition is compelling and differentiated
-- [ ] Summary accurately reflects the full document content
-
-## Problem Statement
-
-- [ ] Current state pain points are specific and measurable
-- [ ] Impact is quantified where possible (time, money, opportunities)
-- [ ] Explanation of why existing solutions fall short is provided
-- [ ] Urgency for solving the problem now is justified
-- [ ] Problem is validated with evidence or data points
-
-## Solution Definition
-
-- [ ] Core approach is clearly explained without implementation details
-- [ ] Key differentiators from existing solutions are identified
-- [ ] Explanation of why this will succeed is compelling
-- [ ] Solution aligns directly with stated problems
-- [ ] Vision paints a clear picture of the user experience
-
-## Target Users
-
-- [ ] Primary user segment has specific demographic/firmographic profile
-- [ ] User behaviors and current workflows are documented
-- [ ] Specific pain points are tied to user segments
-- [ ] User goals are clearly articulated
-- [ ] Secondary segment (if applicable) is equally detailed
-- [ ] Avoids generic personas like "busy professionals"
-
-## Goals and Metrics
-
-- [ ] Business objectives include measurable outcomes with targets
-- [ ] User success metrics focus on behaviors, not features
-- [ ] 3-5 KPIs are defined with clear definitions
-- [ ] All goals follow SMART criteria (Specific, Measurable, Achievable, Relevant, Time-bound)
-- [ ] Success metrics align with problem statement
-
-## MVP Scope
-
-- [ ] Core features list contains only true must-haves
-- [ ] Each core feature includes rationale for why it's essential
-- [ ] Out of scope section explicitly lists deferred features
-- [ ] MVP success criteria are specific and measurable
-- [ ] Scope is genuinely minimal and viable
-- [ ] No feature creep evident in "must-have" list
-
-## Technical Considerations
-
-- [ ] Target platforms are specified (web/mobile/desktop)
-- [ ] Browser/OS support requirements are documented
-- [ ] Performance requirements are defined if applicable
-- [ ] Accessibility requirements are noted
-- [ ] Technology preferences are marked as preferences, not decisions
-- [ ] Integration requirements with existing systems are identified
-
-## Constraints and Assumptions
-
-- [ ] Budget constraints are documented if known
-- [ ] Timeline or deadline pressures are specified
-- [ ] Team/resource limitations are acknowledged
-- [ ] Technical constraints are clearly stated
-- [ ] Key assumptions are listed and testable
-- [ ] Assumptions will be validated during development
-
-## Risk Assessment (if included)
-
-- [ ] Key risks include potential impact descriptions
-- [ ] Open questions are specific and answerable
-- [ ] Research areas are identified with clear objectives
-- [ ] Risk mitigation strategies are suggested where applicable
-
-## Overall Quality
-
-- [ ] Language is clear and free of jargon
-- [ ] Terminology is used consistently throughout
-- [ ] Document is ready for handoff to Product Manager
-- [ ] All [PM-TODO] items are clearly marked if present
-- [ ] References and source documents are properly cited
-
-## Completeness Check
-
-- [ ] Document provides sufficient detail for PRD creation
-- [ ] All user inputs have been incorporated
-- [ ] Market research findings are reflected if provided
-- [ ] Competitive analysis insights are included if available
-- [ ] Brief aligns with overall product strategy
-
-## Final Validation
-
-### Critical Issues Found:
-
-- [ ] None identified
-
-### Minor Issues to Address:
-
-- [ ] List any minor issues here
-
-### Ready for PM Handoff:
-
-- [ ] Yes, brief is complete and validated
-- [ ] No, requires additional work (specify above)
diff --git a/src/modules/bmm/workflows/1-analysis/product-brief/instructions.md b/src/modules/bmm/workflows/1-analysis/product-brief/instructions.md
deleted file mode 100644
index 6ecfd3da..00000000
--- a/src/modules/bmm/workflows/1-analysis/product-brief/instructions.md
+++ /dev/null
@@ -1,515 +0,0 @@
-# Product Brief - Context-Adaptive Discovery Instructions
-
-The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml
-You MUST have already loaded and processed: {installed_path}/workflow.yaml
-This workflow uses INTENT-DRIVEN FACILITATION - adapt organically to what emerges
-The goal is DISCOVERING WHAT MATTERS through natural conversation, not filling a template
-Communicate all responses in {communication_language} and adapt deeply to {user_skill_level}
-Generate all documents in {document_output_language}
-LIVING DOCUMENT: Write to the document continuously as you discover - never wait until the end
-⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.
-⚠️ CHECKPOINT PROTOCOL: After EVERY tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.
-
-## Input Document Discovery
-
-This workflow may reference: market research, brainstorming documents, user specified other inputs, or brownfield project documentation.
-
-**All input files are discovered and loaded automatically via the `discover_inputs` protocol in Step 0.5**
-
-After discovery completes, the following content variables will be available:
-
-- `{research_content}` - Market research or domain research documents
-- `{brainstorming_content}` - Brainstorming session outputs
-- `{document_project_content}` - Brownfield project documentation (intelligently loaded via INDEX_GUIDED strategy)
-
-
-
-
-Check if {output_folder}/bmm-workflow-status.yaml exists
-
-Set standalone_mode = true
-
-
- Load the FULL file: {output_folder}/bmm-workflow-status.yaml
- Parse workflow_status section
- Check status of "product-brief" workflow
- Get project_level from YAML metadata
- Find first non-completed workflow (next expected workflow)
-
-
-
-
- Re-running will overwrite the existing brief. Continue? (y/n)
-
-
- Exit workflow
-
-
-
-
-
- Continue with Product Brief anyway? (y/n)
-
-
- Exit workflow
-
-
-
-Set standalone_mode = false
-
-
-
-
-
-
-
-
-Welcome {user_name} warmly in {communication_language}
-
-Start with open exploration:
-
-- What sparked this idea?
-- What are you hoping to build?
-- Who is this for - yourself, a business, users you know?
-
-- "I'm here to help shape your product vision. Tell me about your idea and what got you excited about this? The more detail you can give me here the better I can help you further craft the idea."
-
-CRITICAL: Listen for context clues that reveal their situation:
-
-- Personal/hobby project (fun, learning, small audience)
-- Startup/solopreneur (market opportunity, competition matters)
-- Enterprise/corporate (stakeholders, compliance, strategic alignment)
-- Technical enthusiasm (implementation focused)
-- Business opportunity (market/revenue focused)
-- Problem frustration (solution focused)
-
-Based on their initial response, sense:
-
-- How formal/casual they want to be
-- Whether they think in business or technical terms
-- If they have existing materials to share
-- Their confidence level with the domain
-
-What's the project name?
-
-From even this first exchange, create initial document sections
-project_name
-executive_summary
-
-If they mentioned existing documents (research, brainstorming, etc.):
-
-- Load and analyze these materials
-- Extract key themes and insights
-- Reference these naturally in conversation: "I see from your research that..."
-- Use these to accelerate discovery, not repeat questions
-
-initial_vision
-
-
-
-Guide problem discovery through natural conversation
-
-DON'T ask: "What problem does this solve?"
-
-DO explore conversationally based on their context:
-
-For hobby projects:
-
-- "What's annoying you that this would fix?"
-- "What would this make easier or more fun?"
-- "Show me what the experience is like today without this"
-
-For business ventures:
-
-- "Walk me through the frustration your users face today"
-- "What's the cost of this problem - time, money, opportunities?"
-- "Who's suffering most from this? Tell me about them"
-- "What solutions have people tried? Why aren't they working?"
-
-For enterprise:
-
-- "What's driving the need for this internally?"
-- "Which teams/processes are most affected?"
-- "What's the business impact of not solving this?"
-- "Are there compliance or strategic drivers?"
-
-Listen for depth cues:
-
-- Brief answers → dig deeper with follow-ups
-- Detailed passion → let them flow, capture everything
-- Uncertainty → help them explore with examples
-- Multiple problems → help prioritize the core issue
-
-Adapt your response:
-
-- If they struggle: offer analogies, examples, frameworks
-- If they're clear: validate and push for specifics
-- If they're technical: explore implementation challenges
-- If they're business-focused: quantify impact
-
-Immediately capture what emerges - even if preliminary
-problem_statement
-
-
- Explore the measurable impact of the problem
- problem_impact
-
-
-
- Understand why existing solutions fall short
- existing_solutions_gaps
-
-
-Reflect understanding: "So the core issue is {{problem_summary}}, and {{impact_if_mentioned}}. Let me capture that..."
-
-
-
-Transition naturally from problem to solution
-
-Based on their energy and context, explore:
-
-For builders/makers:
-
-- "How do you envision this working?"
-- "Walk me through the experience you want to create"
-- "What's the 'magic moment' when someone uses this?"
-
-For business minds:
-
-- "What's your unique approach to solving this?"
-- "How is this different from what exists today?"
-- "What makes this the RIGHT solution now?"
-
-For enterprise:
-
-- "What would success look like for the organization?"
-- "How does this fit with existing systems/processes?"
-- "What's the transformation you're enabling?"
-
-Go deeper based on responses:
-
-- If innovative → explore the unique angle
-- If standard → focus on execution excellence
-- If technical → discuss key capabilities
-- If user-focused → paint the journey
-
-Web research when relevant:
-
-- If they mention competitors → research current solutions
-- If they claim innovation → verify uniqueness
-- If they reference trends → get current data
-
-
- {{competitor/market}} latest features 2024
- Use findings to sharpen differentiation discussion
-
-
-proposed_solution
-
-
- key_differentiators
-
-
-Continue building the living document
-
-
-
-Discover target users through storytelling, not demographics
-
-Facilitate based on project type:
-
-Personal/hobby:
-
-- "Who else would love this besides you?"
-- "Tell me about someone who would use this"
-- Keep it light and informal
-
-Startup/business:
-
-- "Describe your ideal first customer - not demographics, but their situation"
-- "What are they doing today without your solution?"
-- "What would make them say 'finally, someone gets it!'?"
-- "Are there different types of users with different needs?"
-
-Enterprise:
-
-- "Which roles/departments will use this?"
-- "Walk me through their current workflow"
-- "Who are the champions vs skeptics?"
-- "What about indirect stakeholders?"
-
-Push beyond generic personas:
-
-- Not: "busy professionals" → "Sales reps who waste 2 hours/day on data entry"
-- Not: "tech-savvy users" → "Developers who know Docker but hate configuring it"
-- Not: "small businesses" → "Shopify stores doing $10-50k/month wanting to scale"
-
-For each user type that emerges:
-
-- Current behavior/workflow
-- Specific frustrations
-- What they'd value most
-- Their technical comfort level
-
-primary_user_segment
-
-
- Explore secondary users only if truly different needs
- secondary_user_segment
-
-
-
- user_journey
-
-
-
-
-Explore success measures that match their context
-
-For personal projects:
-
-- "How will you know this is working well?"
-- "What would make you proud of this?"
-- Keep metrics simple and meaningful
-
-For startups:
-
-- "What metrics would convince you this is taking off?"
-- "What user behaviors show they love it?"
-- "What business metrics matter most - users, revenue, retention?"
-- Push for specific targets: "100 users" not "lots of users"
-
-For enterprise:
-
-- "How will the organization measure success?"
-- "What KPIs will stakeholders care about?"
-- "What are the must-hit metrics vs nice-to-haves?"
-
-Only dive deep into metrics if they show interest
-Skip entirely for pure hobby projects
-Focus on what THEY care about measuring
-
-
- success_metrics
-
-
- business_objectives
-
-
-
- key_performance_indicators
-
-
-
-Keep the document growing with each discovery
-
-
-
-Focus on FEATURES not epics - that comes in Phase 2
-
-Guide MVP scoping based on their maturity
-
-For experimental/hobby:
-
-- "What's the ONE thing this must do to be useful?"
-- "What would make a fun first version?"
-- Embrace simplicity
-
-For business ventures:
-
-- "What's the smallest version that proves your hypothesis?"
-- "What features would make early adopters say 'good enough'?"
-- "What's tempting to add but would slow you down?"
-- Be ruthless about scope creep
-
-For enterprise:
-
-- "What's the pilot scope that demonstrates value?"
-- "Which capabilities are must-have for initial rollout?"
-- "What can we defer to Phase 2?"
-
-Use this framing:
-
-- Core features: "Without this, the product doesn't work"
-- Nice-to-have: "This would be great, but we can launch without it"
-- Future vision: "This is where we're headed eventually"
-
-Challenge feature creep:
-
-- "Do we need that for launch, or could it come later?"
-- "What if we started without that - what breaks?"
-- "Is this core to proving the concept?"
-
-core_features
-
-
- out_of_scope
-
-
-
- future_vision_features
-
-
-
- mvp_success_criteria
-
-
-
-
-Only explore what emerges naturally - skip what doesn't matter
-
-Based on the conversation so far, selectively explore:
-
-IF financial aspects emerged:
-
-- Development investment needed
-- Revenue potential or cost savings
-- ROI timeline
-- Budget constraints
-
- financial_considerations
-
-
-IF market competition mentioned:
-
-- Competitive landscape
-- Market opportunity size
-- Differentiation strategy
-- Market timing
-
- {{market}} size trends 2024
- market_analysis
-
-
-IF technical preferences surfaced:
-
-- Platform choices (web/mobile/desktop)
-- Technology stack preferences
-- Integration needs
-- Performance requirements
-
- technical_preferences
-
-
-IF organizational context emerged:
-
-- Strategic alignment
-- Stakeholder buy-in needs
-- Change management considerations
-- Compliance requirements
-
- organizational_context
-
-
-IF risks or concerns raised:
-
-- Key risks and mitigation
-- Critical assumptions
-- Open questions needing research
-
- risks_and_assumptions
-
-
-IF timeline pressures mentioned:
-
-- Launch timeline
-- Critical milestones
-- Dependencies
-
- timeline_constraints
-
-
-Skip anything that hasn't naturally emerged
-Don't force sections that don't fit their context
-
-
-
-Review what's been captured with the user
-
-"Let me show you what we've built together..."
-
-Present the actual document sections created so far
-
-- Not a summary, but the real content
-- Shows the document has been growing throughout
-
-Ask:
-"Looking at this, what stands out as most important to you?"
-"Is there anything critical we haven't explored?"
-"Does this capture your vision?"
-
-Based on their response:
-
-- Refine sections that need more depth
-- Add any missing critical elements
-- Remove or simplify sections that don't matter
-- Ensure the document fits THEIR needs, not a template
-
-Make final refinements based on feedback
-final_refinements
-
-Create executive summary that captures the essence
-executive_summary
-
-
-The document has been building throughout our conversation
-Now ensure it's complete and well-organized
-
-
- Append summary of incorporated research
- supporting_materials
-
-
-Ensure the document structure makes sense for what was discovered:
-
-- Hobbyist projects might be 2-3 pages focused on problem/solution/features
-- Startup ventures might be 5-7 pages with market analysis and metrics
-- Enterprise briefs might be 10+ pages with full strategic context
-
-The document should reflect their world, not force their world into a template
-
-Your product brief is ready! Would you like to:
-
-1. Review specific sections together
-2. Make any final adjustments
-3. Save and move forward
-
-What feels right?
-
-Make any requested refinements
-final_document
-
-
-
- Load the FULL file: {output_folder}/bmm-workflow-status.yaml
- Find workflow_status key "product-brief"
- ONLY write the file path as the status value - no other text, notes, or metadata
- Update workflow_status["product-brief"] = "{output_folder}/bmm-product-brief-{{project_name}}-{{date}}.md"
- Save file, preserving ALL comments and structure including STATUS DEFINITIONS
-
-Find first non-completed workflow in workflow_status (next workflow to do)
-Determine next agent from path file based on next workflow
-
-
-
-
-
-
diff --git a/src/modules/bmm/workflows/1-analysis/product-brief/product-brief.template.md b/src/modules/bmm/workflows/1-analysis/product-brief/product-brief.template.md
new file mode 100644
index 00000000..2e70cb95
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/product-brief.template.md
@@ -0,0 +1,8 @@
+# Product Brief: {{project_name}}
+
+**Date:** {{date}}
+**Author:** {{user_name}}
+
+---
+
+
diff --git 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
new file mode 100644
index 00000000..e56062d1
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-01-init.md
@@ -0,0 +1,144 @@
+# Step 1: Product Brief Initialization
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+- ✅ ALWAYS treat this as collaborative discovery between PM peers
+- 📋 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
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis before taking any action
+- 💾 Initialize document and update frontmatter
+- 📖 Set up frontmatter `stepsCompleted: [1]` before loading next step
+- 🚫 FORBIDDEN to load next step until setup is complete
+
+## CONTEXT BOUNDARIES:
+
+- Variables from workflow.md are available in memory
+- Previous context = what's in output document + frontmatter
+- Don't assume knowledge from other steps
+- Input document discovery happens in this step
+
+## YOUR TASK:
+
+Initialize the product brief workflow by detecting continuation state and setting up the document.
+
+## INITIALIZATION SEQUENCE:
+
+### 1. Check for Existing Workflow
+
+First, check if the output document already exists:
+
+- Look for file at `{output_folder}/product-brief-{{project_name}}-{{date}}.md`
+- If exists, read the complete file including frontmatter
+- If not exists, this is a fresh workflow
+
+### 2. Handle Continuation (If Document Exists)
+
+If the document exists and has frontmatter with `stepsCompleted`:
+
+- **STOP here** and load `./step-01b-continue.md` immediately
+- Do not proceed with any initialization tasks
+- Let step-01b handle the continuation logic
+
+### 3. Fresh Workflow Setup (If No Document)
+
+If no document exists or no `stepsCompleted` in frontmatter:
+
+#### A. Input Document Discovery
+
+Discover and load context documents using smart discovery:
+
+**Research Documents (Priority: Sharded → Whole):**
+
+1. Check for sharded research folder: `{output_folder}/*research*/**/*.md`
+2. If folder exists: Load EVERY file in that folder completely for comprehensive research context
+3. If no folder exists: Try whole file: `{output_folder}/*research*.md`
+4. Add discovered files to `inputDocuments` frontmatter
+
+**Brainstorming Documents (Priority: Sharded → Whole):**
+
+1. Check for sharded brainstorming folder: `{output_folder}/*brainstorm*/**/*.md`
+2. If folder exists: Load useful brainstorming files completely
+3. If no folder exists: Try whole file: `{output_folder}/*brainstorm*.md`
+4. Add discovered files to `inputDocuments` frontmatter
+
+**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
+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}`
+Initialize frontmatter with:
+
+```yaml
+---
+stepsCompleted: []
+inputDocuments: []
+workflowType: 'product-brief'
+lastStep: 0
+project_name: '{{project_name}}'
+user_name: '{{user_name}}'
+date: '{{date}}'
+---
+```
+
+#### C. Complete Initialization and Report
+
+Complete setup and report to user:
+
+**Document Setup:**
+
+- Created: `{default_output_file}` 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"}
+- Project docs: {number of project files loaded or "None 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?
+
+[C] Continue to product vision discovery"
+
+## SUCCESS METRICS:
+
+✅ Existing workflow detected and handed off to step-01b correctly
+✅ 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:
+
+❌ Proceeding with fresh initialization when existing workflow exists
+❌ 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
+
+## NEXT STEP:
+
+After user selects [C] to continue, load `./step-02-vision.md` to begin the product vision discovery phase.
+
+Remember: Do NOT proceed to step-02 until user explicitly selects [C] to continue!
diff --git 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
new file mode 100644
index 00000000..615eb69b
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-01b-continue.md
@@ -0,0 +1,116 @@
+# Step 1B: Product Brief Continuation
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+- ✅ ALWAYS treat this as collaborative discovery between PM peers
+- 📋 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
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis of current state before taking action
+- 💾 Keep existing frontmatter `stepsCompleted` values
+- 📖 Only load documents that were already tracked in `inputDocuments`
+- 🚫 FORBIDDEN to modify content completed in previous steps
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter are already loaded
+- Previous context = complete document + existing frontmatter
+- Input documents listed in frontmatter were already processed
+- Last completed step = `lastStep` value from frontmatter
+
+## YOUR TASK:
+
+Resume the product brief workflow from where it was left off, ensuring smooth continuation.
+
+## CONTINUATION SEQUENCE:
+
+### 1. Analyze Current State
+
+Review the frontmatter to understand:
+
+- `stepsCompleted`: Which steps are already done
+- `lastStep`: The most recently completed step number
+- `inputDocuments`: What context was already loaded
+- All other frontmatter variables
+
+### 2. Load All Input Documents
+
+Reload the context documents listed in `inputDocuments`:
+
+- 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
+
+### 3. Summarize Current Progress
+
+Welcome the user back and provide context:
+"Welcome back {{user_name}}! I'm resuming our product brief collaboration for {{project_name}}.
+
+**Current Progress:**
+
+- Steps completed: {stepsCompleted}
+- Last worked on: Step {lastStep}
+- Context documents available: {len(inputDocuments)} files
+
+**Document Status:**
+
+- Current product brief is ready with all completed sections
+- Ready to continue from where we left off
+
+Does this look right, or do you want to make any adjustments before we proceed?"
+
+### 4. Determine Next Step
+
+Based on `lastStep` value, determine which step to load next:
+
+- If `lastStep = 1` → Load `./step-02-vision.md`
+- If `lastStep = 2` → Load `./step-03-users.md`
+- If `lastStep = 3` → Load `./step-04-metrics.md`
+- Continue this pattern for all steps
+- If `lastStep = 6` → Workflow already complete
+
+### 5. Present Continuation Options
+
+After presenting current progress, ask:
+"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
+
+## 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.
+
+Would you like me to:
+
+- Review the completed product brief with you
+- Suggest next workflow steps (like PRD creation)
+- Start a new product brief revision
+
+What would be most helpful?"
+
+## NEXT STEP:
+
+After user selects [C] to continue, load the appropriate next step file based on the `lastStep` value from frontmatter.
+
+Remember: Do NOT load the next step until user explicitly selects [C] to continue!
diff --git 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
new file mode 100644
index 00000000..5a34abd1
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-02-vision.md
@@ -0,0 +1,216 @@
+# Step 2: Product Vision Discovery
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+- ✅ ALWAYS treat this as collaborative discovery between PM peers
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- 💬 FOCUS on product vision, problem, and solution discovery only
+- 🎯 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
+- 💾 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
+
+## 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
+- 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
+- Input documents already loaded are in memory
+- This will be the first content section appended to the document
+- Focus on clear, compelling product vision and problem statement
+
+## YOUR TASK:
+
+Conduct comprehensive product vision discovery to define the core problem, solution, and unique value proposition.
+
+## VISION DISCOVERY SEQUENCE:
+
+### 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:**
+
+- What core problem are you trying to solve?
+- Who experiences this problem most acutely?
+- What would success look like for the people you're helping?
+- What excites you most about this solution?
+
+Let's start with the problem space before we get into solutions."
+
+### 2. Deep Problem Understanding
+
+Explore the problem from multiple angles:
+
+#### Problem Discovery Questions:
+
+- "How do people currently solve this problem?"
+- "What's frustrating about current solutions?"
+- "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:
+
+- "What solutions exist today?"
+- "Where do they fall short?"
+- "What gaps are they leaving open?"
+- "Why haven't existing solutions solved this completely?"
+
+### 4. Solution Vision
+
+Craft the proposed solution collaboratively:
+
+- "If we could solve this perfectly, what would that look like?"
+- "What's the simplest way we could make a meaningful difference?"
+- "What makes your approach different from what's out there?"
+- "What would make users say 'this is exactly what I needed'?"
+
+### 5. Unique Differentiators
+
+Identify what makes this product special:
+
+- "What's your unfair advantage?"
+- "What would be hard for competitors to copy?"
+- "What insight or approach is uniquely yours?"
+- "Why is now the right time for this solution?"
+
+### 6. Generate Executive Summary Content
+
+Prepare the content to append to the document:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Executive Summary
+
+[Executive summary content based on conversation]
+
+---
+
+## Core Vision
+
+### Problem Statement
+
+[Problem statement content based on conversation]
+
+### Problem Impact
+
+[Problem impact content based on conversation]
+
+### Why Existing Solutions Fall Short
+
+[Analysis of existing solution gaps based on conversation]
+
+### Proposed Solution
+
+[Proposed solution description based on conversation]
+
+### Key Differentiators
+
+[Key differentiators based on conversation]
+```
+
+### 7. Present Content and Menu
+
+Show the generated content and present choices:
+"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?**
+[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
+
+#### If 'A' (Advanced Elicitation):
+
+- Execute advanced-elicitation.xml with the current vision content
+- 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):
+
+- Execute party-mode workflow with the current vision content
+- 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):
+
+- Append the final content to `{default_output_file}`
+- Update frontmatter: `stepsCompleted: [1, 2]`
+- Load `./step-03-users.md`
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the document using the structure from step 6.
+
+## 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
+✅ 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 A/P/C menu after content generation
+❌ Appending content without user selecting 'C'
+
+## 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!
diff --git 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
new file mode 100644
index 00000000..d0a752f9
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-03-users.md
@@ -0,0 +1,219 @@
+# Step 3: Target Users Discovery
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+- ✅ ALWAYS treat this as collaborative discovery between PM peers
+- 📋 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
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis before taking any action
+- ⚠️ Present A/P/C menu after generating user segments content
+- 💾 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
+
+## 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
+- 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
+- Product vision and problem already defined in document
+- Input documents from step 1 may contain user research or insights
+- Focus on creating vivid, actionable user personas
+
+## YOUR TASK:
+
+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:
+"Now that we understand what {{project_name}} does, let's define who it's for.
+
+**User Discovery:**
+
+- Who experiences the problem we're solving?
+- Are there different types of users with different needs?
+- Who gets the most value from this solution?
+- Are there primary users and secondary users we should consider?
+
+Let's start by identifying the main user groups."
+
+### 2. Primary User Segment Development
+
+For each primary user segment, create rich personas:
+
+#### Persona Development Process:
+
+**Name & Context:**
+
+- Give them a realistic name and brief backstory
+- Define their role, environment, and context
+- What motivates them? What are their goals?
+
+**Problem Experience:**
+
+- How do they currently experience the problem?
+- What workarounds are they using?
+- What are the emotional and practical impacts?
+
+**Success Vision:**
+
+- What would success look like for them?
+- What would make them say "this is exactly what I needed"?
+
+#### 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?"
+- "What are they trying to accomplish that's hard right now?"
+
+### 3. Secondary User Segment Exploration
+
+Identify and develop secondary user segments:
+
+#### 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?"
+- "Who influences the decision to adopt or purchase this product?"
+- "Are there partner or stakeholder users who matter?"
+
+### 4. User Journey Mapping
+
+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:
+
+- "Walk me through how [Persona Name] would discover and start using {{project_name}}"
+- "What's their 'aha!' moment?"
+- "How does this product change how they work or live?"
+
+### 5. Generate Target Users Content
+
+Prepare the content to append to the document:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Target Users
+
+### Primary Users
+
+[Primary user segment content based on conversation]
+
+### Secondary Users
+
+[Secondary user segment content based on conversation, or N/A if not discussed]
+
+### User Journey
+
+[User journey content based on conversation, or N/A if not discussed]
+```
+
+### 6. Present Content and Menu
+
+Show the generated user content and present choices:
+"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?**
+[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
+
+#### If 'A' (Advanced Elicitation):
+
+- Execute advanced-elicitation.xml with the current user content
+- 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):
+
+- Execute party-mode workflow with the current user personas
+- 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):
+
+- Append the final content to `{default_output_file}`
+- Update frontmatter: `stepsCompleted: [1, 2, 3]`
+- Load `./step-04-metrics.md`
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the document using the structure from step 5.
+
+## SUCCESS METRICS:
+
+✅ Rich, believable user personas with clear motivations
+✅ 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 A/P/C menu after content generation
+❌ Appending content without user selecting 'C'
+
+## 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!
diff --git 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
new file mode 100644
index 00000000..fd04f2c9
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-04-metrics.md
@@ -0,0 +1,231 @@
+# Step 4: Success Metrics Definition
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+- ✅ ALWAYS treat this as collaborative discovery between PM peers
+- 📋 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
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis before taking any action
+- ⚠️ Present A/P/C menu after generating success metrics content
+- 💾 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
+
+## 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
+- 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
+- Product vision and target users already defined
+- Connect metrics directly to user value and business objectives
+- Focus on measurable, actionable success criteria
+
+## YOUR TASK:
+
+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:
+"Now that we know who {{project_name}} serves and what problem it solves, let's define what success looks like.
+
+**Success Discovery:**
+
+- How will we know we're succeeding for our users?
+- What would make users say 'this was worth it'?
+- What metrics show we're creating real value?
+
+Let's start with the user perspective."
+
+### 2. User Success Metrics
+
+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:
+
+- 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
+
+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:
+
+- **Growth Metrics:** User acquisition, market penetration
+- **Engagement Metrics:** Usage patterns, retention, satisfaction
+- **Financial Metrics:** Revenue, profitability, cost efficiency
+- **Strategic Metrics:** Market position, competitive advantage
+
+### 4. Key Performance Indicators
+
+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:
+
+- User acquisition: "X new users per month"
+- Engagement: "Y% of users complete core journey weekly"
+- Business impact: "$Z in cost savings or revenue generation"
+
+### 5. Connect Metrics to Strategy
+
+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
+- Avoid vanity metrics that don't drive decisions
+
+### 6. Generate Success Metrics Content
+
+Prepare the content to append to the document:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Success Metrics
+
+[Success metrics content based on conversation]
+
+### Business Objectives
+
+[Business objectives content based on conversation, or N/A if not discussed]
+
+### Key Performance Indicators
+
+[Key performance indicators content based on conversation, or N/A if not discussed]
+```
+
+### 7. Present Content and Menu
+
+Show the generated metrics content and present choices:
+"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?**
+[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
+
+#### If 'A' (Advanced Elicitation):
+
+- Execute advanced-elicitation.xml with the current metrics content
+- 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):
+
+- Execute party-mode workflow with the current success metrics
+- 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):
+
+- Append the final content to `{default_output_file}`
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
+- Load `./step-05-scope.md`
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the document using the structure from step 6.
+
+## SUCCESS METRICS:
+
+✅ User success metrics that focus on outcomes and behaviors
+✅ 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 A/P/C menu after content generation
+❌ Appending content without user selecting 'C'
+
+## 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!
diff --git 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
new file mode 100644
index 00000000..6bf56645
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-05-scope.md
@@ -0,0 +1,244 @@
+# Step 5: MVP Scope Definition
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+- ✅ ALWAYS treat this as collaborative discovery between PM peers
+- 📋 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
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis before taking any action
+- ⚠️ Present A/P/C menu after generating scope content
+- 💾 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
+
+## 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
+- 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
+- Product vision, users, and success metrics already defined
+- Focus on defining what's essential for MVP vs. future enhancements
+- Balance user needs with implementation feasibility
+
+## YOUR TASK:
+
+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:
+"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:**
+
+- What's the absolute minimum we need to deliver to solve the core problem?
+- What features would make users say 'this solves my problem'?
+- How do we balance ambition with getting something valuable to users quickly?
+
+Let's start with the MVP mindset: what's the smallest version that creates real value?"
+
+### 2. MVP Core Features Definition
+
+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:
+
+- **Solves Core Problem:** Addresses the main pain point effectively
+- **User Value:** Creates meaningful outcome for target users
+- **Feasible:** Achievable with available resources and timeline
+- **Testable:** Allows learning and iteration based on user feedback
+
+### 3. Out of Scope Boundaries
+
+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:
+
+- Clear communication about what's not included
+- Rationale for deferring certain features
+- Timeline considerations for future additions
+- Trade-off explanations for stakeholders
+
+### 4. MVP Success Criteria
+
+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:
+
+- User adoption metrics
+- Problem validation evidence
+- Technical feasibility confirmation
+- Business model validation
+
+### 5. Future Vision Exploration
+
+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:
+
+- Post-MVP enhancements that build on core functionality
+- Scale considerations and growth capabilities
+- Platform or ecosystem expansion opportunities
+- Advanced features that differentiate in the long term
+
+### 6. Generate MVP Scope Content
+
+Prepare the content to append to the document:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## MVP Scope
+
+### Core Features
+
+[Core features content based on conversation]
+
+### Out of Scope for MVP
+
+[Out of scope content based on conversation, or N/A if not discussed]
+
+### MVP Success Criteria
+
+[MVP success criteria content based on conversation, or N/A if not discussed]
+
+### Future Vision
+
+[Future vision content based on conversation, or N/A if not discussed]
+```
+
+### 7. Present Content and Menu
+
+Show the generated scope content and present choices:
+"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?**
+[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
+
+#### If 'A' (Advanced Elicitation):
+
+- Execute advanced-elicitation.xml with the current scope content
+- 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):
+
+- Execute party-mode workflow with the current MVP scope
+- 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):
+
+- Append the final content to `{default_output_file}`
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
+- Load `./step-06-complete.md`
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the document using the structure from step 6.
+
+## 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
+✅ 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 A/P/C menu after content generation
+❌ Appending content without user selecting 'C'
+
+## 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!
diff --git 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
new file mode 100644
index 00000000..ac891b31
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-06-complete.md
@@ -0,0 +1,193 @@
+# Step 6: Product Brief Completion
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ THIS IS A FINAL STEP - Product brief completion required
+- 🛑 NO content generation - this is a wrap-up step
+- 📋 FINALIZE document and update workflow status
+- 💬 FOCUS on completion, next steps, and suggestions
+- 🎯 UPDATE workflow status files with completion information
+
+## 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
+
+## 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
+- Workflow frontmatter shows all completed steps
+- All collaborative content has been generated and saved
+- Focus on completion, validation, and next steps
+
+## YOUR TASK:
+
+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:
+"🎉 **Product Brief Complete, {{user_name}}!**
+
+I've successfully collaborated with you to create a comprehensive Product Brief for {{project_name}}.
+
+**What we've accomplished:**
+
+- ✅ Executive Summary with clear vision and problem statement
+- ✅ Core Vision with solution definition and unique differentiators
+- ✅ Target Users with rich personas and user journeys
+- ✅ Success Metrics with measurable outcomes and business objectives
+- ✅ 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}`
+
+This brief serves as the foundation for all subsequent product development activities and strategic decisions."
+
+### 2. Workflow Status Update
+
+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}`
+- Add completion timestamp and metadata
+- Save file, preserving all comments and structure
+
+### 3. Document Quality Check
+
+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:**
+
+- Do all sections align with the core problem statement?
+- Is user value consistently emphasized throughout?
+- Are success criteria traceable to user needs and business goals?
+- Does MVP scope align with the problem and solution?
+
+### 4. Suggest Next Steps
+
+Provide guidance on logical next workflows:
+
+**Recommended Next Workflow:**
+
+1. `workflow prd` - Create detailed Product Requirements Document
+ - Brief provides foundation for detailed requirements
+ - User personas inform journey mapping
+ - Success metrics become specific acceptance criteria
+ - MVP scope becomes detailed feature specifications
+
+**Other Potential Next Steps:** 2. `workflow create-ux-design` - UX research and design 3. `workflow create-architecture` - Technical architecture planning 4. `workflow domain-research` - Deep market or domain research (if needed)
+
+**Strategic Considerations:**
+
+- The PRD workflow builds directly on this brief for detailed planning
+- Consider team capacity and immediate priorities
+- Use brief to validate concept before committing to detailed work
+- Brief can guide early technical feasibility discussions
+
+### 5. Final Completion Confirmation
+
+Confirm completion with user:
+"**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:
+
+- Clear vision and problem definition
+- Deep understanding of target users
+- Measurable success criteria
+- Focused MVP scope with realistic boundaries
+- Inspiring long-term vision
+
+**Ready to continue with:**
+
+- 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]"
+
+## SUCCESS METRICS:
+
+✅ Product brief contains all essential sections
+✅ 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:
+
+❌ 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
+
+## PRODUCT BRIEF COMPLETION CHECKLIST:
+
+### Document Structure Complete:
+
+- [ ] Executive Summary with vision and problem statement
+- [ ] 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:
+
+- [ ] All steps completed with user confirmation
+- [ ] All content saved to document
+- [ ] Frontmatter properly updated
+- [ ] Workflow status file updated
+- [ ] Next steps clearly communicated
+
+## NEXT STEPS GUIDANCE:
+
+**Immediate Options:**
+
+1. **PRD Workflow** - Transform brief into detailed requirements
+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?**
diff --git a/src/modules/bmm/workflows/1-analysis/product-brief/template.md b/src/modules/bmm/workflows/1-analysis/product-brief/template.md
deleted file mode 100644
index 4684bdc5..00000000
--- a/src/modules/bmm/workflows/1-analysis/product-brief/template.md
+++ /dev/null
@@ -1,181 +0,0 @@
-# Product Brief: {{project_name}}
-
-**Date:** {{date}}
-**Author:** {{user_name}}
-**Context:** {{context_type}}
-
----
-
-## Executive Summary
-
-{{executive_summary}}
-
----
-
-## Core Vision
-
-### Problem Statement
-
-{{problem_statement}}
-
-{{#if problem_impact}}
-
-### Problem Impact
-
-{{problem_impact}}
-{{/if}}
-
-{{#if existing_solutions_gaps}}
-
-### Why Existing Solutions Fall Short
-
-{{existing_solutions_gaps}}
-{{/if}}
-
-### Proposed Solution
-
-{{proposed_solution}}
-
-{{#if key_differentiators}}
-
-### Key Differentiators
-
-{{key_differentiators}}
-{{/if}}
-
----
-
-## Target Users
-
-### Primary Users
-
-{{primary_user_segment}}
-
-{{#if secondary_user_segment}}
-
-### Secondary Users
-
-{{secondary_user_segment}}
-{{/if}}
-
-{{#if user_journey}}
-
-### User Journey
-
-{{user_journey}}
-{{/if}}
-
----
-
-{{#if success_metrics}}
-
-## Success Metrics
-
-{{success_metrics}}
-
-{{#if business_objectives}}
-
-### Business Objectives
-
-{{business_objectives}}
-{{/if}}
-
-{{#if key_performance_indicators}}
-
-### Key Performance Indicators
-
-{{key_performance_indicators}}
-{{/if}}
-{{/if}}
-
----
-
-## MVP Scope
-
-### Core Features
-
-{{core_features}}
-
-{{#if out_of_scope}}
-
-### Out of Scope for MVP
-
-{{out_of_scope}}
-{{/if}}
-
-{{#if mvp_success_criteria}}
-
-### MVP Success Criteria
-
-{{mvp_success_criteria}}
-{{/if}}
-
-{{#if future_vision_features}}
-
-### Future Vision
-
-{{future_vision_features}}
-{{/if}}
-
----
-
-{{#if market_analysis}}
-
-## Market Context
-
-{{market_analysis}}
-{{/if}}
-
-{{#if financial_considerations}}
-
-## Financial Considerations
-
-{{financial_considerations}}
-{{/if}}
-
-{{#if technical_preferences}}
-
-## Technical Preferences
-
-{{technical_preferences}}
-{{/if}}
-
-{{#if organizational_context}}
-
-## Organizational Context
-
-{{organizational_context}}
-{{/if}}
-
-{{#if risks_and_assumptions}}
-
-## Risks and Assumptions
-
-{{risks_and_assumptions}}
-{{/if}}
-
-{{#if timeline_constraints}}
-
-## Timeline
-
-{{timeline_constraints}}
-{{/if}}
-
-{{#if supporting_materials}}
-
-## Supporting Materials
-
-{{supporting_materials}}
-{{/if}}
-
----
-
-_This Product Brief captures the vision and requirements for {{project_name}}._
-
-_It was created through collaborative discovery and reflects the unique needs of this {{context_type}} project._
-
-{{#if next_workflow}}
-_Next: {{next_workflow}} will transform this brief into detailed planning artifacts._
-{{else}}
-_Next: Use the PRD workflow to create detailed product requirements from this brief._
-{{/if}}
diff --git a/src/modules/bmm/workflows/1-analysis/product-brief/workflow.md b/src/modules/bmm/workflows/1-analysis/product-brief/workflow.md
new file mode 100644
index 00000000..7889aad8
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/workflow.md
@@ -0,0 +1,47 @@
+---
+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.
+---
+
+# 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.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **micro-file architecture** for disciplined execution:
+
+- Each step is a self-contained file with embedded rules
+- Sequential progression with user control at each step
+- Document state tracked in frontmatter
+- Append-only document building through conversation
+
+---
+
+## INITIALIZATION
+
+### Configuration Loading
+
+Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve:
+
+- `project_name`, `output_folder`, `user_name`
+- `communication_language`, `document_output_language`, `user_skill_level`
+- `date` as system-generated current datetime
+
+### Paths
+
+- `installed_path` = `{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief`
+- `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.
diff --git a/src/modules/bmm/workflows/1-analysis/product-brief/workflow.yaml b/src/modules/bmm/workflows/1-analysis/product-brief/workflow.yaml
deleted file mode 100644
index d94b4dc2..00000000
--- a/src/modules/bmm/workflows/1-analysis/product-brief/workflow.yaml
+++ /dev/null
@@ -1,61 +0,0 @@
-# Product Brief - Interactive Workflow Configuration
-name: product-brief
-description: "Interactive product brief creation workflow that guides users through defining their product vision with multiple input sources and conversational collaboration"
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-document_output_language: "{config_source}:document_output_language"
-user_skill_level: "{config_source}:user_skill_level"
-date: system-generated
-
-# Smart input file references - handles both whole docs and sharded docs
-# Priority: Whole document first, then sharded version
-# Strategy: How to load sharded documents (FULL_LOAD, SELECTIVE_LOAD, INDEX_GUIDED)
-input_file_patterns:
- research:
- description: "Market research or competitive analysis (optional)"
- whole: "{output_folder}/*research*.md"
- sharded: "{output_folder}/*research*/index.md"
- load_strategy: "FULL_LOAD"
-
- brainstorming:
- description: "Brainstorming session outputs (optional)"
- whole: "{output_folder}/*brainstorm*.md"
- sharded: "{output_folder}/*brainstorm*/index.md"
- load_strategy: "FULL_LOAD"
-
- document_project:
- description: "Brownfield project documentation (optional)"
- sharded: "{output_folder}/index.md"
- load_strategy: "INDEX_GUIDED"
-
-# Module path and component files
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief"
-template: "{installed_path}/template.md"
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-
-# Output configuration
-default_output_file: "{output_folder}/product-brief-{{project_name}}-{{date}}.md"
-
-standalone: true
-
-web_bundle:
- name: "product-brief"
- description: "Interactive product brief creation workflow that guides users through defining their product vision with multiple input sources and conversational collaboration"
- author: "BMad"
- instructions: "{bmad_folder}/bmm/workflows/1-analysis/product-brief/instructions.md"
- validation: "{bmad_folder}/bmm/workflows/1-analysis/product-brief/checklist.md"
- template: "{bmad_folder}/bmm/workflows/1-analysis/product-brief/template.md"
- web_bundle_files:
- # Core workflow files
- - "{bmad_folder}/bmm/workflows/1-analysis/product-brief/template.md"
- - "{bmad_folder}/bmm/workflows/1-analysis/product-brief/instructions.md"
- - "{bmad_folder}/bmm/workflows/1-analysis/product-brief/checklist.md"
-
- # Task dependencies (referenced in instructions.md)
- - "{bmad_folder}/core/tasks/workflow.xml"
diff --git a/src/modules/bmm/workflows/1-analysis/research/checklist-deep-prompt.md b/src/modules/bmm/workflows/1-analysis/research/checklist-deep-prompt.md
deleted file mode 100644
index d515eb51..00000000
--- a/src/modules/bmm/workflows/1-analysis/research/checklist-deep-prompt.md
+++ /dev/null
@@ -1,144 +0,0 @@
-# Deep Research Prompt Validation Checklist
-
-## 🚨 CRITICAL: Anti-Hallucination Instructions (PRIORITY)
-
-### Citation Requirements Built Into Prompt
-
-- [ ] Prompt EXPLICITLY instructs: "Cite sources with URLs for ALL factual claims"
-- [ ] Prompt requires: "Include source name, date, and URL for every statistic"
-- [ ] Prompt mandates: "If you cannot find reliable data, state 'No verified data found for [X]'"
-- [ ] Prompt specifies inline citation format (e.g., "[Source: Company, Year, URL]")
-- [ ] Prompt requires References section at end with all sources listed
-
-### Multi-Source Verification Requirements
-
-- [ ] Prompt instructs: "Cross-reference critical claims with at least 2 independent sources"
-- [ ] Prompt requires: "Note when sources conflict and present all viewpoints"
-- [ ] Prompt specifies: "Verify version numbers and dates from official sources"
-- [ ] Prompt mandates: "Mark confidence levels: [Verified], [Single source], [Uncertain]"
-
-### Fact vs Analysis Distinction
-
-- [ ] Prompt requires clear labeling: "Distinguish FACTS (sourced), ANALYSIS (your interpretation), SPECULATION (projections)"
-- [ ] Prompt instructs: "Do not present assumptions or analysis as verified facts"
-- [ ] Prompt requires: "Label projections and forecasts clearly as such"
-- [ ] Prompt warns: "Avoid vague attributions like 'experts say' - name the expert/source"
-
-### Source Quality Guidance
-
-- [ ] Prompt specifies preferred sources (e.g., "Official docs > analyst reports > blog posts")
-- [ ] Prompt prioritizes recency: "Prioritize {{current_year}} sources for time-sensitive data"
-- [ ] Prompt requires credibility assessment: "Note source credibility for each citation"
-- [ ] Prompt warns against: "Do not rely on single blog posts for critical claims"
-
-### Anti-Hallucination Safeguards
-
-- [ ] Prompt warns: "If data seems convenient or too round, verify with additional sources"
-- [ ] Prompt instructs: "Flag suspicious claims that need third-party verification"
-- [ ] Prompt requires: "Provide date accessed for all web sources"
-- [ ] Prompt mandates: "Do NOT invent statistics - only use verified data"
-
-## Prompt Foundation
-
-### Topic and Scope
-
-- [ ] Research topic is specific and focused (not too broad)
-- [ ] Target platform is specified (ChatGPT, Gemini, Grok, Claude)
-- [ ] Temporal scope defined and includes "current {{current_year}}" requirement
-- [ ] Source recency requirement specified (e.g., "prioritize 2024-2025 sources")
-
-## Content Requirements
-
-### Information Specifications
-
-- [ ] Types of information needed are listed (quantitative, qualitative, trends, case studies, etc.)
-- [ ] Preferred sources are specified (academic, industry reports, news, etc.)
-- [ ] Recency requirements are stated (e.g., "prioritize {{current_year}} sources")
-- [ ] Keywords and technical terms are included for search optimization
-- [ ] Validation criteria are defined (how to verify findings)
-
-### Output Structure
-
-- [ ] Desired format is clear (executive summary, comparison table, timeline, SWOT, etc.)
-- [ ] Key sections or questions are outlined
-- [ ] Depth level is specified (overview, standard, comprehensive, exhaustive)
-- [ ] Citation requirements are stated
-- [ ] Any special formatting needs are mentioned
-
-## Platform Optimization
-
-### Platform-Specific Elements
-
-- [ ] Prompt is optimized for chosen platform's capabilities
-- [ ] Platform-specific tips are included
-- [ ] Query limit considerations are noted (if applicable)
-- [ ] Platform strengths are leveraged (e.g., ChatGPT's multi-step search, Gemini's plan modification)
-
-### Execution Guidance
-
-- [ ] Research persona/perspective is specified (if applicable)
-- [ ] Special requirements are stated (bias considerations, recency, etc.)
-- [ ] Follow-up strategy is outlined
-- [ ] Validation approach is defined
-
-## Quality and Usability
-
-### Clarity and Completeness
-
-- [ ] Prompt language is clear and unambiguous
-- [ ] All placeholders and variables are replaced with actual values
-- [ ] Prompt can be copy-pasted directly into platform
-- [ ] No contradictory instructions exist
-- [ ] Prompt is self-contained (doesn't assume unstated context)
-
-### Practical Utility
-
-- [ ] Execution checklist is provided (before, during, after research)
-- [ ] Platform usage tips are included
-- [ ] Follow-up questions are anticipated
-- [ ] Success criteria are defined
-- [ ] Output file format is specified
-
-## Research Depth
-
-### Scope Appropriateness
-
-- [ ] Scope matches user's available time and resources
-- [ ] Depth is appropriate for decision at hand
-- [ ] Key questions that MUST be answered are identified
-- [ ] Nice-to-have vs. critical information is distinguished
-
-## Validation Criteria
-
-### Quality Standards
-
-- [ ] Method for cross-referencing sources is specified
-- [ ] Approach to handling conflicting information is defined
-- [ ] Confidence level indicators are requested
-- [ ] Gap identification is included
-- [ ] Fact vs. opinion distinction is required
-
----
-
-## Issues Found
-
-### Critical Issues
-
-_List any critical gaps or errors that must be addressed:_
-
-- [ ] Issue 1: [Description]
-- [ ] Issue 2: [Description]
-
-### Minor Improvements
-
-_List minor improvements that would enhance the prompt:_
-
-- [ ] Issue 1: [Description]
-- [ ] Issue 2: [Description]
-
----
-
-**Validation Complete:** ☐ Yes ☐ No
-**Ready to Execute:** ☐ Yes ☐ No
-**Reviewer:** {agent}
-**Date:** {date}
diff --git a/src/modules/bmm/workflows/1-analysis/research/checklist-technical.md b/src/modules/bmm/workflows/1-analysis/research/checklist-technical.md
deleted file mode 100644
index d82ec6c9..00000000
--- a/src/modules/bmm/workflows/1-analysis/research/checklist-technical.md
+++ /dev/null
@@ -1,249 +0,0 @@
-# Technical/Architecture Research Validation Checklist
-
-## 🚨 CRITICAL: Source Verification and Fact-Checking (PRIORITY)
-
-### Version Number Verification (MANDATORY)
-
-- [ ] **EVERY** technology version number has cited source with URL
-- [ ] Version numbers verified via WebSearch from {{current_year}} (NOT from training data!)
-- [ ] Official documentation/release pages cited for each version
-- [ ] Release dates included with version numbers
-- [ ] LTS status verified from official sources (with URL)
-- [ ] No "assumed" or "remembered" version numbers - ALL must be verified
-
-### Technical Claim Source Verification
-
-- [ ] **EVERY** feature claim has source (official docs, release notes, website)
-- [ ] Performance benchmarks cite source (official benchmarks, third-party tests with URLs)
-- [ ] Compatibility claims verified (official compatibility matrix, documentation)
-- [ ] Community size/popularity backed by sources (GitHub stars, npm downloads, official stats)
-- [ ] "Supports X" claims verified via official documentation with URL
-- [ ] No invented capabilities or features
-
-### Source Quality for Technical Data
-
-- [ ] Official documentation prioritized (docs.technology.com > blog posts)
-- [ ] Version info from official release pages (highest credibility)
-- [ ] Benchmarks from official sources or reputable third-parties (not random blogs)
-- [ ] Community data from verified sources (GitHub, npm, official registries)
-- [ ] Pricing from official pricing pages (with URL and date verified)
-
-### Multi-Source Verification (Critical Technical Claims)
-
-- [ ] Major technical claims (performance, scalability) verified by 2+ sources
-- [ ] Technology comparisons cite multiple independent sources
-- [ ] "Best for X" claims backed by comparative analysis with sources
-- [ ] Production experience claims cite real case studies or articles with URLs
-- [ ] No single-source critical decisions without flagging need for verification
-
-### Anti-Hallucination for Technical Data
-
-- [ ] No invented version numbers or release dates
-- [ ] No assumed feature availability without verification
-- [ ] If current data not found, explicitly states "Could not verify {{current_year}} information"
-- [ ] Speculation clearly labeled (e.g., "Based on trends, technology may...")
-- [ ] No "probably supports" or "likely compatible" without verification
-
-## Technology Evaluation
-
-### Comprehensive Profiling
-
-For each evaluated technology:
-
-- [ ] Core capabilities and features are documented
-- [ ] Architecture and design philosophy are explained
-- [ ] Maturity level is assessed (experimental, stable, mature, legacy)
-- [ ] Community size and activity are measured
-- [ ] Maintenance status is verified (active, maintenance mode, abandoned)
-
-### Practical Considerations
-
-- [ ] Learning curve is evaluated
-- [ ] Documentation quality is assessed
-- [ ] Developer experience is considered
-- [ ] Tooling ecosystem is reviewed
-- [ ] Testing and debugging capabilities are examined
-
-### Operational Assessment
-
-- [ ] Deployment complexity is understood
-- [ ] Monitoring and observability options are evaluated
-- [ ] Operational overhead is estimated
-- [ ] Cloud provider support is verified
-- [ ] Container/Kubernetes compatibility is checked (if relevant)
-
-## Comparative Analysis
-
-### Multi-Dimensional Comparison
-
-- [ ] Technologies are compared across relevant dimensions
-- [ ] Performance benchmarks are included (if available)
-- [ ] Scalability characteristics are compared
-- [ ] Complexity trade-offs are analyzed
-- [ ] Total cost of ownership is estimated for each option
-
-### Trade-off Analysis
-
-- [ ] Key trade-offs between options are identified
-- [ ] Decision factors are prioritized based on user needs
-- [ ] Conditions favoring each option are specified
-- [ ] Weighted analysis reflects user's priorities
-
-## Real-World Evidence
-
-### Production Experience
-
-- [ ] Real-world production experiences are researched
-- [ ] Known issues and gotchas are documented
-- [ ] Performance data from actual deployments is included
-- [ ] Migration experiences are considered (if replacing existing tech)
-- [ ] Community discussions and war stories are referenced
-
-### Source Quality
-
-- [ ] Multiple independent sources validate key claims
-- [ ] Recent sources from {{current_year}} are prioritized
-- [ ] Practitioner experiences are included (blog posts, conference talks, forums)
-- [ ] Both proponent and critic perspectives are considered
-
-## Decision Support
-
-### Recommendations
-
-- [ ] Primary recommendation is clearly stated with rationale
-- [ ] Alternative options are explained with use cases
-- [ ] Fit for user's specific context is explained
-- [ ] Decision is justified by requirements and constraints
-
-### Implementation Guidance
-
-- [ ] Proof-of-concept approach is outlined
-- [ ] Key implementation decisions are identified
-- [ ] Migration path is described (if applicable)
-- [ ] Success criteria are defined
-- [ ] Validation approach is recommended
-
-### Risk Management
-
-- [ ] Technical risks are identified
-- [ ] Mitigation strategies are provided
-- [ ] Contingency options are outlined (if primary choice doesn't work)
-- [ ] Exit strategy considerations are discussed
-
-## Architecture Decision Record
-
-### ADR Completeness
-
-- [ ] Status is specified (Proposed, Accepted, Superseded)
-- [ ] Context and problem statement are clear
-- [ ] Decision drivers are documented
-- [ ] All considered options are listed
-- [ ] Chosen option and rationale are explained
-- [ ] Consequences (positive, negative, neutral) are identified
-- [ ] Implementation notes are included
-- [ ] References to research sources are provided
-
-## References and Source Documentation (CRITICAL)
-
-### References Section Completeness
-
-- [ ] Report includes comprehensive "References and Sources" section
-- [ ] Sources organized by category (official docs, benchmarks, community, architecture)
-- [ ] Every source includes: Title, Publisher/Site, Date Accessed, Full URL
-- [ ] URLs are clickable and functional (documentation links, release pages, GitHub)
-- [ ] Version verification sources clearly listed
-- [ ] Inline citations throughout report reference the sources section
-
-### Technology Source Documentation
-
-- [ ] For each technology evaluated, sources documented:
- - Official documentation URL
- - Release notes/changelog URL for version
- - Pricing page URL (if applicable)
- - Community/GitHub URL
- - Benchmark source URLs
-- [ ] Comparison data cites source for each claim
-- [ ] Architecture pattern sources cited (articles, books, official guides)
-
-### Source Quality Metrics
-
-- [ ] Report documents total sources cited
-- [ ] Official sources count (highest credibility)
-- [ ] Third-party sources count (benchmarks, articles)
-- [ ] Version verification count (all technologies verified {{current_year}})
-- [ ] Outdated sources flagged (if any used)
-
-### Citation Format Standards
-
-- [ ] Inline citations format: [Source: Docs URL] or [Version: 1.2.3, Source: Release Page URL]
-- [ ] Consistent citation style throughout
-- [ ] No vague citations like "according to the community" without specifics
-- [ ] GitHub links include star count and last update date
-- [ ] Documentation links point to current stable version docs
-
-## Document Quality
-
-### Anti-Hallucination Final Check
-
-- [ ] Spot-check 5 random version numbers - can you find the cited source?
-- [ ] Verify feature claims against official documentation
-- [ ] Check any performance numbers have benchmark sources
-- [ ] Ensure no "cutting edge" or "latest" without specific version number
-- [ ] Cross-check technology comparisons with cited sources
-
-### Structure and Completeness
-
-- [ ] Executive summary captures key findings
-- [ ] No placeholder text remains (all {{variables}} are replaced)
-- [ ] References section is complete and properly formatted
-- [ ] Version verification audit trail included
-- [ ] Document ready for technical fact-checking by third party
-
-## Research Completeness
-
-### Coverage
-
-- [ ] All user requirements were addressed
-- [ ] All constraints were considered
-- [ ] Sufficient depth for the decision at hand
-- [ ] Optional analyses were considered and included/excluded appropriately
-- [ ] Web research was conducted for current market data
-
-### Data Freshness
-
-- [ ] Current {{current_year}} data was used throughout
-- [ ] Version information is up-to-date
-- [ ] Recent developments and trends are included
-- [ ] Outdated or deprecated information is flagged or excluded
-
----
-
-## Issues Found
-
-### Critical Issues
-
-_List any critical gaps or errors that must be addressed:_
-
-- [ ] Issue 1: [Description]
-- [ ] Issue 2: [Description]
-
-### Minor Improvements
-
-_List minor improvements that would enhance the report:_
-
-- [ ] Issue 1: [Description]
-- [ ] Issue 2: [Description]
-
-### Additional Research Needed
-
-_List areas requiring further investigation:_
-
-- [ ] Topic 1: [Description]
-- [ ] Topic 2: [Description]
-
----
-
-**Validation Complete:** ☐ Yes ☐ No
-**Ready for Decision:** ☐ Yes ☐ No
-**Reviewer:** {agent}
-**Date:** {date}
diff --git a/src/modules/bmm/workflows/1-analysis/research/checklist.md b/src/modules/bmm/workflows/1-analysis/research/checklist.md
deleted file mode 100644
index ef0c8ad6..00000000
--- a/src/modules/bmm/workflows/1-analysis/research/checklist.md
+++ /dev/null
@@ -1,299 +0,0 @@
-# Market Research Report Validation Checklist
-
-## 🚨 CRITICAL: Source Verification and Fact-Checking (PRIORITY)
-
-### Source Citation Completeness
-
-- [ ] **EVERY** market size claim has at least 2 cited sources with URLs
-- [ ] **EVERY** growth rate/CAGR has cited sources with URLs
-- [ ] **EVERY** competitive data point (pricing, features, funding) has sources with URLs
-- [ ] **EVERY** customer statistic or insight has cited sources
-- [ ] **EVERY** industry trend claim has sources from {{current_year}} or recent years
-- [ ] All sources include: Name, Date, URL (clickable links)
-- [ ] No claims exist without verifiable sources
-
-### Source Quality and Credibility
-
-- [ ] Market size sources are HIGH credibility (Gartner, Forrester, IDC, government data, industry associations)
-- [ ] NOT relying on single blog posts or unverified sources for critical data
-- [ ] Sources are recent ({{current_year}} or within 1-2 years for time-sensitive data)
-- [ ] Primary sources prioritized over secondary/tertiary sources
-- [ ] Paywalled reports are cited with proper attribution (e.g., "Gartner Market Report 2025")
-
-### Multi-Source Verification (Critical Claims)
-
-- [ ] TAM calculation verified by at least 2 independent sources
-- [ ] SAM calculation methodology is transparent and sourced
-- [ ] SOM estimates are conservative and based on comparable benchmarks
-- [ ] Market growth rates corroborated by multiple analyst reports
-- [ ] Competitive market share data verified across sources
-
-### Conflicting Data Resolution
-
-- [ ] Where sources conflict, ALL conflicting estimates are presented
-- [ ] Variance between sources is explained (methodology, scope differences)
-- [ ] No arbitrary selection of "convenient" numbers without noting alternatives
-- [ ] Conflicting data is flagged with confidence levels
-- [ ] User is made aware of uncertainty in conflicting claims
-
-### Confidence Level Marking
-
-- [ ] Every major claim is marked with confidence level:
- - **[Verified - 2+ sources]** = High confidence, multiple independent sources agree
- - **[Single source - verify]** = Medium confidence, only one source found
- - **[Estimated - low confidence]** = Low confidence, calculated/projected without strong sources
-- [ ] Low confidence claims are clearly flagged for user to verify independently
-- [ ] Speculative/projected data is labeled as PROJECTION or FORECAST, not presented as fact
-
-### Fact vs Analysis vs Speculation
-
-- [ ] Clear distinction between:
- - **FACT:** Sourced data with citations (e.g., "Market is $5.2B [Source: Gartner 2025]")
- - **ANALYSIS:** Interpretation of facts (e.g., "This suggests strong growth momentum")
- - **SPECULATION:** Educated guesses (e.g., "This trend may continue if...")
-- [ ] Analysis and speculation are NOT presented as verified facts
-- [ ] Recommendations are based on sourced facts, not unsupported assumptions
-
-### Anti-Hallucination Verification
-
-- [ ] No invented statistics or "made up" market sizes
-- [ ] All percentages, dollar amounts, and growth rates are traceable to sources
-- [ ] If data couldn't be found, report explicitly states "No verified data available for [X]"
-- [ ] No use of vague sources like "industry experts say" without naming the expert/source
-- [ ] Version numbers, dates, and specific figures match source material exactly
-
-## Market Sizing Analysis (Source-Verified)
-
-### TAM Calculation Sources
-
-- [ ] TAM figure has at least 2 independent source citations
-- [ ] Calculation methodology is sourced (not invented)
-- [ ] Industry benchmarks used for sanity-check are cited
-- [ ] Growth rate assumptions are backed by sourced projections
-- [ ] Any adjustments or filters applied are justified and documented
-
-### SAM and SOM Source Verification
-
-- [ ] SAM constraints are based on sourced data (addressable market scope)
-- [ ] SOM competitive assumptions cite actual competitor data
-- [ ] Market share benchmarks reference comparable companies with sources
-- [ ] Scenarios (conservative/realistic/optimistic) are justified with sourced reasoning
-
-## Competitive Analysis (Source-Verified)
-
-### Competitor Data Source Verification
-
-- [ ] **EVERY** competitor mentioned has source for basic company info
-- [ ] Competitor pricing data has sources (website URLs, pricing pages, reviews)
-- [ ] Funding amounts cite sources (Crunchbase, press releases, SEC filings)
-- [ ] Product features verified through sources (official website, documentation, reviews)
-- [ ] Market positioning claims are backed by sources (analyst reports, company statements)
-- [ ] Customer count/user numbers cite sources (company announcements, verified reports)
-- [ ] Recent news and developments cite article URLs with dates from {{current_year}}
-
-### Competitive Data Credibility
-
-- [ ] Company websites/official sources used for product info (highest credibility)
-- [ ] Financial data from Crunchbase, PitchBook, or SEC filings (not rumors)
-- [ ] Review sites cited for customer sentiment (G2, Capterra, TrustPilot with URLs)
-- [ ] Pricing verified from official pricing pages (with URL and date checked)
-- [ ] No assumptions about competitors without sourced evidence
-
-### Competitive Claims Verification
-
-- [ ] Market share claims cite analyst reports or verified data
-- [ ] "Leading" or "dominant" claims backed by sourced market data
-- [ ] Competitor weaknesses cited from reviews, articles, or public statements (not speculation)
-- [ ] Product comparison claims verified (feature lists from official sources)
-
-## Customer Intelligence (Source-Verified)
-
-### Customer Data Sources
-
-- [ ] Customer segment data cites research sources (reports, surveys, studies)
-- [ ] Demographics/firmographics backed by census data, industry reports, or studies
-- [ ] Pain points sourced from customer research, reviews, surveys (not assumed)
-- [ ] Willingness to pay backed by pricing studies, surveys, or comparable market data
-- [ ] Buying behavior sourced from research studies or industry data
-- [ ] Jobs-to-be-Done insights cite customer research or validated frameworks
-
-### Customer Insight Credibility
-
-- [ ] Primary research (if conducted) documents sample size and methodology
-- [ ] Secondary research cites the original study/report with full attribution
-- [ ] Customer quotes or testimonials cite the source (interview, review site, case study)
-- [ ] Persona data based on real research findings (not fictional archetypes)
-- [ ] No invented customer statistics or behaviors without source backing
-
-### Positioning Analysis
-
-- [ ] Market positioning map uses relevant dimensions for the industry
-- [ ] White space opportunities are clearly identified
-- [ ] Differentiation strategy is supported by competitive gaps
-- [ ] Switching costs and barriers are quantified
-- [ ] Network effects and moats are assessed
-
-## Industry Analysis
-
-### Porter's Five Forces
-
-- [ ] Each force has a clear rating (Low/Medium/High) with justification
-- [ ] Specific examples and evidence support each assessment
-- [ ] Industry-specific factors are considered (not generic template)
-- [ ] Implications for strategy are drawn from each force
-- [ ] Overall industry attractiveness conclusion is provided
-
-### Trends and Dynamics
-
-- [ ] At least 5 major trends are identified with evidence
-- [ ] Technology disruptions are assessed for probability and timeline
-- [ ] Regulatory changes and their impacts are documented
-- [ ] Social/cultural shifts relevant to adoption are included
-- [ ] Market maturity stage is identified with supporting indicators
-
-## Strategic Recommendations
-
-### Go-to-Market Strategy
-
-- [ ] Target segment prioritization has clear rationale
-- [ ] Positioning statement is specific and differentiated
-- [ ] Channel strategy aligns with customer buying behavior
-- [ ] Partnership opportunities are identified with specific targets
-- [ ] Pricing strategy is justified by willingness-to-pay analysis
-
-### Opportunity Assessment
-
-- [ ] Each opportunity is sized quantitatively
-- [ ] Resource requirements are estimated (time, money, people)
-- [ ] Success criteria are measurable and time-bound
-- [ ] Dependencies and prerequisites are identified
-- [ ] Quick wins vs. long-term plays are distinguished
-
-### Risk Analysis
-
-- [ ] All major risk categories are covered (market, competitive, execution, regulatory)
-- [ ] Each risk has probability and impact assessment
-- [ ] Mitigation strategies are specific and actionable
-- [ ] Early warning indicators are defined
-- [ ] Contingency plans are outlined for high-impact risks
-
-## References and Source Documentation (CRITICAL)
-
-### References Section Completeness
-
-- [ ] Report includes comprehensive "References and Sources" section
-- [ ] Sources organized by category (market size, competitive, customer, trends)
-- [ ] Every source includes: Title/Name, Publisher, Date, Full URL
-- [ ] URLs are clickable and functional (not broken links)
-- [ ] Sources are numbered or organized for easy reference
-- [ ] Inline citations throughout report reference the sources section
-
-### Source Quality Metrics
-
-- [ ] Report documents total sources cited count
-- [ ] High confidence claims (2+ sources) count is reported
-- [ ] Single source claims are identified and counted
-- [ ] Low confidence/speculative claims are flagged
-- [ ] Web searches conducted count is included (for transparency)
-
-### Source Audit Trail
-
-- [ ] For each major section, sources are listed
-- [ ] TAM/SAM/SOM calculations show source for each number
-- [ ] Competitive data shows source for each competitor profile
-- [ ] Customer insights show research sources
-- [ ] Industry trends show article/report sources with dates
-
-### Citation Format Standards
-
-- [ ] Inline citations format: [Source: Company/Publication, Year, URL] or similar
-- [ ] Consistent citation style throughout document
-- [ ] No vague citations like "according to sources" without specifics
-- [ ] URLs are complete (not truncated)
-- [ ] Accessed/verified dates included for web sources
-
-## Document Quality
-
-### Anti-Hallucination Final Check
-
-- [ ] Read through entire report - does anything "feel" invented or too convenient?
-- [ ] Spot-check 5-10 random claims - can you find the cited source?
-- [ ] Check suspicious round numbers - are they actually from sources?
-- [ ] Verify any "shocking" statistics have strong sources
-- [ ] Cross-check key market size claims against multiple cited sources
-
-### Structure and Completeness
-
-- [ ] Executive summary captures all key insights
-- [ ] No placeholder text remains (all {{variables}} are replaced)
-- [ ] References section is complete and properly formatted
-- [ ] Source quality assessment included
-- [ ] Document ready for fact-checking by third party
-
-## Research Completeness
-
-### Coverage Check
-
-- [ ] All workflow steps were completed (none skipped without justification)
-- [ ] Optional analyses were considered and included where valuable
-- [ ] Web research was conducted for current market intelligence
-- [ ] Financial projections align with market size analysis
-- [ ] Implementation roadmap provides clear next steps
-
-### Validation
-
-- [ ] Key findings are triangulated across multiple sources
-- [ ] Surprising insights are double-checked for accuracy
-- [ ] Calculations are verified for mathematical accuracy
-- [ ] Conclusions logically follow from the analysis
-- [ ] Recommendations are actionable and specific
-
-## Final Quality Assurance
-
-### Ready for Decision-Making
-
-- [ ] Research answers all initial objectives
-- [ ] Sufficient detail for investment decisions
-- [ ] Clear go/no-go recommendation provided
-- [ ] Success metrics are defined
-- [ ] Follow-up research needs are identified
-
-### Document Meta
-
-- [ ] Research date is current
-- [ ] Confidence levels are indicated for key assertions
-- [ ] Next review date is set
-- [ ] Distribution list is appropriate
-- [ ] Confidentiality classification is marked
-
----
-
-## Issues Found
-
-### Critical Issues
-
-_List any critical gaps or errors that must be addressed:_
-
-- [ ] Issue 1: [Description]
-- [ ] Issue 2: [Description]
-
-### Minor Issues
-
-_List minor improvements that would enhance the report:_
-
-- [ ] Issue 1: [Description]
-- [ ] Issue 2: [Description]
-
-### Additional Research Needed
-
-_List areas requiring further investigation:_
-
-- [ ] Topic 1: [Description]
-- [ ] Topic 2: [Description]
-
----
-
-**Validation Complete:** ☐ Yes ☐ No
-**Ready for Distribution:** ☐ Yes ☐ No
-**Reviewer:** {reviewer}
-**Date:** {date}
diff --git a/src/modules/bmm/workflows/1-analysis/research/claude-code/injections.yaml b/src/modules/bmm/workflows/1-analysis/research/claude-code/injections.yaml
deleted file mode 100644
index 97137fc1..00000000
--- a/src/modules/bmm/workflows/1-analysis/research/claude-code/injections.yaml
+++ /dev/null
@@ -1,114 +0,0 @@
-# Market Research Workflow - Claude Code Integration Configuration
-# This file configures how subagents are installed and integrated
-
-subagents:
- # List of subagent files to be installed
- files:
- - bmm-market-researcher.md
- - bmm-trend-spotter.md
- - bmm-data-analyst.md
- - bmm-competitor-analyzer.md
- - bmm-user-researcher.md
-
- # Installation configuration
- installation:
- prompt: "The Market Research workflow includes specialized AI subagents for enhanced research capabilities. Would you like to install them?"
- location_options:
- - project # Install to .claude/agents/ in project
- - user # Install to ~/.claude/agents/ for all projects
- default_location: project
-
-# Content injections for the workflow
-injections:
- - injection_point: "market-research-subagents"
- description: "Injects subagent activation instructions into the workflow"
- content: |
-
- Claude Code Enhanced Mode: The following specialized subagents are available to enhance your market research:
-
- - **bmm-market-researcher**: Comprehensive market intelligence gathering and analysis
- - **bmm-trend-spotter**: Identifies emerging trends and weak signals
- - **bmm-data-analyst**: Quantitative analysis and market sizing calculations
- - **bmm-competitor-analyzer**: Deep competitive intelligence and positioning
- - **bmm-user-researcher**: User research, personas, and journey mapping
-
- These subagents will be automatically invoked when their expertise is relevant to the current research task.
- Use them PROACTIVELY throughout the workflow for enhanced insights.
-
-
- - injection_point: "market-tam-calculations"
- description: "Enhanced TAM calculation with data analyst"
- content: |
-
- Calculate TAM using multiple methodologies and provide confidence intervals.
- Use all available market data from previous research steps.
- Show detailed calculations and assumptions.
-
-
- - injection_point: "market-trends-analysis"
- description: "Enhanced trend analysis with trend spotter"
- content: |
-
- Identify emerging trends, weak signals, and future disruptions.
- Look for cross-industry patterns and second-order effects.
- Provide timeline estimates for mainstream adoption.
-
-
- - injection_point: "market-customer-segments"
- description: "Enhanced customer research"
- content: |
-
- Develop detailed user personas with jobs-to-be-done analysis.
- Map the complete customer journey with pain points and opportunities.
- Provide behavioral and psychographic insights.
-
-
- - injection_point: "market-executive-summary"
- description: "Enhanced executive summary synthesis"
- content: |
-
- Synthesize all research findings into a compelling executive summary.
- Highlight the most critical insights and strategic implications.
- Ensure all key metrics and recommendations are captured.
-
-
-# Configuration for subagent behavior
-configuration:
- auto_invoke: true # Automatically invoke subagents when relevant
- parallel_execution: true # Allow parallel subagent execution
- cache_results: true # Cache subagent outputs for reuse
-
- # Subagent-specific configurations
- subagent_config:
- bmm-market-researcher:
- priority: high
- max_execution_time: 300 # seconds
- retry_on_failure: true
-
- bmm-trend-spotter:
- priority: medium
- max_execution_time: 180
- retry_on_failure: false
-
- bmm-data-analyst:
- priority: high
- max_execution_time: 240
- retry_on_failure: true
-
- bmm-competitor-analyzer:
- priority: high
- max_execution_time: 300
- retry_on_failure: true
-
- bmm-user-researcher:
- priority: medium
- max_execution_time: 240
- retry_on_failure: false
-
-# Metadata
-metadata:
- compatible_with: "claude-code-1.0+"
- workflow: "market-research"
- module: "bmm"
- author: "BMad Builder"
- description: "Claude Code enhancements for comprehensive market research"
diff --git a/src/modules/bmm/workflows/1-analysis/research/deep-prompt-steps/step-01-init.md b/src/modules/bmm/workflows/1-analysis/research/deep-prompt-steps/step-01-init.md
new file mode 100644
index 00000000..ab06c73f
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/research/deep-prompt-steps/step-01-init.md
@@ -0,0 +1,191 @@
+# Deep Research Prompt Step 1: Context and Scope
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+- ✅ ALWAYS treat this as collaborative prompt engineering partnership
+- 📋 YOU ARE A RESEARCH METHODOLOGIST, not content generator
+- 💬 FOCUS on understanding research needs and creating structured prompts
+- 🔍 WEB RESEARCH OPTIONAL - May search for best practices in research prompting
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis before taking any action
+- ⚠️ Present A/P/C menu after initial context generation
+- 💾 ONLY save when user chooses C (Continue)
+- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
+- 🚫 FORBIDDEN to load next step until C is selected
+
+## COLLABORATION MENUS (A/P/C):
+
+This step will generate content and present choices:
+
+- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper prompt insights
+- **P (Party Mode)**: Bring multiple perspectives to validate prompt methodology
+- **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
+- 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 main workflow discovery are available
+- Research type = "deep-prompt" is already set
+- Focus on creating structured research prompts for AI platforms
+- May use web search for research prompting best practices
+
+## YOUR TASK:
+
+Understand the research prompting needs and establish the scope and methodology for creating structured research prompts.
+
+## DEEP PROMPT RESEARCH INITIALIZATION:
+
+### 1. Confirm Deep Prompt Research Direction
+
+Begin with prompt engineering positioning:
+"I'll guide you through **deep research prompt creation** where we develop structured, effective prompts for AI platforms.
+
+**Deep Prompt Research Focus:**
+
+- Structured prompt methodologies and frameworks
+- Multi-step research prompt design
+- Domain-specific prompt engineering techniques
+- Prompt optimization and testing strategies
+- Research workflow automation through prompts
+
+**What type of research prompts are we creating?**
+
+### 2. Gather Prompt Context
+
+Understand the specific prompting needs:
+
+#### Context Questions:
+
+- "What AI platforms or models will these prompts be used with?"
+- "What types of research topics or domains will the prompts cover?"
+- "What level of complexity do the research prompts need?"
+- "Are there specific methodologies or frameworks you want the prompts to follow?"
+- "What research outcomes or deliverables should the prompts generate?"
+
+### 3. Establish Prompt Research Scope
+
+Define the boundaries and objectives:
+
+#### Scope Definition:
+
+- "How many different types of research prompts do we need?"
+- "Should we focus on general research prompts or domain-specific ones?"
+- "Are we creating prompts for single-use research or repeatable workflows?"
+- "What level of detail should the prompts provide?"
+- "Should the prompts include data analysis, synthesis, or both?"
+
+### 4. Generate Prompt Research Overview
+
+Prepare initial content to append to the document:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Research Overview
+
+### Prompt Engineering Objectives
+
+[Prompt engineering objectives based on conversation]
+
+### Target AI Platforms
+
+[Target platforms and models based on conversation]
+
+### Research Prompt Types
+
+[Types of research prompts based on conversation]
+
+### Prompt Methodology Framework
+
+[Methodology framework for structuring research prompts]
+
+### Quality Assurance Approach
+
+[Quality assurance and testing approach for prompts]
+```
+
+### 5. Present Content and Menu
+
+Show the generated overview and present choices:
+"I've established the foundation for our **deep research prompt** creation. This will help you develop structured, effective prompts for AI-powered research.
+
+**Here's what I'll add to the document:**
+
+[Show the complete markdown content from step 4]
+
+**What would you like to do?**
+[A] Advanced Elicitation - Let's deepen our understanding of prompt engineering needs
+[P] Party Mode - Bring different perspectives on prompt methodology
+[C] Continue - Save this to the document and begin prompt framework development
+
+### 6. Handle Menu Selection
+
+#### If 'A' (Advanced Elicitation):
+
+- Execute advanced-elicitation.xml with current prompt overview
+- Process enhanced prompt insights that come back
+- Ask user: "Accept these improvements to the prompt research overview? (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):
+
+- Execute party-mode workflow with current prompt overview
+- Process collaborative prompt expertise and additional insights
+- Ask user: "Accept these changes to the prompt research overview? (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):
+
+- Append the final content to the research document
+- Update frontmatter: `stepsCompleted: [1]`
+- Load: `./step-02-prompt-frameworks.md`
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the research document using the structure from step 4.
+
+## SUCCESS METRICS:
+
+✅ Prompt research scope clearly defined and confirmed
+✅ Target AI platforms and models identified
+✅ Prompt methodology framework established
+✅ Quality assurance approach documented
+✅ A/P/C menu presented and handled correctly
+✅ Content properly appended to document when C selected
+✅ Proper routing to next prompt development step
+
+## FAILURE MODES:
+
+❌ Not confirming specific AI platforms or use cases
+❌ Missing prompt methodology framework definition
+❌ Not establishing quality assurance approach
+❌ Not presenting A/P/C menu after content generation
+❌ Appending content without user selecting 'C'
+
+## WEB RESEARCH READINESS:
+
+This step may include web search for:
+
+- Current best practices in AI research prompting
+- Prompt engineering methodologies and frameworks
+- Domain-specific prompt optimization techniques
+- AI platform-specific prompt capabilities
+
+## NEXT STEP:
+
+After user selects 'C' and content is saved to document, load `./step-02-prompt-frameworks.md` to begin structured prompt framework development.
+
+Remember: Focus on creating structured, effective prompts that enable AI-powered research workflows!
diff --git a/src/modules/bmm/workflows/1-analysis/research/deep-prompt-steps/step-02-prompt-engineering.md b/src/modules/bmm/workflows/1-analysis/research/deep-prompt-steps/step-02-prompt-engineering.md
new file mode 100644
index 00000000..869e6169
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/research/deep-prompt-steps/step-02-prompt-engineering.md
@@ -0,0 +1,190 @@
+# Deep Prompt Research Step 2: Prompt Engineering
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+- ✅ ALWAYS use {{current_year}} web searches for current prompt engineering data
+- 📋 YOU ARE A PROMPT ENGINEERING ANALYST, not content generator
+- 💬 FOCUS on prompt engineering techniques and best practices
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] continue option after prompt engineering content generation
+- 💾 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
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from step-01 are available
+- Focus on prompt engineering techniques and methodologies
+- Web search capabilities with source verification are enabled
+- May need to search for current prompt engineering research and frameworks
+
+## YOUR TASK:
+
+Conduct comprehensive prompt engineering research using current {{current_year}} web data with emphasis on techniques, frameworks, and best practices.
+
+## PROMPT ENGINEERING SEQUENCE:
+
+### 1. Begin Prompt Engineering Analysis
+
+Start with prompt engineering research approach:
+"Now I'll conduct **prompt engineering research** using current {{current_year}} web data to understand effective prompt design and optimization techniques.
+
+**Prompt Engineering Focus:**
+
+- Current prompt engineering methodologies and frameworks
+- Advanced prompting techniques and strategies
+- Prompt optimization and evaluation approaches
+- Industry best practices and case studies
+- Emerging trends in prompt engineering
+
+**Let me search for current prompt engineering research and techniques.**"
+
+### 2. Web Search for Prompt Engineering Techniques
+
+Search for current prompt engineering techniques:
+`WebSearch: "prompt engineering techniques methodologies {{current_year}}"`
+
+**Techniques focus:**
+
+- Chain-of-thought and reasoning prompts
+- Few-shot and zero-shot prompting strategies
+- Instruction following and role-based prompts
+- Multi-modal and multimodal prompting approaches
+
+### 3. Web Search for Prompt Frameworks
+
+Search for current prompt frameworks:
+`WebSearch: "prompt engineering frameworks tools {{current_year}}"`
+
+**Frameworks focus:**
+
+- Structured prompt design frameworks
+- Prompt template systems and libraries
+- Evaluation and testing frameworks
+- Industry-standard prompting methodologies
+
+### 4. Web Search for Prompt Optimization
+
+Search for current optimization approaches:
+`WebSearch: "prompt optimization evaluation {{current_year}}"`
+
+**Optimization focus:**
+
+- A/B testing and prompt improvement strategies
+- Performance metrics and evaluation criteria
+- Automated prompt optimization techniques
+- Quality assessment methodologies
+
+### 5. Generate Prompt Engineering Content
+
+Prepare prompt engineering analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Prompt Engineering Analysis
+
+### Current Prompting Techniques
+
+[Prompting techniques analysis with source citations]
+_Source: [URL with {{current_year}} prompting data]_
+
+### Structured Prompting Frameworks
+
+[Prompt frameworks analysis with source citations]
+_Source: [URL with {{current_year}} frameworks data]_
+
+### Advanced Prompting Strategies
+
+[Advanced strategies analysis with source citations]
+_Source: [URL with {{current_year}} strategies data]_
+
+### Prompt Optimization Methods
+
+[Optimization methods analysis with source citations]
+_Source: [URL with {{current_year}} optimization data]_
+
+### Industry Best Practices
+
+[Best practices analysis with source citations]
+_Source: [URL with {{current_year}} best practices data]_
+
+### Evaluation and Testing Approaches
+
+[Evaluation approaches analysis with source citations]
+_Source: [URL with {{current_year}} evaluation data]_
+
+### Emerging Trends and Innovations
+
+[Emerging trends analysis with source citations]
+_Source: [URL with {{current_year}} trends data]_
+```
+
+### 6. Present Analysis and Continue Option
+
+Show the generated prompt engineering analysis and present continue option:
+"I've completed the **prompt engineering research** using current {{current_year}} data to understand effective prompt design and optimization techniques.
+
+**Key Prompt Engineering Findings:**
+
+- Current prompting techniques and methodologies clearly mapped
+- Structured prompting frameworks and tools identified
+- Advanced prompting strategies thoroughly analyzed
+- Optimization and evaluation approaches documented
+- Industry best practices and emerging trends captured
+
+**Ready to proceed to AI interaction patterns?**
+[C] Continue - Save this to the document and move to AI interaction patterns
+
+### 7. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- Append the final content to the research document
+- Update frontmatter: `stepsCompleted: [1, 2]`
+- Load: `./step-03-ai-interaction-patterns.md`
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the research document using the structure from step 5.
+
+## SUCCESS METRICS:
+
+✅ Prompting techniques identified with current {{current_year}} citations
+✅ Structured prompting frameworks clearly documented
+✅ Advanced prompting strategies thoroughly analyzed
+✅ Optimization and evaluation approaches mapped
+✅ Industry best practices and emerging trends captured
+✅ [C] continue option presented and handled correctly
+✅ Content properly appended to document when C selected
+✅ Proper routing to AI interaction patterns step
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in prompt engineering web searches
+❌ Missing critical prompting techniques or frameworks
+❌ Not analyzing advanced prompting strategies
+❌ Incomplete optimization or evaluation approaches analysis
+❌ Not presenting [C] continue option after content generation
+❌ Appending content without user selecting 'C'
+
+## PROMPT ENGINEERING RESEARCH PROTOCOLS:
+
+- Search for academic research papers on prompt engineering
+- Research AI company blog posts and technical documentation
+- Analyze open-source prompting frameworks and libraries
+- Study prompt engineering case studies and success stories
+- Research evaluation methodologies and benchmark datasets
+
+## NEXT STEP:
+
+After user selects 'C' and content is saved to document, load `./step-03-ai-interaction-patterns.md` to focus on AI interaction patterns and conversational design.
+
+Remember: Always emphasize current {{current_year}} prompt engineering data and rigorous source verification!
diff --git a/src/modules/bmm/workflows/1-analysis/research/deep-prompt-steps/step-03-ai-interaction-patterns.md b/src/modules/bmm/workflows/1-analysis/research/deep-prompt-steps/step-03-ai-interaction-patterns.md
new file mode 100644
index 00000000..0fd91767
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/research/deep-prompt-steps/step-03-ai-interaction-patterns.md
@@ -0,0 +1,195 @@
+# Deep Prompt Research Step 3: AI Interaction Patterns
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+- ✅ ALWAYS use {{current_year}} web searches for current AI interaction data
+- 📋 YOU ARE AN AI INTERACTION DESIGN ANALYST, not content generator
+- 💬 FOCUS on conversational AI patterns and user experience design
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] continue option after AI interaction patterns content generation
+- 💾 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
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- Focus on AI interaction patterns and conversational design principles
+- Web search capabilities with source verification are enabled
+- May need to search for current conversational AI research and patterns
+
+## YOUR TASK:
+
+Conduct comprehensive AI interaction patterns research using current {{current_year}} web data with emphasis on conversational design and user experience patterns.
+
+## AI INTERACTION PATTERNS SEQUENCE:
+
+### 1. Begin AI Interaction Patterns Analysis
+
+Start with interaction patterns research approach:
+"Now I'll focus on **AI interaction patterns and conversational design** using current {{current_year}} data to understand effective human-AI interaction approaches.
+
+**AI Interaction Patterns Focus:**
+
+- Conversational design principles and patterns
+- User experience (UX) considerations for AI interactions
+- Multi-turn dialogue management strategies
+- Error handling and recovery patterns
+- Personalization and adaptation approaches
+
+**Let me search for current AI interaction patterns and research.**"
+
+### 2. Web Search for Conversational Design
+
+Search for current conversational design patterns:
+`WebSearch: "conversational AI design patterns principles {{current_year}}"`
+
+**Design focus:**
+
+- Conversational flow design and management
+- Dialogue structure and turn-taking patterns
+- Context management and memory strategies
+- Natural language understanding and generation patterns
+
+### 3. Web Search for AI User Experience
+
+Search for current AI UX patterns:
+`WebSearch: "AI user experience design patterns {{current_year}}"`
+
+**UX focus:**
+
+- Interface design for AI-powered applications
+- Trust and transparency in AI interactions
+- User onboarding and education patterns
+- Feedback and improvement mechanisms
+
+### 4. Web Search for Error Handling Patterns
+
+Search for current error handling approaches:
+`WebSearch: "AI error handling recovery patterns {{current_year}}"`
+
+**Error focus:**
+
+- Graceful failure and recovery strategies
+- Ambiguity resolution and clarification requests
+- Confidence communication and uncertainty management
+- Fallback mechanisms and escalation patterns
+
+### 5. Generate AI Interaction Patterns Content
+
+Prepare interaction patterns analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## AI Interaction Patterns and Design
+
+### Conversational Design Principles
+
+[Conversational design analysis with source citations]
+_Source: [URL with {{current_year}} conversational data]_
+
+### Multi-Turn Dialogue Management
+
+[Dialogue management analysis with source citations]
+_Source: [URL with {{current_year}} dialogue data]_
+
+### User Experience Patterns
+
+[UX patterns analysis with source citations]
+_Source: [URL with {{current_year}} UX data]_
+
+### Error Handling and Recovery
+
+[Error handling analysis with source citations]
+_Source: [URL with {{current_year}} error handling data]_
+
+### Context Management Strategies
+
+[Context management analysis with source citations]
+_Source: [URL with {{current_year}} context data]_
+
+### Personalization and Adaptation
+
+[Personalization analysis with source citations]
+_Source: [URL with {{current_year}} personalization data]_
+
+### Trust and Transparency Patterns
+
+[Trust patterns analysis with source citations]
+_Source: [URL with {{current_year}} trust data]_
+
+### Performance Optimization Strategies
+
+[Performance optimization analysis with source citations]
+_Source: [URL with {{current_year}} performance data]_
+```
+
+### 6. Present Analysis and Continue Option
+
+Show the generated AI interaction patterns and present continue option:
+"I've completed the **AI interaction patterns research** using current {{current_year}} data to understand effective human-AI interaction approaches.
+
+**Key Interaction Findings:**
+
+- Conversational design principles and patterns clearly mapped
+- Multi-turn dialogue management strategies thoroughly analyzed
+- User experience patterns and considerations documented
+- Error handling and recovery approaches identified
+- Trust, transparency, and personalization patterns captured
+
+**Ready to proceed to workflow integration?**
+[C] Continue - Save this to the document and move to workflow integration
+
+### 7. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- Append the final content to the research document
+- Update frontmatter: `stepsCompleted: [1, 2, 3]`
+- Load: `./step-04-workflow-integration.md`
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the research document using the structure from step 5.
+
+## SUCCESS METRICS:
+
+✅ Conversational design principles identified with current {{current_year}} citations
+✅ Multi-turn dialogue management strategies clearly documented
+✅ User experience patterns thoroughly analyzed
+✅ Error handling and recovery approaches mapped
+✅ Trust, transparency, and personalization patterns captured
+✅ [C] continue option presented and handled correctly
+✅ Content properly appended to document when C selected
+✅ Proper routing to workflow integration step
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in AI interaction web searches
+❌ Missing critical conversational design principles
+❌ Not analyzing user experience patterns thoroughly
+❌ Incomplete error handling or recovery patterns analysis
+❌ Not presenting [C] continue option after content generation
+❌ Appending content without user selecting 'C'
+
+## AI INTERACTION RESEARCH PROTOCOLS:
+
+- Search for human-computer interaction (HCI) research on AI interfaces
+- Research conversational AI case studies and best practices
+- Analyze industry guidelines for AI-powered product design
+- Study user research and usability testing methodologies for AI
+- Research accessibility and inclusive design patterns for AI interactions
+
+## NEXT STEP:
+
+After user selects 'C' and content is saved to document, load `./step-04-workflow-integration.md` to focus on workflow integration and implementation strategies.
+
+Remember: Always emphasize current {{current_year}} AI interaction data and rigorous source verification!
diff --git a/src/modules/bmm/workflows/1-analysis/research/deep-prompt-steps/step-04-workflow-integration.md b/src/modules/bmm/workflows/1-analysis/research/deep-prompt-steps/step-04-workflow-integration.md
new file mode 100644
index 00000000..9c1fc4c0
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/research/deep-prompt-steps/step-04-workflow-integration.md
@@ -0,0 +1,235 @@
+# Deep Prompt Research Step 4: Workflow Integration
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+- ✅ ALWAYS use {{current_year}} web searches for current workflow integration data
+- 📋 YOU ARE A WORKFLOW INTEGRATION SPECIALIST, not content generator
+- 💬 FOCUS on practical implementation and workflow design strategies
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] complete option after workflow integration content generation
+- 💾 ONLY save when user chooses C (Complete)
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before completing workflow
+- 🚫 FORBIDDEN to complete workflow until C is selected
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- Focus on workflow integration and practical implementation strategies
+- Web search capabilities with source verification are enabled
+- This is the final step in the deep prompt research workflow
+
+## YOUR TASK:
+
+Conduct comprehensive workflow integration research using current {{current_year}} web data with emphasis on practical implementation and workflow design strategies.
+
+## WORKFLOW INTEGRATION SEQUENCE:
+
+### 1. Begin Workflow Integration Analysis
+
+Start with workflow integration research approach:
+"Now I'll complete our deep prompt research with **workflow integration and implementation strategies** using current {{current_year}} data.
+
+**Workflow Integration Focus:**
+
+- Integration patterns for AI-powered workflows
+- Implementation strategies and best practices
+- Workflow orchestration and automation approaches
+- Testing and validation methodologies
+- Monitoring and optimization techniques
+
+**Let me search for current workflow integration and implementation strategies.**"
+
+### 2. Web Search for Workflow Integration Patterns
+
+Search for current integration patterns:
+`WebSearch: "AI workflow integration patterns best practices {{current_year}}"`
+
+**Integration focus:**
+
+- System architecture integration approaches
+- API design and integration patterns
+- Data flow and processing workflows
+- Microservices and distributed system integration
+
+### 3. Web Search for Implementation Strategies
+
+Search for current implementation approaches:
+`WebSearch: "AI implementation strategies deployment {{current_year}}"`
+
+**Implementation focus:**
+
+- Development and deployment workflows
+- Testing and quality assurance practices
+- Change management and adoption strategies
+- Performance monitoring and optimization
+
+### 4. Web Search for Workflow Automation
+
+Search for current automation approaches:
+`WebSearch: "workflow automation orchestration AI {{current_year}}"`
+
+**Automation focus:**
+
+- Low-code and no-code workflow platforms
+- Process automation and optimization techniques
+- Integration with existing business processes
+- Scalability and reliability considerations
+
+### 5. Generate Workflow Integration Content
+
+Prepare integration analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Workflow Integration and Implementation
+
+### Integration Architecture Patterns
+
+[Integration patterns analysis with source citations]
+_Source: [URL with {{current_year}} integration data]_
+
+### Implementation Strategies
+
+[Implementation strategies analysis with source citations]
+_Source: [URL with {{current_year}} implementation data]_
+
+### Workflow Orchestration Approaches
+
+[Orchestration analysis with source citations]
+_Source: [URL with {{current_year}} orchestration data]_
+
+### Testing and Validation Frameworks
+
+[Testing frameworks analysis with source citations]
+_Source: [URL with {{current_year}} testing data]_
+
+### Monitoring and Optimization
+
+[Monitoring optimization analysis with source citations]
+_Source: [URL with {{current_year}} monitoring data]_
+
+### Change Management and Adoption
+
+[Change management analysis with source citations]
+_Source: [URL with {{current_year}} change management data]_
+
+### Scalability and Performance Considerations
+
+[Scalability analysis with source citations]
+_Source: [URL with {{current_year}} scalability data]_
+
+### Security and Compliance Integration
+
+[Security integration analysis with source citations]
+_Source: [URL with {{current_year}} security data]_
+
+## Deep Prompt Research Recommendations
+
+### Implementation Roadmap
+
+[Implementation roadmap recommendations]
+
+### Technology Stack Recommendations
+
+[Technology stack suggestions]
+
+### Best Practices and Guidelines
+
+[Best practices recommendations]
+
+### Success Metrics and Evaluation
+
+[Success measurement framework]
+```
+
+### 6. Present Analysis and Complete Option
+
+Show the generated workflow integration and present complete option:
+"I've completed the **workflow integration and implementation research** using current {{current_year}} data, finalizing our comprehensive deep prompt research.
+
+**Integration Highlights:**
+
+- Integration architecture patterns and approaches documented
+- Implementation strategies and best practices thoroughly analyzed
+- Workflow orchestration and automation approaches identified
+- Testing, monitoring, and optimization strategies provided
+- Change management and adoption considerations captured
+
+**This completes our deep prompt research covering:**
+
+- Prompt engineering techniques and methodologies
+- AI interaction patterns and design principles
+- Workflow integration and implementation strategies
+- Practical recommendations and implementation roadmap
+
+**Ready to complete the deep prompt research report?**
+[C] Complete Research - Save final document and conclude
+
+### 7. Handle Complete Selection
+
+#### If 'C' (Complete Research):
+
+- Append the final content to the research document
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
+- Complete the deep prompt research workflow
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the research document using the structure from step 5.
+
+## SUCCESS METRICS:
+
+✅ Integration architecture patterns identified with current {{current_year}} citations
+✅ Implementation strategies clearly documented
+✅ Workflow orchestration approaches thoroughly analyzed
+✅ Testing and monitoring frameworks mapped
+✅ Change management and scalability considerations captured
+✅ [C] complete option presented and handled correctly
+✅ Content properly appended to document when C selected
+✅ Deep prompt research workflow completed successfully
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in workflow integration web searches
+❌ Missing critical integration patterns or implementation strategies
+❌ Not providing practical implementation guidance
+❌ Incomplete testing or monitoring frameworks analysis
+❌ Not presenting completion option for research workflow
+❌ Appending content without user selecting 'C'
+
+## WORKFLOW INTEGRATION RESEARCH PROTOCOLS:
+
+- Search for enterprise architecture integration patterns
+- Research DevOps and CI/CD practices for AI-powered applications
+- Analyze workflow automation platforms and case studies
+- Study change management methodologies for AI implementation
+- Research monitoring and observability best practices for AI workflows
+
+## DEEP PROMPT RESEARCH WORKFLOW COMPLETION:
+
+When 'C' is selected:
+
+- All deep prompt research steps completed
+- Comprehensive deep prompt research document generated
+- All sections appended with source citations
+- Deep prompt research workflow status updated
+- Final implementation recommendations provided to user
+
+## NEXT STEPS:
+
+Deep prompt research workflow complete. User may:
+
+- Use deep prompt research to inform AI-powered workflow design
+- Conduct additional research on specific AI technologies
+- Combine deep prompt research with other research types for comprehensive insights
+- Move forward with AI implementation based on research insights
+
+Congratulations on completing comprehensive deep prompt research with current {{current_year}} data! 🎉
diff --git a/src/modules/bmm/workflows/1-analysis/research/domain-steps/step-01-init.md b/src/modules/bmm/workflows/1-analysis/research/domain-steps/step-01-init.md
new file mode 100644
index 00000000..ba35a3ad
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/research/domain-steps/step-01-init.md
@@ -0,0 +1,194 @@
+# Domain Research Step 1: Initialization and Context
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+- ✅ ALWAYS treat this as collaborative research partnership
+- 📋 YOU ARE A RESEARCH FACILITATOR, not content generator
+- 💬 FOCUS on domain/industry research with current web data
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis before taking any action
+- ⚠️ Present A/P/C menu after initial context generation
+- 💾 ONLY save when user chooses C (Continue)
+- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
+- 🚫 FORBIDDEN to load next step until C is selected
+
+## COLLABORATION MENUS (A/P/C):
+
+This step will generate content and present choices:
+
+- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper domain insights
+- **P (Party Mode)**: Bring multiple perspectives to validate domain 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
+- 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-01-discovery are available
+- Research type = "domain" is already set
+- Focus on industry/domain analysis with web research
+- Web search capabilities with {{current_year}} data are enabled
+
+## YOUR TASK:
+
+Initialize domain research, gather context, and establish research scope with current web data.
+
+## DOMAIN RESEARCH INITIALIZATION:
+
+### 1. Confirm Domain Research Direction
+
+Begin with domain-specific positioning:
+"I'll guide you through **domain research** using current {{current_year}} web data with rigorous source verification.
+
+**Domain Research Focus:**
+
+- Industry analysis and market dynamics
+- Regulatory requirements and compliance standards
+- Technology trends and innovation patterns
+- Competitive landscape within the domain
+- Supply chain and ecosystem analysis
+
+**What specific domain or industry are we researching?**
+
+### 2. Establish Research Context
+
+Gather domain-specific details:
+
+#### Context Questions:
+
+- "What specific domain/industry are we focusing on?"
+- "Are there particular segments or sub-domains we should examine?"
+- "What aspects of this domain are most critical for your project?"
+- "Are there specific regulatory or compliance concerns?"
+- "What time horizon should we consider (current state, future trends)?"
+
+### 3. Define Research Scope
+
+Collaboratively establish research boundaries:
+
+#### Scope Definition:
+
+- "How broad should our domain analysis be?"
+- "Are we looking at global markets or specific regions?"
+- "Should we focus on current state or include future projections?"
+- "What depth of research do you need (overview vs deep dive)?"
+
+### 4. Generate Research Overview Content
+
+Prepare initial content to append to the document:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Research Overview
+
+### Research Objectives
+
+[Domain research objectives based on conversation]
+
+### Scope and Boundaries
+
+[Research scope definition based on conversation]
+
+### Research Methodology
+
+[Research methodology approach with {{current_year}} web data emphasis]
+
+### Source Verification Standards
+
+[Source verification approach and confidence level framework]
+```
+
+### 5. Present Content and Menu
+
+Show the generated overview and present choices:
+"I've established the foundation for our **domain research** with {{current_year}} web data and rigorous source verification.
+
+**Here's what I'll add to the document:**
+
+[Show the complete markdown content from step 4]
+
+**Research Standards:**
+
+- Always using {{current_year}} web searches
+- Requiring multiple sources for critical claims
+- Citing all factual claims with URLs
+- Presenting conflicting information when sources disagree
+- Using confidence levels for uncertain data
+
+**What would you like to do?**
+[A] Advanced Elicitation - Let's deepen our understanding of the domain scope
+[P] Party Mode - Bring different perspectives on domain research approach
+[C] Continue - Save this to the document and begin domain analysis
+
+### 6. Handle Menu Selection
+
+#### If 'A' (Advanced Elicitation):
+
+- Execute advanced-elicitation.xml with current domain overview
+- Process enhanced domain insights that come back
+- Ask user: "Accept these improvements to the research overview? (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):
+
+- Execute party-mode workflow with current domain overview
+- Process collaborative domain expertise and additional insights
+- Ask user: "Accept these changes to the research overview? (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):
+
+- Append the final content to the research document
+- Update frontmatter: `stepsCompleted: [1]`
+- Load: `./step-02-domain-analysis.md`
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the research document using the structure from step 4.
+
+## SUCCESS METRICS:
+
+✅ Domain research scope clearly defined and confirmed
+✅ Research methodology established with {{current_year}} emphasis
+✅ Source verification standards communicated and documented
+✅ A/P/C menu presented and handled correctly
+✅ Content properly appended to document when C selected
+✅ Proper routing to next domain research step
+
+## FAILURE MODES:
+
+❌ Not confirming specific domain/industry to research
+❌ Missing research scope boundaries
+❌ Not emphasizing {{current_year}} web data requirement
+❌ Not communicating source verification protocols
+❌ Not presenting A/P/C menu after content generation
+❌ Appending content without user selecting 'C'
+
+## WEB RESEARCH READINESS:
+
+This step prepares for web research by:
+
+- Establishing {{current_year}} search query framework
+- Defining source verification protocols
+- Setting confidence level methodology
+- Preparing for multiple source verification of critical claims
+
+## NEXT STEP:
+
+After user selects 'C' and content is saved to document, load `./step-02-domain-analysis.md` to begin web-based domain analysis with current {{current_year}} data.
+
+Remember: Always emphasize current {{current_year}} data and rigorous source verification in domain research!
diff --git a/src/modules/bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md b/src/modules/bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md
new file mode 100644
index 00000000..8afd1323
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md
@@ -0,0 +1,187 @@
+# Domain Research Step 2: Industry Analysis
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+- ✅ ALWAYS use {{current_year}} web searches for current data
+- 📋 YOU ARE A RESEARCH ANALYST, not content generator
+- 💬 FOCUS on industry/domain analysis with verified sources
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] continue option after domain analysis content generation
+- 💾 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
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from step-01 are available
+- Research type = "domain" is already set
+- Focus on industry/domain web research with {{current_year}} data
+- Web search capabilities with source verification are enabled
+
+## YOUR TASK:
+
+Conduct comprehensive domain/industry analysis using current {{current_year}} web data with rigorous source verification.
+
+## DOMAIN ANALYSIS SEQUENCE:
+
+### 1. Begin Domain Analysis
+
+Start with web research approach:
+"Now I'll conduct comprehensive domain research using current {{current_year}} web data with rigorous source verification.
+
+**Domain Analysis Focus:**
+
+- Industry size, growth, and market dynamics
+- Technology trends and innovation patterns
+- Regulatory landscape and compliance requirements
+- Key players and competitive ecosystem
+- Supply chain and business model evolution
+
+**Let me search for current {{current_year}} data on [domain/industry].**"
+
+### 2. Web Search for Industry Overview
+
+Search for current industry information:
+`WebSearch: "[domain/industry] market size growth {{current_year}}"`
+
+**Analysis approach:**
+
+- Look for recent market research reports and industry analyses
+- Identify market size, growth rates, and trends
+- Find authoritative sources (market research firms, industry associations)
+- Note conflicting information from different sources
+
+### 3. Web Search for Technology Trends
+
+Search for current technology developments:
+`WebSearch: "[domain/industry] technology trends {{current_year}}"`
+
+**Technology focus:**
+
+- Emerging technologies and innovation patterns
+- Digital transformation impacts
+- Automation and efficiency improvements
+- New business models enabled by technology
+
+### 4. Web Search for Regulatory Landscape
+
+Search for current regulatory requirements:
+`WebSearch: "[domain/industry] regulations compliance {{current_year}}"`
+
+**Regulatory focus:**
+
+- Current regulations and compliance requirements
+- Recent changes or upcoming regulations
+- Industry standards and best practices
+- Regional or jurisdictional differences
+
+### 5. Generate Domain Analysis Content
+
+Prepare analysis content with source citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Industry Overview
+
+### Market Size and Growth
+
+[Market size and growth data with source citations]
+_Source: [URL with {{current_year}} data]_
+
+### Technology Trends
+
+[Technology trends analysis with source citations]
+_Source: [URL with {{current_year}} data]_
+
+### Regulatory Landscape
+
+[Regulatory analysis with source citations]
+_Source: [URL with {{current_year}} data]_
+
+### Key Players and Ecosystem
+
+[Key players analysis with source citations]
+_Source: [URL with {{current_year}} data]_
+
+### Growth Drivers and Challenges
+
+[Growth drivers and challenges with source citations]
+_Source: [URL with {{current_year}} data]_
+```
+
+### 6. Present Analysis and Continue Option
+
+Show the generated analysis and present continue option:
+"I've completed the **domain/industry analysis** using current {{current_year}} web data with rigorous source verification.
+
+**Key Findings:**
+
+- Multiple sources verified for critical market data
+- Conflicting information noted where sources disagree
+- Confidence levels applied to uncertain data
+- All factual claims include source citations
+
+**Ready to proceed to regulatory focus?**
+[C] Continue - Save this to the document and move to regulatory focus
+
+### 7. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- Append the final content to the research document
+- Update frontmatter: `stepsCompleted: [1, 2]`
+- Load: `./step-03-regulatory-focus.md`
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the research document using the structure from step 5.
+
+## SUCCESS METRICS:
+
+✅ Industry size and growth data with current {{current_year}} citations
+✅ Technology trends identified with current developments
+✅ Regulatory landscape analysis with current requirements
+✅ Key players and ecosystem mapped with current data
+✅ [C] continue option presented and handled correctly
+✅ Content properly appended to document when C selected
+✅ Web searches properly structured with {{current_year}} parameter
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in web search queries
+❌ Not requiring source citations for factual claims
+❌ Not presenting conflicting information when sources disagree
+❌ Not applying confidence levels to uncertain data
+❌ Not presenting [C] continue option after content generation
+❌ Appending content without user selecting 'C'
+
+## WEB RESEARCH PROTOCOLS:
+
+All web searches must:
+
+- Include {{current_year}} for current data
+- Require multiple sources for critical claims
+- Present conflicting information when found
+- Include source URLs for all factual claims
+- Apply confidence levels appropriately
+
+## SOURCE VERIFICATION:
+
+- Always cite URLs for web search results
+- Use authoritative sources (market research firms, industry associations)
+- Note data currency and potential limitations
+- Present multiple perspectives when sources conflict
+
+## NEXT STEP:
+
+After user selects 'C' and content is saved to document, load `./step-03-regulatory-focus.md` to focus on specific regulatory and compliance requirements.
+
+Remember: Always emphasize current {{current_year}} data and rigorous source verification in domain research!
diff --git a/src/modules/bmm/workflows/1-analysis/research/domain-steps/step-03-regulatory-focus.md b/src/modules/bmm/workflows/1-analysis/research/domain-steps/step-03-regulatory-focus.md
new file mode 100644
index 00000000..12f77b47
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/research/domain-steps/step-03-regulatory-focus.md
@@ -0,0 +1,195 @@
+# Domain Research Step 3: Regulatory Focus
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+- ✅ ALWAYS use {{current_year}} web searches for current regulatory data
+- 📋 YOU ARE A REGULATORY ANALYST, not content generator
+- 💬 FOCUS on compliance requirements and regulatory landscape
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] continue option after regulatory content generation
+- 💾 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
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- Focus on regulatory and compliance requirements for the domain
+- Web search capabilities with source verification are enabled
+- May need to search for specific regulations and compliance frameworks
+
+## YOUR TASK:
+
+Conduct focused regulatory and compliance analysis using current {{current_year}} web data with emphasis on requirements that impact your project.
+
+## REGULATORY FOCUS SEQUENCE:
+
+### 1. Begin Regulatory Analysis
+
+Start with regulatory research approach:
+"Now I'll focus on **regulatory and compliance requirements** that impact the [domain/industry] using current {{current_year}} data.
+
+**Regulatory Focus Areas:**
+
+- Specific regulations and compliance frameworks
+- Industry standards and best practices
+- Licensing and certification requirements
+- Data protection and privacy regulations
+- Environmental and safety requirements
+
+**Let me search for current regulatory requirements.**"
+
+### 2. Web Search for Specific Regulations
+
+Search for current regulatory information:
+`WebSearch: "[domain/industry] regulations compliance requirements {{current_year}}"`
+
+**Regulatory focus:**
+
+- Specific regulations applicable to the domain
+- Compliance frameworks and standards
+- Recent regulatory changes or updates
+- Enforcement agencies and oversight bodies
+
+### 3. Web Search for Industry Standards
+
+Search for current industry standards:
+`WebSearch: "[domain/industry] standards best practices {{current_year}}"`
+
+**Standards focus:**
+
+- Industry-specific technical standards
+- Best practices and guidelines
+- Certification requirements
+- Quality assurance frameworks
+
+### 4. Web Search for Data Privacy Requirements
+
+Search for current privacy regulations:
+`WebSearch: "data privacy regulations [domain/industry] {{current_year}}"`
+
+**Privacy focus:**
+
+- GDPR, CCPA, and other data protection laws
+- Industry-specific privacy requirements
+- Data governance and security standards
+- User consent and data handling requirements
+
+### 5. Generate Regulatory Analysis Content
+
+Prepare regulatory content with source citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Regulatory Requirements
+
+### Applicable Regulations
+
+[Specific regulations analysis with source citations]
+_Source: [URL with {{current_year}} regulatory data]_
+
+### Industry Standards and Best Practices
+
+[Industry standards analysis with source citations]
+_Source: [URL with {{current_year}} standards data]_
+
+### Compliance Frameworks
+
+[Compliance frameworks analysis with source citations]
+_Source: [URL with {{current_year}} compliance data]_
+
+### Data Protection and Privacy
+
+[Privacy requirements analysis with source citations]
+_Source: [URL with {{current_year}} privacy data]_
+
+### Licensing and Certification
+
+[Licensing requirements analysis with source citations]
+_Source: [URL with {{current_year}} licensing data]_
+
+### Implementation Considerations
+
+[Practical implementation considerations with source citations]
+_Source: [URL with {{current_year}} implementation data]_
+
+### Risk Assessment
+
+[Regulatory and compliance risk assessment]
+```
+
+### 6. Present Analysis and Continue Option
+
+Show the generated regulatory analysis and present continue option:
+"I've completed the **regulatory requirements analysis** focusing on compliance requirements that impact your [domain/industry] project.
+
+**Key Regulatory Findings:**
+
+- Specific regulations and frameworks identified
+- Industry standards and best practices mapped
+- Compliance requirements clearly documented
+- Implementation considerations provided
+- Risk assessment completed
+
+**Ready to proceed to technical trends?**
+[C] Continue - Save this to the document and move to technical trends
+
+### 7. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- Append the final content to the research document
+- Update frontmatter: `stepsCompleted: [1, 2, 3]`
+- Load: `./step-04-technical-trends.md`
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the research document using the structure from step 5.
+
+## SUCCESS METRICS:
+
+✅ Applicable regulations identified with current {{current_year}} citations
+✅ Industry standards and best practices documented
+✅ Compliance frameworks clearly mapped
+✅ Data protection requirements analyzed
+✅ Implementation considerations provided
+✅ [C] continue option presented and handled correctly
+✅ Content properly appended to document when C selected
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in regulatory web searches
+❌ Missing critical regulatory requirements for the domain
+❌ Not providing implementation considerations for compliance
+❌ Not completing risk assessment for regulatory compliance
+❌ Not presenting [C] continue option after content generation
+❌ Appending content without user selecting 'C'
+
+## REGULATORY RESEARCH PROTOCOLS:
+
+- Search for specific regulations by name and number
+- Identify regulatory bodies and enforcement agencies
+- Research recent regulatory changes and updates
+- Map industry standards to regulatory requirements
+- Consider regional and jurisdictional differences
+
+## SOURCE VERIFICATION:
+
+- Always cite regulatory agency websites
+- Use official government and industry association sources
+- Note effective dates and implementation timelines
+- Present compliance requirement levels and obligations
+
+## NEXT STEP:
+
+After user selects 'C' and content is saved to document, load `./step-04-technical-trends.md` to analyze technical trends and innovations in the domain.
+
+Remember: Always emphasize current {{current_year}} regulatory data and practical implementation considerations!
diff --git a/src/modules/bmm/workflows/1-analysis/research/domain-steps/step-04-technical-trends.md b/src/modules/bmm/workflows/1-analysis/research/domain-steps/step-04-technical-trends.md
new file mode 100644
index 00000000..cba9f98f
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/research/domain-steps/step-04-technical-trends.md
@@ -0,0 +1,220 @@
+# Domain Research Step 4: Technical Trends
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+- ✅ ALWAYS use {{current_year}} web searches for current technical data
+- 📋 YOU ARE A TECHNOLOGY ANALYST, not content generator
+- 💬 FOCUS on emerging technologies and innovation patterns
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] complete option after technical trends content generation
+- 💾 ONLY save when user chooses C (Complete)
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before completing workflow
+- 🚫 FORBIDDEN to complete workflow until C is selected
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- Focus on emerging technologies and innovation patterns in the domain
+- Web search capabilities with source verification are enabled
+- This is the final step in the domain research workflow
+
+## YOUR TASK:
+
+Conduct comprehensive technical trends analysis using current {{current_year}} web data with emphasis on innovations and emerging technologies impacting the domain.
+
+## TECHNICAL TRENDS SEQUENCE:
+
+### 1. Begin Technical Trends Analysis
+
+Start with technology research approach:
+"Now I'll complete our domain research with **technical trends and emerging technologies** analysis using current {{current_year}} data.
+
+**Technical Trends Focus:**
+
+- Emerging technologies and innovations
+- Digital transformation impacts
+- Automation and efficiency improvements
+- New business models enabled by technology
+- Future technology projections and roadmaps
+
+**Let me search for current technology developments.**"
+
+### 2. Web Search for Emerging Technologies
+
+Search for current technology information:
+`WebSearch: "[domain/industry] emerging technologies innovations {{current_year}}"`
+
+**Technology focus:**
+
+- AI, machine learning, and automation impacts
+- Digital transformation trends
+- New technologies disrupting the industry
+- Innovation patterns and breakthrough developments
+
+### 3. Web Search for Digital Transformation
+
+Search for current transformation trends:
+`WebSearch: "[domain/industry] digital transformation {{current_year}}"`
+
+**Transformation focus:**
+
+- Digital adoption trends and rates
+- Business model evolution
+- Customer experience innovations
+- Operational efficiency improvements
+
+### 4. Web Search for Future Outlook
+
+Search for future projections:
+`WebSearch: "[domain/industry] future outlook {{current_year}} 2025"`
+
+**Future focus:**
+
+- Technology roadmaps and projections
+- Market evolution predictions
+- Innovation pipelines and R&D trends
+- Long-term industry transformation
+
+### 5. Generate Technical Trends Content
+
+Prepare technical analysis with source citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Technical Trends and Innovation
+
+### Emerging Technologies
+
+[Emerging technologies analysis with source citations]
+_Source: [URL with {{current_year}} technology data]_
+
+### Digital Transformation
+
+[Digital transformation analysis with source citations]
+_Source: [URL with {{current_year}} transformation data]_
+
+### Innovation Patterns
+
+[Innovation patterns analysis with source citations]
+_Source: [URL with {{current_year}} innovation data]_
+
+### Future Outlook
+
+[Future outlook and projections with source citations]
+_Source: [URL with {{current_year}} outlook data]_
+
+### Implementation Opportunities
+
+[Implementation opportunity analysis with source citations]
+_Source: [URL with {{current_year}} implementation data]_
+
+### Challenges and Risks
+
+[Challenges and risks assessment with source citations]
+_Source: [URL with {{current_year}} risk data]_
+
+## Recommendations
+
+### Technology Adoption Strategy
+
+[Technology adoption recommendations]
+
+### Innovation Roadmap
+
+[Innovation roadmap suggestions]
+
+### Risk Mitigation
+
+[Risk mitigation strategies]
+```
+
+### 6. Present Analysis and Complete Option
+
+Show the generated technical analysis and present complete option:
+"I've completed the **technical trends and innovation analysis** using current {{current_year}} data, finalizing our comprehensive domain research.
+
+**Technical Highlights:**
+
+- Emerging technologies and innovations identified
+- Digital transformation trends mapped
+- Future outlook and projections analyzed
+- Implementation opportunities and challenges documented
+- Practical recommendations provided
+
+**This completes our domain research covering:**
+
+- Industry overview and market dynamics
+- Regulatory requirements and compliance
+- Technical trends and innovations
+- Strategic recommendations for your project
+
+**Ready to complete the domain research report?**
+[C] Complete Research - Save final document and conclude
+
+### 7. Handle Complete Selection
+
+#### If 'C' (Complete Research):
+
+- Append the final content to the research document
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
+- Complete the domain research workflow
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the research document using the structure from step 5.
+
+## SUCCESS METRICS:
+
+✅ Emerging technologies identified with current {{current_year}} data
+✅ Digital transformation trends clearly documented
+✅ Future outlook and projections analyzed
+✅ Implementation opportunities and challenges mapped
+✅ Strategic recommendations provided
+✅ [C] complete option presented and handled correctly
+✅ Content properly appended to document when C selected
+✅ Research workflow completed successfully
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in technology web searches
+❌ Missing critical emerging technologies in the domain
+❌ Not providing practical implementation recommendations
+❌ Not completing strategic recommendations
+❌ Not presenting completion option for research workflow
+❌ Appending content without user selecting 'C'
+
+## TECHNICAL RESEARCH PROTOCOLS:
+
+- Search for cutting-edge technologies and innovations
+- Identify disruption patterns and game-changers
+- Research technology adoption timelines and barriers
+- Consider regional technology variations
+- Analyze competitive technological advantages
+
+## RESEARCH WORKFLOW COMPLETION:
+
+When 'C' is selected:
+
+- All domain research steps completed
+- Comprehensive research document generated
+- All sections appended with source citations
+- Research workflow status updated
+- Final recommendations provided to user
+
+## NEXT STEPS:
+
+Research workflow complete. User may:
+
+- Use the domain research to inform other workflows (PRD, architecture, etc.)
+- Conduct additional research on specific topics if needed
+- Move forward with product development based on research insights
+
+Congratulations on completing comprehensive domain research with current {{current_year}} data! 🎉
diff --git a/src/modules/bmm/workflows/1-analysis/research/instructions-deep-prompt.md b/src/modules/bmm/workflows/1-analysis/research/instructions-deep-prompt.md
deleted file mode 100644
index 602dc74e..00000000
--- a/src/modules/bmm/workflows/1-analysis/research/instructions-deep-prompt.md
+++ /dev/null
@@ -1,438 +0,0 @@
-# Deep Research Prompt Generator Instructions
-
-The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml
-You MUST have already loaded and processed: {installed_path}/workflow.yaml
-This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}
-This workflow generates structured research prompts optimized for AI platforms
-Based on {{current_year}} best practices from ChatGPT, Gemini, Grok, and Claude
-Communicate all responses in {communication_language} and tailor to {user_skill_level}
-Generate all documents in {document_output_language}
-
-🚨 BUILD ANTI-HALLUCINATION INTO PROMPTS 🚨
-Generated prompts MUST instruct AI to cite sources with URLs for all factual claims
-Include validation requirements: "Cross-reference claims with at least 2 independent sources"
-Add explicit instructions: "If you cannot find reliable data, state 'No verified data found for [X]'"
-Require confidence indicators in prompts: "Mark each claim with confidence level and source quality"
-Include fact-checking instructions: "Distinguish between verified facts, analysis, and speculation"
-⚠️ CHECKPOINT PROTOCOL: After EVERY tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.
-
-
-
-
-
-Engage conversationally to understand their needs:
-
-
- "Let's craft a research prompt optimized for AI deep research tools.
-
-What topic or question do you want to investigate, and which platform are you planning to use? (ChatGPT Deep Research, Gemini, Grok, Claude Projects)"
-
-
-
- "I'll help you create a structured research prompt for AI platforms like ChatGPT Deep Research, Gemini, or Grok.
-
-These tools work best with well-structured prompts that define scope, sources, and output format.
-
-What do you want to research?"
-
-
-
- "Think of this as creating a detailed brief for an AI research assistant.
-
-Tools like ChatGPT Deep Research can spend hours searching the web and synthesizing information - but they work best when you give them clear instructions about what to look for and how to present it.
-
-What topic are you curious about?"
-
-
-
-Through conversation, discover:
-
-- **The research topic** - What they want to explore
-- **Their purpose** - Why they need this (decision-making, learning, writing, etc.)
-- **Target platform** - Which AI tool they'll use (affects prompt structure)
-- **Existing knowledge** - What they already know vs. what's uncertain
-
-Adapt your questions based on their clarity:
-
-- If they're vague → Help them sharpen the focus
-- If they're specific → Capture the details
-- If they're unsure about platform → Guide them to the best fit
-
-Don't make them fill out a form - have a real conversation.
-
-
-research_topic
-research_goal
-target_platform
-
-
-
-
-Help user define clear boundaries for focused research
-
-**Let's define the scope to ensure focused, actionable results:**
-
-**Temporal Scope** - What time period should the research cover?
-
-- Current state only (last 6-12 months)
-- Recent trends (last 2-3 years)
-- Historical context (5-10 years)
-- Future outlook (projections 3-5 years)
-- Custom date range (specify)
-
-temporal_scope
-
-**Geographic Scope** - What geographic focus?
-
-- Global
-- Regional (North America, Europe, Asia-Pacific, etc.)
-- Specific countries
-- US-focused
-- Other (specify)
-
-geographic_scope
-
-**Thematic Boundaries** - Are there specific aspects to focus on or exclude?
-
-Examples:
-
-- Focus: technological innovation, regulatory changes, market dynamics
-- Exclude: historical background, unrelated adjacent markets
-
-thematic_boundaries
-
-
-
-
-Determine what types of information and sources are needed
-
-**What types of information do you need?**
-
-Select all that apply:
-
-- [ ] Quantitative data and statistics
-- [ ] Qualitative insights and expert opinions
-- [ ] Trends and patterns
-- [ ] Case studies and examples
-- [ ] Comparative analysis
-- [ ] Technical specifications
-- [ ] Regulatory and compliance information
-- [ ] Financial data
-- [ ] Academic research
-- [ ] Industry reports
-- [ ] News and current events
-
-information_types
-
-**Preferred Sources** - Any specific source types or credibility requirements?
-
-Examples:
-
-- Peer-reviewed academic journals
-- Industry analyst reports (Gartner, Forrester, IDC)
-- Government/regulatory sources
-- Financial reports and SEC filings
-- Technical documentation
-- News from major publications
-- Expert blogs and thought leadership
-- Social media and forums (with caveats)
-
-preferred_sources
-
-
-
-
-Specify desired output format for the research
-
-**Output Format** - How should the research be structured?
-
-1. Executive Summary + Detailed Sections
-2. Comparative Analysis Table
-3. Chronological Timeline
-4. SWOT Analysis Framework
-5. Problem-Solution-Impact Format
-6. Question-Answer Format
-7. Custom structure (describe)
-
-output_format
-
-**Key Sections** - What specific sections or questions should the research address?
-
-Examples for market research:
-
-- Market size and growth
-- Key players and competitive landscape
-- Trends and drivers
-- Challenges and barriers
-- Future outlook
-
-Examples for technical research:
-
-- Current state of technology
-- Alternative approaches and trade-offs
-- Best practices and patterns
-- Implementation considerations
-- Tool/framework comparison
-
-key_sections
-
-**Depth Level** - How detailed should each section be?
-
-- High-level overview (2-3 paragraphs per section)
-- Standard depth (1-2 pages per section)
-- Comprehensive (3-5 pages per section with examples)
-- Exhaustive (deep dive with all available data)
-
-depth_level
-
-
-
-
-Gather additional context to make the prompt more effective
-
-**Persona/Perspective** - Should the research take a specific viewpoint?
-
-Examples:
-
-- "Act as a venture capital analyst evaluating investment opportunities"
-- "Act as a CTO evaluating technology choices for a fintech startup"
-- "Act as an academic researcher reviewing literature"
-- "Act as a product manager assessing market opportunities"
-- No specific persona needed
-
-research_persona
-
-**Special Requirements or Constraints:**
-
-- Citation requirements (e.g., "Include source URLs for all claims")
-- Bias considerations (e.g., "Consider perspectives from both proponents and critics")
-- Recency requirements (e.g., "Prioritize sources from 2024-2025")
-- Specific keywords or technical terms to focus on
-- Any topics or angles to avoid
-
-special_requirements
-
-
-
-
-Establish how to validate findings and what follow-ups might be needed
-
-**Validation Criteria** - How should the research be validated?
-
-- Cross-reference multiple sources for key claims
-- Identify conflicting viewpoints and resolve them
-- Distinguish between facts, expert opinions, and speculation
-- Note confidence levels for different findings
-- Highlight gaps or areas needing more research
-
-validation_criteria
-
-**Follow-up Questions** - What potential follow-up questions should be anticipated?
-
-Examples:
-
-- "If cost data is unclear, drill deeper into pricing models"
-- "If regulatory landscape is complex, create separate analysis"
-- "If multiple technical approaches exist, create comparison matrix"
-
-follow_up_strategy
-
-
-
-
-Synthesize all inputs into platform-optimized research prompt
-
-Generate the deep research prompt using best practices for the target platform
-
-**Prompt Structure Best Practices:**
-
-1. **Clear Title/Question** (specific, focused)
-2. **Context and Goal** (why this research matters)
-3. **Scope Definition** (boundaries and constraints)
-4. **Information Requirements** (what types of data/insights)
-5. **Output Structure** (format and sections)
-6. **Source Guidance** (preferred sources and credibility)
-7. **Validation Requirements** (how to verify findings)
-8. **Keywords** (precise technical terms, brand names)
-
-Generate prompt following this structure
-
-deep_research_prompt
-
-Review the generated prompt:
-
-- [a] Accept and save
-- [e] Edit sections
-- [r] Refine with additional context
-- [o] Optimize for different platform
-
-
- What would you like to adjust?
- Regenerate with modifications
-
-
-
-
-
-Provide platform-specific usage tips based on target platform
-
-
- **ChatGPT Deep Research Tips:**
-
-- Use clear verbs: "compare," "analyze," "synthesize," "recommend"
-- Specify keywords explicitly to guide search
-- Answer clarifying questions thoroughly (requests are more expensive)
-- You have 25-250 queries/month depending on tier
-- Review the research plan before it starts searching
-
-
-
- **Gemini Deep Research Tips:**
-
-- Keep initial prompt simple - you can adjust the research plan
-- Be specific and clear - vagueness is the enemy
-- Review and modify the multi-point research plan before it runs
-- Use follow-up questions to drill deeper or add sections
-- Available in 45+ languages globally
-
-
-
- **Grok DeepSearch Tips:**
-
-- Include date windows: "from Jan-Jun 2025"
-- Specify output format: "bullet list + citations"
-- Pair with Think Mode for reasoning
-- Use follow-up commands: "Expand on [topic]" to deepen sections
-- Verify facts when obscure sources cited
-- Free tier: 5 queries/24hrs, Premium: 30/2hrs
-
-
-
- **Claude Projects Tips:**
-
-- Use Chain of Thought prompting for complex reasoning
-- Break into sub-prompts for multi-step research (prompt chaining)
-- Add relevant documents to Project for context
-- Provide explicit instructions and examples
-- Test iteratively and refine prompts
-
-
-platform_tips
-
-
-
-
-Create a checklist for executing and evaluating the research
-
-Generate execution checklist with:
-
-**Before Running Research:**
-
-- [ ] Prompt clearly states the research question
-- [ ] Scope and boundaries are well-defined
-- [ ] Output format and structure specified
-- [ ] Keywords and technical terms included
-- [ ] Source guidance provided
-- [ ] Validation criteria clear
-
-**During Research:**
-
-- [ ] Review research plan before execution (if platform provides)
-- [ ] Answer any clarifying questions thoroughly
-- [ ] Monitor progress if platform shows reasoning process
-- [ ] Take notes on unexpected findings or gaps
-
-**After Research Completion:**
-
-- [ ] Verify key facts from multiple sources
-- [ ] Check citation credibility
-- [ ] Identify conflicting information and resolve
-- [ ] Note confidence levels for findings
-- [ ] Identify gaps requiring follow-up
-- [ ] Ask clarifying follow-up questions
-- [ ] Export/save research before query limit resets
-
-execution_checklist
-
-
-
-
-Save complete research prompt package
-
-**Your Deep Research Prompt Package is ready!**
-
-The output includes:
-
-1. **Optimized Research Prompt** - Ready to paste into AI platform
-2. **Platform-Specific Tips** - How to get the best results
-3. **Execution Checklist** - Ensure thorough research process
-4. **Follow-up Strategy** - Questions to deepen findings
-
-Save all outputs to {default_output_file}
-
-Would you like to:
-
-1. Generate a variation for a different platform
-2. Create a follow-up prompt based on hypothetical findings
-3. Generate a related research prompt
-4. Exit workflow
-
-Select option (1-4):
-
-
- Start with different platform selection
-
-
-
- Start new prompt with context from previous
-
-
-
-
-
-
- Load the FULL file: {output_folder}/bmm-workflow-status.yaml
- Find workflow_status key "research"
- ONLY write the file path as the status value - no other text, notes, or metadata
- Update workflow_status["research"] = "{output_folder}/bmm-research-deep-prompt-{{date}}.md"
- Save file, preserving ALL comments and structure including STATUS DEFINITIONS
-
-Find first non-completed workflow in workflow_status (next workflow to do)
-Determine next agent from path file based on next workflow
-
-
-
-
-
-
diff --git a/src/modules/bmm/workflows/1-analysis/research/instructions-market.md b/src/modules/bmm/workflows/1-analysis/research/instructions-market.md
deleted file mode 100644
index 067cf2ee..00000000
--- a/src/modules/bmm/workflows/1-analysis/research/instructions-market.md
+++ /dev/null
@@ -1,675 +0,0 @@
-# Market Research Workflow Instructions
-
-The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml
-You MUST have already loaded and processed: {installed_path}/workflow.yaml
-This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}
-This is a HIGHLY INTERACTIVE workflow - collaborate with user throughout, don't just gather info and disappear
-Web research is MANDATORY - use WebSearch tool with {{current_year}} for all market intelligence gathering
-Communicate all responses in {communication_language} and tailor to {user_skill_level}
-Generate all documents in {document_output_language}
-
-🚨 ANTI-HALLUCINATION PROTOCOL - MANDATORY 🚨
-NEVER invent market data - if you cannot find reliable data, explicitly state: "I could not find verified data for [X]"
-EVERY statistic, market size, growth rate, or competitive claim MUST have a cited source with URL
-For CRITICAL claims (TAM/SAM/SOM, market size, growth rates), require 2+ independent sources that agree
-When data sources conflict (e.g., different market size estimates), present ALL estimates with sources and explain variance
-Mark data confidence: [Verified - 2+ sources], [Single source - verify], [Estimated - low confidence]
-Clearly label: FACT (sourced data), ANALYSIS (your interpretation), PROJECTION (forecast/speculation)
-After each WebSearch, extract and store source URLs - include them in the report
-If a claim seems suspicious or too convenient, STOP and cross-verify with additional searches
-⚠️ CHECKPOINT PROTOCOL: After EVERY tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.
-
-
-
-
-
-
-
-Welcome {user_name} warmly. Position yourself as their collaborative research partner who will:
-
-- Gather live {{current_year}} market data
-- Share findings progressively throughout
-- Help make sense of what we discover together
-
-Ask what they're building and what market questions they need answered.
-
-
-Through natural conversation, discover:
-
-- The product/service and current stage
-- Their burning questions (what they REALLY need to know)
-- Context and urgency (fundraising? launch decision? pivot?)
-- Existing knowledge vs. uncertainties
-- Desired depth (gauge from their needs, don't ask them to choose)
-
-Adapt your approach: If uncertain → help them think it through. If detailed → dig deeper.
-
-Collaboratively define scope:
-
-- Markets/segments to focus on
-- Geographic boundaries
-- Critical questions vs. nice-to-have
-
-
-Reflect understanding back to confirm you're aligned on what matters.
-
-product_name
-product_description
-research_objectives
-research_scope
-
-
-
-Help the user precisely define the market scope
-
-Work with the user to establish:
-
-1. **Market Category Definition**
- - Primary category/industry
- - Adjacent or overlapping markets
- - Where this fits in the value chain
-
-2. **Geographic Scope**
- - Global, regional, or country-specific?
- - Primary markets vs. expansion markets
- - Regulatory considerations by region
-
-3. **Customer Segment Boundaries**
- - B2B, B2C, or B2B2C?
- - Primary vs. secondary segments
- - Segment size estimates
-
-Should we include adjacent markets in the TAM calculation? This could significantly increase market size but may be less immediately addressable.
-
-market_definition
-geographic_scope
-segment_boundaries
-
-
-
-
-This step REQUIRES WebSearch tool usage - gather CURRENT data from {{current_year}}
-Share findings as you go - make this collaborative, not a black box
-
-Let {user_name} know you're searching for current {{market_category}} market data: size, growth, analyst reports, recent trends. Tell them you'll share what you find in a few minutes and review it together.
-
-
-Conduct systematic web searches using WebSearch tool:
-
-{{market_category}} market size {{geographic_scope}} {{current_year}}
-{{market_category}} industry report Gartner Forrester IDC {{current_year}}
-{{market_category}} market growth rate CAGR forecast {{current_year}}
-{{market_category}} market trends {{current_year}}
-{{market_category}} TAM SAM market opportunity {{current_year}}
-
-
-Share findings WITH SOURCES including URLs and dates. Ask if it aligns with their expectations.
-
-CRITICAL - Validate data before proceeding:
-
-- Multiple sources with similar figures?
-- Recent sources ({{current_year}} or within 1-2 years)?
-- Credible sources (Gartner, Forrester, govt data, reputable pubs)?
-- Conflicts? Note explicitly, search for more sources, mark [Low Confidence]
-
-
-Explore surprising data points together
-
-sources_market_size
-
-
-
-Search for recent market developments:
-
-{{market_category}} news {{current_year}} funding acquisitions
-{{market_category}} recent developments {{current_year}}
-{{market_category}} regulatory changes {{current_year}}
-
-
-Share noteworthy findings:
-
-"I found some interesting recent developments:
-
-{{key_news_highlights}}
-
-Anything here surprise you or confirm what you suspected?"
-
-
-
-
-Search for authoritative sources:
-
-{{market_category}} government statistics census data {{current_year}}
-{{market_category}} academic research white papers {{current_year}}
-
-
-
-market_intelligence_raw
-key_data_points
-source_credibility_notes
-
-
-
-Calculate market sizes using multiple methodologies for triangulation
-
-Use actual data gathered in previous steps, not hypothetical numbers
-
-
-**Method 1: Top-Down Approach**
-- Start with total industry size from research
-- Apply relevant filters and segments
-- Show calculation: Industry Size × Relevant Percentage
-
-**Method 2: Bottom-Up Approach**
-
-- Number of potential customers × Average revenue per customer
-- Build from unit economics
-
-**Method 3: Value Theory Approach**
-
-- Value created × Capturable percentage
-- Based on problem severity and alternative costs
-
-Which TAM calculation method seems most credible given our data? Should we use multiple methods and triangulate?
-
-tam_calculation
-tam_methodology
-
-
-
-Calculate Serviceable Addressable Market
-
-Apply constraints to TAM:
-
-- Geographic limitations (markets you can serve)
-- Regulatory restrictions
-- Technical requirements (e.g., internet penetration)
-- Language/cultural barriers
-- Current business model limitations
-
-SAM = TAM × Serviceable Percentage
-Show the calculation with clear assumptions.
-
-sam_calculation
-
-
-
-Calculate realistic market capture
-
-Consider competitive dynamics:
-
-- Current market share of competitors
-- Your competitive advantages
-- Resource constraints
-- Time to market considerations
-- Customer acquisition capabilities
-
-Create 3 scenarios:
-
-1. Conservative (1-2% market share)
-2. Realistic (3-5% market share)
-3. Optimistic (5-10% market share)
-
-som_scenarios
-
-
-
-
-Develop detailed understanding of target customers
-
-
-For each major segment, research and define:
-
-**Demographics/Firmographics:**
-
-- Size and scale characteristics
-- Geographic distribution
-- Industry/vertical (for B2B)
-
-**Psychographics:**
-
-- Values and priorities
-- Decision-making process
-- Technology adoption patterns
-
-**Behavioral Patterns:**
-
-- Current solutions used
-- Purchasing frequency
-- Budget allocation
-
-segment*profile*{{segment_number}}
-
-
-
-Apply JTBD framework to understand customer needs
-
-For primary segment, identify:
-
-**Functional Jobs:**
-
-- Main tasks to accomplish
-- Problems to solve
-- Goals to achieve
-
-**Emotional Jobs:**
-
-- Feelings sought
-- Anxieties to avoid
-- Status desires
-
-**Social Jobs:**
-
-- How they want to be perceived
-- Group dynamics
-- Peer influences
-
-Would you like to conduct actual customer interviews or surveys to validate these jobs? (We can create an interview guide)
-
-jobs_to_be_done
-
-
-
-Research and estimate pricing sensitivity
-
-Analyze:
-
-- Current spending on alternatives
-- Budget allocation for this category
-- Value perception indicators
-- Price points of substitutes
-
-pricing_analysis
-
-
-
-
-Ask if they know their main competitors or if you should search for them.
-
-
-Search for competitors:
-
-{{product_category}} competitors {{geographic_scope}} {{current_year}}
-{{product_category}} alternatives comparison {{current_year}}
-top {{product_category}} companies {{current_year}}
-
-
-Present findings. Ask them to pick the 3-5 that matter most (most concerned about or curious to understand).
-
-
-
-For each competitor, search for:
-- Company overview, product features
-- Pricing model
-- Funding and recent news
-- Customer reviews and ratings
-
-Use {{current_year}} in all searches.
-
-
-Share findings with sources. Ask what jumps out and if it matches expectations.
-
-Dig deeper based on their interests
-
-competitor-analysis-{{competitor_name}}
-
-
-
-Create positioning analysis
-
-Map competitors on key dimensions:
-
-- Price vs. Value
-- Feature completeness vs. Ease of use
-- Market segment focus
-- Technology approach
-- Business model
-
-Identify:
-
-- Gaps in the market
-- Over-served areas
-- Differentiation opportunities
-
-competitive_positioning
-
-
-
-
-Apply Porter's Five Forces framework
-
-Use specific evidence from research, not generic assessments
-
-Analyze each force with concrete examples:
-
-
-Rate: [Low/Medium/High]
-- Key suppliers and dependencies
-- Switching costs
-- Concentration of suppliers
-- Forward integration threat
-
-
-
-Rate: [Low/Medium/High]
-- Customer concentration
-- Price sensitivity
-- Switching costs for customers
-- Backward integration threat
-
-
-
-Rate: [Low/Medium/High]
-- Number and strength of competitors
-- Industry growth rate
-- Exit barriers
-- Differentiation levels
-
-
-
-Rate: [Low/Medium/High]
-- Capital requirements
-- Regulatory barriers
-- Network effects
-- Brand loyalty
-
-
-
-Rate: [Low/Medium/High]
-- Alternative solutions
-- Switching costs to substitutes
-- Price-performance trade-offs
-
-
-porters_five_forces
-
-
-
-Identify trends and future market dynamics
-
-Research and analyze:
-
-**Technology Trends:**
-
-- Emerging technologies impacting market
-- Digital transformation effects
-- Automation possibilities
-
-**Social/Cultural Trends:**
-
-- Changing customer behaviors
-- Generational shifts
-- Social movements impact
-
-**Economic Trends:**
-
-- Macroeconomic factors
-- Industry-specific economics
-- Investment trends
-
-**Regulatory Trends:**
-
-- Upcoming regulations
-- Compliance requirements
-- Policy direction
-
-Should we explore any specific emerging technologies or disruptions that could reshape this market?
-
-market_trends
-future_outlook
-
-
-
-Synthesize research into strategic opportunities
-
-
-Based on all research, identify top 3-5 opportunities:
-
-For each opportunity:
-
-- Description and rationale
-- Size estimate (from SOM)
-- Resource requirements
-- Time to market
-- Risk assessment
-- Success criteria
-
-market_opportunities
-
-
-
-Develop GTM strategy based on research:
-
-**Positioning Strategy:**
-
-- Value proposition refinement
-- Differentiation approach
-- Messaging framework
-
-**Target Segment Sequencing:**
-
-- Beachhead market selection
-- Expansion sequence
-- Segment-specific approaches
-
-**Channel Strategy:**
-
-- Distribution channels
-- Partnership opportunities
-- Marketing channels
-
-**Pricing Strategy:**
-
-- Model recommendation
-- Price points
-- Value metrics
-
-gtm_strategy
-
-
-
-Identify and assess key risks:
-
-**Market Risks:**
-
-- Demand uncertainty
-- Market timing
-- Economic sensitivity
-
-**Competitive Risks:**
-
-- Competitor responses
-- New entrants
-- Technology disruption
-
-**Execution Risks:**
-
-- Resource requirements
-- Capability gaps
-- Scaling challenges
-
-For each risk: Impact (H/M/L) × Probability (H/M/L) = Risk Score
-Provide mitigation strategies.
-
-risk_assessment
-
-
-
-
-Create financial model based on market research
-
-Would you like to create a financial model with revenue projections based on the market analysis?
-
-
- Build 3-year projections:
-
-- Revenue model based on SOM scenarios
-- Customer acquisition projections
-- Unit economics
-- Break-even analysis
-- Funding requirements
-
-financial_projections
-
-
-
-
-
-
-This is the last major content section - make it collaborative
-
-Review the research journey together. Share high-level summaries of market size, competitive dynamics, customer insights. Ask what stands out most - what surprised them or confirmed their thinking.
-
-Collaboratively craft the narrative:
-
-- What's the headline? (The ONE thing someone should know)
-- What are the 3-5 critical insights?
-- Recommended path forward?
-- Key risks?
-
-This should read like a strategic brief, not a data dump.
-
-
-Draft executive summary and share. Ask if it captures the essence and if anything is missing or overemphasized.
-
-executive_summary
-
-
-
-
-MANDATORY SOURCE VALIDATION - Do NOT skip this step!
-
-Before finalizing, conduct source audit:
-
-Review every major claim in the report and verify:
-
-**For Market Size Claims:**
-
-- [ ] At least 2 independent sources cited with URLs
-- [ ] Sources are from {{current_year}} or within 2 years
-- [ ] Sources are credible (Gartner, Forrester, govt data, reputable pubs)
-- [ ] Conflicting estimates are noted with all sources
-
-**For Competitive Data:**
-
-- [ ] Competitor information has source URLs
-- [ ] Pricing data is current and sourced
-- [ ] Funding data is verified with dates
-- [ ] Customer reviews/ratings have source links
-
-**For Growth Rates and Projections:**
-
-- [ ] CAGR and forecast data are sourced
-- [ ] Methodology is explained or linked
-- [ ] Multiple analyst estimates are compared if available
-
-**For Customer Insights:**
-
-- [ ] Persona data is based on real research (cited)
-- [ ] Survey/interview data has sample size and source
-- [ ] Behavioral claims are backed by studies/data
-
-
-Count and document source quality:
-
-- Total sources cited: {{count_all_sources}}
-- High confidence (2+ sources): {{high_confidence_claims}}
-- Single source (needs verification): {{single_source_claims}}
-- Uncertain/speculative: {{low_confidence_claims}}
-
-If {{single_source_claims}} or {{low_confidence_claims}} is high, consider additional research.
-
-
-Compile full report with ALL sources properly referenced:
-
-Generate the complete market research report using the template:
-
-- Ensure every statistic has inline citation: [Source: Company, Year, URL]
-- Populate all {{sources_*}} template variables
-- Include confidence levels for major claims
-- Add References section with full source list
-
-
-Present source quality summary to user:
-
-"I've completed the research with {{count_all_sources}} total sources:
-
-- {{high_confidence_claims}} claims verified with multiple sources
-- {{single_source_claims}} claims from single sources (marked for verification)
-- {{low_confidence_claims}} claims with low confidence or speculation
-
-Would you like me to strengthen any areas with additional research?"
-
-
-Would you like to review any specific sections before finalizing? Are there any additional analyses you'd like to include?
-
-Return to refine opportunities
-
-final_report_ready
-source_audit_complete
-
-
-
-Would you like to include detailed appendices with calculations, full competitor profiles, or raw research data?
-
-
- Create appendices with:
-
-- Detailed TAM/SAM/SOM calculations
-- Full competitor profiles
-- Customer interview notes
-- Data sources and methodology
-- Financial model details
-- Glossary of terms
-
-appendices
-
-
-
-
-
-
- Load the FULL file: {output_folder}/bmm-workflow-status.yaml
- Find workflow_status key "research"
- ONLY write the file path as the status value - no other text, notes, or metadata
- Update workflow_status["research"] = "{output_folder}/bmm-research-{{research_mode}}-{{date}}.md"
- Save file, preserving ALL comments and structure including STATUS DEFINITIONS
-
-Find first non-completed workflow in workflow_status (next workflow to do)
-Determine next agent from path file based on next workflow
-
-
-
-
-
-
diff --git a/src/modules/bmm/workflows/1-analysis/research/instructions-router.md b/src/modules/bmm/workflows/1-analysis/research/instructions-router.md
deleted file mode 100644
index e62c382e..00000000
--- a/src/modules/bmm/workflows/1-analysis/research/instructions-router.md
+++ /dev/null
@@ -1,134 +0,0 @@
-# Research Workflow Router Instructions
-
-The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml
-You MUST have already loaded and processed: {installed_path}/workflow.yaml
-Communicate in {communication_language}, generate documents in {document_output_language}
-Web research is ENABLED - always use current {{current_year}} data
-
-🚨 ANTI-HALLUCINATION PROTOCOL - MANDATORY 🚨
-NEVER present information without a verified source - if you cannot find a source, say "I could not find reliable data on this"
-ALWAYS cite sources with URLs when presenting data, statistics, or factual claims
-REQUIRE at least 2 independent sources for critical claims (market size, growth rates, competitive data)
-When sources conflict, PRESENT BOTH views and note the discrepancy - do NOT pick one arbitrarily
-Flag any data you are uncertain about with confidence levels: [High Confidence], [Medium Confidence], [Low Confidence - verify]
-Distinguish clearly between: FACTS (from sources), ANALYSIS (your interpretation), and SPECULATION (educated guesses)
-When using WebSearch results, ALWAYS extract and include the source URL for every claim
-⚠️ CHECKPOINT PROTOCOL: After EVERY tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.
-
-
-
-
-
-This is a ROUTER that directs to specialized research instruction sets
-
-
-Check if {output_folder}/bmm-workflow-status.yaml exists
-
-
-
- Set standalone_mode = true
-
-
-
- Load the FULL file: {output_folder}/bmm-workflow-status.yaml
- Parse workflow_status section
- Check status of "research" workflow
- Get project_level from YAML metadata
- Find first non-completed workflow (next expected workflow)
- Pass status context to loaded instruction set for final update
-
-
-
- Re-running will create a new research report. Continue? (y/n)
-
-
- Exit workflow
-
-
-
-
-
-
- Continue with Research anyway? (y/n)
-
-
- Exit workflow
-
-
-
-Set standalone_mode = false
-
-
-
-
-
-Welcome {user_name} warmly. Position yourself as their research partner who uses live {{current_year}} web data. Ask what they're looking to understand or research.
-
-Listen and collaboratively identify the research type based on what they describe:
-
-- Market/Business questions → Market Research
-- Competitor questions → Competitive Intelligence
-- Customer questions → User Research
-- Technology questions → Technical Research
-- Industry questions → Domain Research
-- Creating research prompts for AI platforms → Deep Research Prompt Generator
-
-Confirm your understanding of what type would be most helpful and what it will produce.
-
-
-Capture {{research_type}} and {{research_mode}}
-
-research_type_discovery
-
-
-
-
-Based on user selection, load the appropriate instruction set
-
-
- Set research_mode = "market"
- LOAD: {installed_path}/instructions-market.md
- Continue with market research workflow
-
-
-
- Set research_mode = "deep-prompt"
- LOAD: {installed_path}/instructions-deep-prompt.md
- Continue with deep research prompt generation
-
-
-
- Set research_mode = "technical"
- LOAD: {installed_path}/instructions-technical.md
- Continue with technical research workflow
-
-
-
-
- Set research_mode = "competitive"
- This will use market research workflow with competitive focus
- LOAD: {installed_path}/instructions-market.md
- Pass mode="competitive" to focus on competitive intelligence
-
-
-
-
- Set research_mode = "user"
- This will use market research workflow with user research focus
- LOAD: {installed_path}/instructions-market.md
- Pass mode="user" to focus on customer insights
-
-
-
-
- Set research_mode = "domain"
- This will use market research workflow with domain focus
- LOAD: {installed_path}/instructions-market.md
- Pass mode="domain" to focus on industry/domain analysis
-
-
-The loaded instruction set will continue from here with full context of the {research_type}
-
-
-
-
diff --git a/src/modules/bmm/workflows/1-analysis/research/instructions-technical.md b/src/modules/bmm/workflows/1-analysis/research/instructions-technical.md
deleted file mode 100644
index fc22a1ac..00000000
--- a/src/modules/bmm/workflows/1-analysis/research/instructions-technical.md
+++ /dev/null
@@ -1,534 +0,0 @@
-# Technical/Architecture Research Instructions
-
-The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml
-You MUST have already loaded and processed: {installed_path}/workflow.yaml
-This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}
-This is a HIGHLY INTERACTIVE workflow - make technical decisions WITH user, not FOR them
-Web research is MANDATORY - use WebSearch tool with {{current_year}} for current version info and trends
-ALWAYS verify current versions - NEVER use hardcoded or outdated version numbers
-Communicate all responses in {communication_language} and tailor to {user_skill_level}
-Generate all documents in {document_output_language}
-
-🚨 ANTI-HALLUCINATION PROTOCOL - MANDATORY 🚨
-NEVER invent version numbers, features, or technical details - ALWAYS verify with current {{current_year}} sources
-Every technical claim (version, feature, performance, compatibility) MUST have a cited source with URL
-Version numbers MUST be verified via WebSearch - do NOT rely on training data (it's outdated!)
-When comparing technologies, cite sources for each claim (performance benchmarks, community size, etc.)
-Mark confidence levels: [Verified {{current_year}} source], [Older source - verify], [Uncertain - needs verification]
-Distinguish: FACT (from official docs/sources), OPINION (from community/reviews), SPECULATION (your analysis)
-If you cannot find current information about a technology, state: "I could not find recent {{current_year}} data on [X]"
-Extract and include source URLs in all technology profiles and comparisons
-⚠️ CHECKPOINT PROTOCOL: After EVERY tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.
-
-
-
-
-
-Engage conversationally based on skill level:
-
-
- "Let's research the technical options for your decision.
-
-I'll gather current data from {{current_year}}, compare approaches, and help you think through trade-offs.
-
-What technical question are you wrestling with?"
-
-
-
- "I'll help you research and evaluate your technical options.
-
-We'll look at current technologies (using {{current_year}} data), understand the trade-offs, and figure out what fits your needs best.
-
-What technical decision are you trying to make?"
-
-
-
- "Think of this as having a technical advisor help you research your options.
-
-I'll explain what different technologies do, why you might choose one over another, and help you make an informed decision.
-
-What technical challenge brought you here?"
-
-
-
-Through conversation, understand:
-
-- **The technical question** - What they need to decide or understand
-- **The context** - Greenfield? Brownfield? Learning? Production?
-- **Current constraints** - Languages, platforms, team skills, budget
-- **What they already know** - Do they have candidates in mind?
-
-Don't interrogate - explore together. If they're unsure, help them articulate the problem.
-
-
-technical_question
-project_context
-
-
-
-
-Gather requirements and constraints that will guide the research
-
-**Let's define your technical requirements:**
-
-**Functional Requirements** - What must the technology do?
-
-Examples:
-
-- Handle 1M requests per day
-- Support real-time data processing
-- Provide full-text search capabilities
-- Enable offline-first mobile app
-- Support multi-tenancy
-
-functional_requirements
-
-**Non-Functional Requirements** - Performance, scalability, security needs?
-
-Consider:
-
-- Performance targets (latency, throughput)
-- Scalability requirements (users, data volume)
-- Reliability and availability needs
-- Security and compliance requirements
-- Maintainability and developer experience
-
-non_functional_requirements
-
-**Constraints** - What limitations or requirements exist?
-
-- Programming language preferences or requirements
-- Cloud platform (AWS, Azure, GCP, on-prem)
-- Budget constraints
-- Team expertise and skills
-- Timeline and urgency
-- Existing technology stack (if brownfield)
-- Open source vs commercial requirements
-- Licensing considerations
-
-technical_constraints
-
-
-
-
-
-MUST use WebSearch to find current options from {{current_year}}
-
-Ask if they have candidates in mind:
-
-"Do you already have specific technologies you want to compare, or should I search for the current options?"
-
-
-Great! Let's research: {{user_candidates}}
-
-Search for current leading technologies:
-
-{{technical_category}} best tools {{current_year}}
-{{technical_category}} comparison {{use_case}} {{current_year}}
-{{technical_category}} popular frameworks {{current_year}}
-state of {{technical_category}} {{current_year}}
-
-
-Share findings conversationally:
-
-"Based on current {{current_year}} data, here are the main options:
-
-{{discovered_options}}
-
-
-These are the leaders right now. Which ones make sense to evaluate for your use case?"
-
-
-
-Each of these is popular for different reasons. Let me know if you want me to explain what makes each one different."
-
-
-
-technology_options
-
-
-
-
-
-For each option, use WebSearch to gather CURRENT {{current_year}} information
-
-
-
-For {{technology_name}}, conduct comprehensive research:
-
-{{technology_name}} overview what is {{current_year}}
-{{technology_name}} latest version release notes {{current_year}}
-{{technology_name}} pros cons trade-offs {{current_year}}
-{{technology_name}} production experience real world {{current_year}}
-{{technology_name}} vs alternatives comparison {{current_year}}
-
-
-Share findings conversationally and collaboratively:
-
-"Here's what I found about {{technology_name}}:
-
-**Overview:**
-{{what_it_is_and_solves}}
-
-**Current Status ({{current_year}}):**
-{{maturity_community_release_cadence}}
-
-**Technical Characteristics:**
-
-- Architecture and design philosophy
-- Core features and capabilities
-- Performance characteristics
-- Scalability approach
-- Integration capabilities
-
-**Developer Experience:**
-
-- Learning curve
-- Documentation quality
-- Tooling ecosystem
-- Testing support
-- Debugging capabilities
-
-**Operations:**
-
-- Deployment complexity
-- Monitoring and observability
-- Operational overhead
-- Cloud provider support
-- Container/K8s compatibility
-
-**Ecosystem:**
-
-- Available libraries and plugins
-- Third-party integrations
-- Commercial support options
-- Training and educational resources
-
-**Community and Adoption:**
-
-- GitHub stars/contributors (if applicable)
-- Production usage examples
-- Case studies from similar use cases
-- Community support channels
-- Job market demand
-
-**Costs:**
-
-- Licensing model
-- Hosting/infrastructure costs
-- Support costs
-- Training costs
-- Total cost of ownership estimate
-
-tech*profile*{{option_number}}
-
-
-
-
-
-
-Create structured comparison across all options
-
-**Create comparison matrices:**
-
-Generate comparison table with key dimensions:
-
-**Comparison Dimensions:**
-
-1. **Meets Requirements** - How well does each meet functional requirements?
-2. **Performance** - Speed, latency, throughput benchmarks
-3. **Scalability** - Horizontal/vertical scaling capabilities
-4. **Complexity** - Learning curve and operational complexity
-5. **Ecosystem** - Maturity, community, libraries, tools
-6. **Cost** - Total cost of ownership
-7. **Risk** - Maturity, vendor lock-in, abandonment risk
-8. **Developer Experience** - Productivity, debugging, testing
-9. **Operations** - Deployment, monitoring, maintenance
-10. **Future-Proofing** - Roadmap, innovation, sustainability
-
-Rate each option on relevant dimensions (High/Medium/Low or 1-5 scale)
-
-comparative_analysis
-
-
-
-
-Analyze trade-offs between options
-
-**Identify key trade-offs:**
-
-For each pair of leading options, identify trade-offs:
-
-- What do you gain by choosing Option A over Option B?
-- What do you sacrifice?
-- Under what conditions would you choose one vs the other?
-
-**Decision factors by priority:**
-
-What are your top 3 decision factors?
-
-Examples:
-
-- Time to market
-- Performance
-- Developer productivity
-- Operational simplicity
-- Cost efficiency
-- Future flexibility
-- Team expertise match
-- Community and support
-
-decision_priorities
-
-Weight the comparison analysis by decision priorities
-
-weighted_analysis
-
-
-
-
-Evaluate fit for specific use case
-
-**Match technologies to your specific use case:**
-
-Based on:
-
-- Your functional and non-functional requirements
-- Your constraints (team, budget, timeline)
-- Your context (greenfield vs brownfield)
-- Your decision priorities
-
-Analyze which option(s) best fit your specific scenario.
-
-Are there any specific concerns or "must-haves" that would immediately eliminate any options?
-
-use_case_fit
-
-
-
-
-Gather production experience evidence
-
-**Search for real-world experiences:**
-
-For top 2-3 candidates:
-
-- Production war stories and lessons learned
-- Known issues and gotchas
-- Migration experiences (if replacing existing tech)
-- Performance benchmarks from real deployments
-- Team scaling experiences
-- Reddit/HackerNews discussions
-- Conference talks and blog posts from practitioners
-
-real_world_evidence
-
-
-
-
-If researching architecture patterns, provide pattern analysis
-
-Are you researching architecture patterns (microservices, event-driven, etc.)?
-
-
-
-Research and document:
-
-**Pattern Overview:**
-
-- Core principles and concepts
-- When to use vs when not to use
-- Prerequisites and foundations
-
-**Implementation Considerations:**
-
-- Technology choices for the pattern
-- Reference architectures
-- Common pitfalls and anti-patterns
-- Migration path from current state
-
-**Trade-offs:**
-
-- Benefits and drawbacks
-- Complexity vs benefits analysis
-- Team skill requirements
-- Operational overhead
-
-architecture_pattern_analysis
-
-
-
-
-
-Synthesize research into clear recommendations
-
-**Generate recommendations:**
-
-**Top Recommendation:**
-
-- Primary technology choice with rationale
-- Why it best fits your requirements and constraints
-- Key benefits for your use case
-- Risks and mitigation strategies
-
-**Alternative Options:**
-
-- Second and third choices
-- When you might choose them instead
-- Scenarios where they would be better
-
-**Implementation Roadmap:**
-
-- Proof of concept approach
-- Key decisions to make during implementation
-- Migration path (if applicable)
-- Success criteria and validation approach
-
-**Risk Mitigation:**
-
-- Identified risks and mitigation plans
-- Contingency options if primary choice doesn't work
-- Exit strategy considerations
-
-recommendations
-
-
-
-
-Create architecture decision record (ADR) template
-
-**Generate Architecture Decision Record:**
-
-Create ADR format documentation:
-
-```markdown
-# ADR-XXX: [Decision Title]
-
-## Status
-
-[Proposed | Accepted | Superseded]
-
-## Context
-
-[Technical context and problem statement]
-
-## Decision Drivers
-
-[Key factors influencing the decision]
-
-## Considered Options
-
-[Technologies/approaches evaluated]
-
-## Decision
-
-[Chosen option and rationale]
-
-## Consequences
-
-**Positive:**
-
-- [Benefits of this choice]
-
-**Negative:**
-
-- [Drawbacks and risks]
-
-**Neutral:**
-
-- [Other impacts]
-
-## Implementation Notes
-
-[Key considerations for implementation]
-
-## References
-
-[Links to research, benchmarks, case studies]
-```
-
-architecture_decision_record
-
-
-
-
-Compile complete technical research report
-
-**Your Technical Research Report includes:**
-
-1. **Executive Summary** - Key findings and recommendation
-2. **Requirements and Constraints** - What guided the research
-3. **Technology Options** - All candidates evaluated
-4. **Detailed Profiles** - Deep dive on each option
-5. **Comparative Analysis** - Side-by-side comparison
-6. **Trade-off Analysis** - Key decision factors
-7. **Real-World Evidence** - Production experiences
-8. **Recommendations** - Detailed recommendation with rationale
-9. **Architecture Decision Record** - Formal decision documentation
-10. **Next Steps** - Implementation roadmap
-
-Save complete report to {default_output_file}
-
-Would you like to:
-
-1. Deep dive into specific technology
-2. Research implementation patterns for chosen technology
-3. Generate proof-of-concept plan
-4. Create deep research prompt for ongoing investigation
-5. Exit workflow
-
-Select option (1-5):
-
-
- LOAD: {installed_path}/instructions-deep-prompt.md
- Pre-populate with technical research context
-
-
-
-
-
-
- Load the FULL file: {output_folder}/bmm-workflow-status.yaml
- Find workflow_status key "research"
- ONLY write the file path as the status value - no other text, notes, or metadata
- Update workflow_status["research"] = "{output_folder}/bmm-research-technical-{{date}}.md"
- Save file, preserving ALL comments and structure including STATUS DEFINITIONS
-
-Find first non-completed workflow in workflow_status (next workflow to do)
-Determine next agent from path file based on next workflow
-
-
-
-
-
-
diff --git a/src/modules/bmm/workflows/1-analysis/research/market-steps/step-01-init.md b/src/modules/bmm/workflows/1-analysis/research/market-steps/step-01-init.md
new file mode 100644
index 00000000..959d366d
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/research/market-steps/step-01-init.md
@@ -0,0 +1,147 @@
+# Market Research Step 1: Market Analysis
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+- ✅ ALWAYS use {{current_year}} web searches for current market data
+- 📋 YOU ARE A MARKET ANALYST, not content generator
+- 💬 FOCUS on market size, growth, and competitive analysis
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] continue option after market analysis content generation
+- 💾 ONLY save when user chooses C (Continue)
+- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
+- 🚫 FORBIDDEN to load next step until C is selected
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from main workflow discovery are available
+- Research type = "market" is already set
+- Focus on market research with current {{current_year}} data
+- Web search capabilities with source verification are enabled
+
+## YOUR TASK:
+
+Conduct comprehensive market analysis using current {{current_year}} web data with rigorous source verification.
+
+## MARKET ANALYSIS SEQUENCE:
+
+### 1. Begin Market Analysis
+
+Start with market research approach:
+"I'll conduct comprehensive **market analysis** using current {{current_year}} web data with rigorous source verification.
+
+**Market Analysis Focus:**
+
+- Market size and growth projections
+- Customer segments and demographics
+- Competitive landscape analysis
+- Pricing strategies and business models
+- Market trends and consumer behavior
+
+**Let me search for current market data.**"
+
+### 2. Generate Market Analysis Content
+
+Prepare market analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Market Analysis
+
+### Market Size and Growth
+
+[Market size and growth data with source citations]
+_Source: [URL with {{current_year}} market data]_
+
+### Customer Segments
+
+[Customer segments analysis with source citations]
+_Source: [URL with {{current_year}} segment data]_
+
+### Competitive Landscape
+
+[Competitive landscape analysis with source citations]
+_Source: [URL with {{current_year}} competitive data]_
+
+### Market Trends
+
+[Market trends analysis with source citations]
+_Source: [URL with {{current_year}} trends data]_
+
+### Pricing and Business Models
+
+[Pricing analysis with source citations]
+_Source: [URL with {{current_year}} pricing data]_
+
+### Market Opportunities
+
+[Market opportunities analysis with source citations]
+_Source: [URL with {{current_year}} opportunity data]_
+```
+
+### 3. Present Analysis and Continue Option
+
+Show the generated market analysis and present continue option:
+"I've completed the **market analysis** using current {{current_year}} web data with rigorous source verification.
+
+**Key Market Findings:**
+
+- Market size and growth projections identified
+- Customer segments clearly defined
+- Competitive landscape thoroughly analyzed
+- Market trends and opportunities documented
+
+**Ready to proceed to customer insights?**
+[C] Continue - Save this to the document and proceed to customer insights
+
+### 4. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- Append the final content to the research document
+- Update frontmatter: `stepsCompleted: [1]`
+- Load: `./step-02-customer-insights.md`
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the research document using the structure from step 2.
+
+## SUCCESS METRICS:
+
+✅ Market size and growth data with current {{current_year}} citations
+✅ Customer segments clearly identified and analyzed
+✅ Competitive landscape thoroughly mapped
+✅ Market trends and opportunities documented
+✅ [C] continue option presented and handled correctly
+✅ Content properly appended to document when C selected
+✅ Proper routing to customer insights step
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in market web searches
+❌ Missing critical market size or growth data
+❌ Not identifying key customer segments
+❌ Incomplete competitive landscape analysis
+❌ Not presenting [C] continue option after content generation
+❌ Appending content without user selecting 'C'
+
+## MARKET RESEARCH PROTOCOLS:
+
+- Search for authoritative market research reports
+- Use industry association and trade publication sources
+- Cross-reference multiple sources for critical market data
+- Note regional and demographic market variations
+- Research market validation and sizing methodologies
+
+## NEXT STEP:
+
+After user selects 'C' and content is saved to document, load `./step-02-customer-insights.md` to focus on customer behavior and insights.
+
+Remember: Always emphasize current {{current_year}} market data and rigorous source verification!
diff --git a/src/modules/bmm/workflows/1-analysis/research/market-steps/step-02-customer-insights.md b/src/modules/bmm/workflows/1-analysis/research/market-steps/step-02-customer-insights.md
new file mode 100644
index 00000000..dda0082f
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/research/market-steps/step-02-customer-insights.md
@@ -0,0 +1,154 @@
+# Market Research Step 2: Customer Insights
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+- ✅ ALWAYS use {{current_year}} web searches for current customer data
+- 📋 YOU ARE A CUSTOMER INSIGHTS ANALYST, not content generator
+- 💬 FOCUS on customer behavior and needs analysis
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] continue option after customer insights content generation
+- 💾 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
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from step-01 are available
+- Focus on customer behavior and needs analysis
+- Web search capabilities with source verification are enabled
+- May need to search for current customer behavior trends
+
+## YOUR TASK:
+
+Conduct comprehensive customer insights analysis using current {{current_year}} web data with emphasis on behavior patterns and needs.
+
+## CUSTOMER INSIGHTS SEQUENCE:
+
+### 1. Begin Customer Insights Analysis
+
+Start with customer research approach:
+"Now I'll conduct **customer insights analysis** using current {{current_year}} web data to understand customer behavior and needs.
+
+**Customer Insights Focus:**
+
+- Customer behavior patterns and preferences
+- Pain points and challenges
+- Decision-making processes
+- Customer journey mapping
+- Customer satisfaction drivers
+- Demographic and psychographic profiles
+
+**Let me search for current customer insights.**"
+
+### 2. Generate Customer Insights Content
+
+Prepare customer analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Customer Insights
+
+### Customer Behavior Patterns
+
+[Customer behavior analysis with source citations]
+_Source: [URL with {{current_year}} customer data]_
+
+### Pain Points and Challenges
+
+[Pain points analysis with source citations]
+_Source: [URL with {{current_year}} customer challenges data]_
+
+### Decision-Making Processes
+
+[Decision-making analysis with source citations]
+_Source: [URL with {{current_year}} decision process data]_
+
+### Customer Journey Mapping
+
+[Customer journey analysis with source citations]
+_Source: [URL with {{current_year}} customer journey data]_
+
+### Customer Satisfaction Drivers
+
+[Satisfaction drivers analysis with source citations]
+_Source: [URL with {{current_year}} satisfaction data]_
+
+### Demographic Profiles
+
+[Demographic profiles analysis with source citations]
+_Source: [URL with {{current_year}} demographic data]_
+
+### Psychographic Profiles
+
+[Psychographic profiles analysis with source citations]
+_Source: [URL with {{current_year}} psychographic data]_
+```
+
+### 3. Present Analysis and Continue Option
+
+Show the generated customer insights and present continue option:
+"I've completed the **customer insights analysis** using current {{current_year}} data to understand customer behavior and needs.
+
+**Key Customer Findings:**
+
+- Customer behavior patterns clearly identified
+- Pain points and challenges thoroughly documented
+- Decision-making processes mapped
+- Customer journey insights captured
+- Satisfaction and profile data analyzed
+
+**Ready to proceed to competitive analysis?**
+[C] Continue - Save this to the document and proceed to competitive analysis
+
+### 4. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- Append the final content to the research document
+- Update frontmatter: `stepsCompleted: [1, 2]`
+- Load: `./step-03-competitive-analysis.md`
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the research document using the structure from step 2.
+
+## SUCCESS METRICS:
+
+✅ Customer behavior patterns identified with current {{current_year}} citations
+✅ Pain points and challenges clearly documented
+✅ Decision-making processes thoroughly analyzed
+✅ Customer journey insights captured and mapped
+✅ Customer satisfaction drivers identified
+✅ [C] continue option presented and handled correctly
+✅ Content properly appended to document when C selected
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in customer web searches
+❌ Missing critical customer behavior patterns
+❌ Not identifying key pain points and challenges
+❌ Incomplete customer journey mapping
+❌ Not presenting [C] continue option after content generation
+❌ Appending content without user selecting 'C'
+
+## CUSTOMER RESEARCH PROTOCOLS:
+
+- Search for customer behavior studies and surveys
+- Use market research firm and industry association sources
+- Research customer experience and interaction patterns
+- Note generational and cultural customer variations
+- Research customer satisfaction methodologies
+
+## NEXT STEP:
+
+After user selects 'C' and content is saved to document, load `./step-03-competitive-analysis.md` to focus on competitive landscape analysis.
+
+Remember: Always emphasize current {{current_year}} customer data and rigorous source verification!
diff --git a/src/modules/bmm/workflows/1-analysis/research/market-steps/step-03-competitive-analysis.md b/src/modules/bmm/workflows/1-analysis/research/market-steps/step-03-competitive-analysis.md
new file mode 100644
index 00000000..c71439c2
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/research/market-steps/step-03-competitive-analysis.md
@@ -0,0 +1,168 @@
+# Market Research Step 3: Competitive Analysis
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+- ✅ ALWAYS use {{current_year}} web searches for current competitive data
+- 📋 YOU ARE A COMPETITIVE ANALYST, not content generator
+- 💬 FOCUS on competitive landscape and market positioning
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] complete option after competitive analysis content generation
+- 💾 ONLY save when user chooses C (Complete)
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before completing workflow
+- 🚫 FORBIDDEN to complete workflow until C is selected
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- Focus on competitive landscape and market positioning analysis
+- Web search capabilities with source verification are enabled
+- May need to search for specific competitor information
+
+## YOUR TASK:
+
+Conduct comprehensive competitive analysis using current {{current_year}} web data with emphasis on market positioning.
+
+## COMPETITIVE ANALYSIS SEQUENCE:
+
+### 1. Begin Competitive Analysis
+
+Start with competitive research approach:
+"Now I'll conduct **competitive analysis** using current {{current_year}} web data to understand the competitive landscape.
+
+**Competitive Analysis Focus:**
+
+- Key players and market share
+- Competitive positioning strategies
+- Strengths and weaknesses analysis
+- Market differentiation opportunities
+- Competitive threats and challenges
+
+**Let me search for current competitive information.**"
+
+### 2. Generate Competitive Analysis Content
+
+Prepare competitive analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Competitive Landscape
+
+### Key Market Players
+
+[Key players analysis with market share data]
+_Source: [URL with {{current_year}} market share data]_
+
+### Market Share Analysis
+
+[Market share analysis with source citations]
+_Source: [URL with {{current_year}} market share data]_
+
+### Competitive Positioning
+
+[Positioning analysis with source citations]
+_Source: [URL with {{current_year}} positioning data]_
+
+### Strengths and Weaknesses
+
+[SWOT analysis with source citations]
+_Source: [URL with {{current_year}} competitor analysis]_
+
+### Market Differentiation
+
+[Differentiation analysis with source citations]
+_Source: [URL with {{current_year}} differentiation data]_
+
+### Competitive Threats
+
+[Threats analysis with source citations]
+_Source: [URL with {{current_year}} threat assessment]_
+
+### Opportunities
+
+[Competitive opportunities analysis with source citations]
+_Source: [URL with {{current_year}} opportunity data]_
+```
+
+### 3. Present Analysis and Complete Option
+
+Show the generated competitive analysis and present complete option:
+"I've completed the **competitive analysis** using current {{current_year}} data to understand the competitive landscape.
+
+**Key Competitive Findings:**
+
+- Key market players and market share identified
+- Competitive positioning strategies mapped
+- Strengths and weaknesses thoroughly analyzed
+- Market differentiation opportunities identified
+- Competitive threats and challenges documented
+
+**Ready to complete the market research?**
+[C] Complete Research - Save final document and conclude
+
+### 4. Handle Complete Selection
+
+#### If 'C' (Complete Research):
+
+- Append the final content to the research document
+- Update frontmatter: `stepsCompleted: [1, 2, 3]`
+- Complete the market research workflow
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the research document using the structure from step 2.
+
+## SUCCESS METRICS:
+
+✅ Key market players identified with {{current_year}} data
+✅ Market share analysis completed with source verification
+✅ Competitive positioning strategies clearly mapped
+✅ Strengths and weaknesses thoroughly analyzed
+✅ Market differentiation opportunities identified
+✅ [C] complete option presented and handled correctly
+✅ Content properly appended to document when C selected
+✅ Market research workflow completed successfully
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in competitive web searches
+❌ Missing key market players or market share data
+❌ Incomplete competitive positioning analysis
+❌ Not identifying market differentiation opportunities
+❌ Not presenting completion option for research workflow
+❌ Appending content without user selecting 'C'
+
+## COMPETITIVE RESEARCH PROTOCOLS:
+
+- Search for industry reports and competitive intelligence
+- Use competitor company websites and annual reports
+- Research market research firm competitive analyses
+- Note competitive advantages and disadvantages
+- Search for recent market developments and disruptions
+
+## MARKET RESEARCH COMPLETION:
+
+When 'C' is selected:
+
+- All market research steps completed
+- Comprehensive market research document generated
+- All sections appended with source citations
+- Market research workflow status updated
+- Final recommendations provided to user
+
+## NEXT STEPS:
+
+Market research workflow complete. User may:
+
+- Use market research to inform product development strategies
+- Conduct additional competitive research on specific companies
+- Combine market research with other research types for comprehensive insights
+
+Congratulations on completing comprehensive market research with current {{current_year}} data! 🎉
diff --git a/src/modules/bmm/workflows/1-analysis/research/market-steps/step-04-research-completion.md b/src/modules/bmm/workflows/1-analysis/research/market-steps/step-04-research-completion.md
new file mode 100644
index 00000000..fc8c097b
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/research/market-steps/step-04-research-completion.md
@@ -0,0 +1,214 @@
+# Market Research Step 4: Research Completion
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+- ✅ ALWAYS use {{current_year}} web searches for current market data
+- 📋 YOU ARE A MARKET RESEARCH STRATEGIST, not content generator
+- 💬 FOCUS on strategic recommendations and actionable insights
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] complete option after completion content generation
+- 💾 ONLY save when user chooses C (Complete)
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before completing workflow
+- 🚫 FORBIDDEN to complete workflow until C is selected
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- Focus on strategic synthesis and actionable recommendations
+- Web search capabilities with source verification are enabled
+- This is the final step in the market research workflow
+
+## YOUR TASK:
+
+Conduct comprehensive strategic synthesis using current {{current_year}} web data with emphasis on actionable market research recommendations.
+
+## MARKET RESEARCH COMPLETION SEQUENCE:
+
+### 1. Begin Strategic Synthesis
+
+Start with strategic synthesis approach:
+"Now I'll complete our market research with **strategic synthesis and recommendations** using current {{current_year}} data.
+
+**Strategic Synthesis Focus:**
+
+- Integrated insights from market, customer, and competitive analysis
+- Strategic recommendations based on research findings
+- Market entry or expansion strategies
+- Risk assessment and mitigation approaches
+- Actionable next steps and implementation guidance
+
+**Let me search for current strategic insights and best practices.**"
+
+### 2. Web Search for Market Entry Strategies
+
+Search for current market strategies:
+`WebSearch: "market entry strategies best practices {{current_year}}"`
+
+**Strategy focus:**
+
+- Market entry timing and approaches
+- Go-to-market strategies and frameworks
+- Market positioning and differentiation tactics
+- Customer acquisition and growth strategies
+
+### 3. Web Search for Risk Assessment
+
+Search for current risk approaches:
+`WebSearch: "market research risk assessment frameworks {{current_year}}"`
+
+**Risk focus:**
+
+- Market risks and uncertainty management
+- Competitive threats and mitigation strategies
+- Regulatory and compliance risks
+- Economic and market volatility considerations
+
+### 4. Generate Strategic Synthesis Content
+
+Prepare strategic recommendations with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Strategic Synthesis and Recommendations
+
+### Key Market Insights Summary
+
+[Integrated summary of market research findings with source citations]
+_Source: [URL with {{current_year}} strategic data]_
+
+### Strategic Recommendations
+
+[Strategic recommendations based on research with source citations]
+_Source: [URL with {{current_year}} strategy data]_
+
+### Market Entry or Expansion Strategy
+
+[Market approach strategy with source citations]
+_Source: [URL with {{current_year}} market entry data]_
+
+### Competitive Positioning Strategy
+
+[Positioning recommendations with source citations]
+_Source: [URL with {{current_year}} positioning data]_
+
+### Risk Assessment and Mitigation
+
+[Risk analysis and mitigation strategies with source citations]
+_Source: [URL with {{current_year}} risk data]_
+
+### Implementation Roadmap
+
+[Actionable implementation plan with source citations]
+_Source: [URL with {{current_year}} implementation data]_
+
+### Success Metrics and KPIs
+
+[Success measurement framework with source citations]
+_Source: [URL with {{current_year}} metrics data]_
+
+## Market Research Summary
+
+### Research Methodology
+
+[Summary of research approach and sources]
+
+### Key Findings Recap
+
+[Brief recap of all research findings]
+
+### Limitations and Considerations
+
+[Research limitations and additional considerations]
+```
+
+### 5. Present Analysis and Complete Option
+
+Show the generated strategic synthesis and present complete option:
+"I've completed the **market research strategic synthesis** using current {{current_year}} data, finalizing our comprehensive market research.
+
+**Strategic Highlights:**
+
+- Integrated market insights synthesized from all research phases
+- Strategic recommendations grounded in current market data
+- Market entry and positioning strategies developed
+- Risk assessment and mitigation approaches documented
+- Actionable implementation roadmap provided
+
+**This completes our market research covering:**
+
+- Market size, growth, and dynamics analysis
+- Customer behavior and insights profiling
+- Competitive landscape and positioning analysis
+- Strategic recommendations and implementation guidance
+
+**Ready to complete the market research report?**
+[C] Complete Research - Save final document and conclude
+
+### 6. Handle Complete Selection
+
+#### If 'C' (Complete Research):
+
+- Append the final content to the research document
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
+- Complete the market research workflow
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the research document using the structure from step 4.
+
+## SUCCESS METRICS:
+
+✅ Strategic insights synthesized with current {{current_year}} citations
+✅ Strategic recommendations grounded in research findings
+✅ Market entry/positioning strategies clearly documented
+✅ Risk assessment and mitigation approaches provided
+✅ Implementation roadmap with actionable steps
+✅ [C] complete option presented and handled correctly
+✅ Content properly appended to document when C selected
+✅ Market research workflow completed successfully
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in strategic web searches
+❌ Not synthesizing insights from all research phases
+❌ Missing actionable strategic recommendations
+❌ Not providing implementation guidance
+❌ Not presenting completion option for research workflow
+❌ Appending content without user selecting 'C'
+
+## STRATEGIC RESEARCH PROTOCOLS:
+
+- Search for current market strategy frameworks and best practices
+- Research successful market entry cases and approaches
+- Identify risk management methodologies and frameworks
+- Research implementation planning and execution strategies
+- Consider market timing and readiness factors
+
+## MARKET RESEARCH WORKFLOW COMPLETION:
+
+When 'C' is selected:
+
+- All market research steps completed
+- Comprehensive market research document generated
+- All sections appended with source citations
+- Market research workflow status updated
+- Final strategic recommendations provided to user
+
+## NEXT STEPS:
+
+Market research workflow complete. User may:
+
+- Use market research to inform product development strategies
+- Conduct additional research on specific market segments
+- Combine market research with other research types for comprehensive insights
+- Move forward with product development based on market insights
+
+Congratulations on completing comprehensive market research with current {{current_year}} data! 🎉
diff --git a/src/modules/bmm/workflows/1-analysis/research/research.template.md b/src/modules/bmm/workflows/1-analysis/research/research.template.md
new file mode 100644
index 00000000..53f653f0
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/research/research.template.md
@@ -0,0 +1,16 @@
+# Research Report: {{research_type}}
+
+**Date:** {{date}}
+**Author:** {{user_name}}
+**Research Type:** {{research_type}}
+**Data Currency:** {{current_year}}
+
+---
+
+## Research Overview
+
+[Research overview and methodology will be appended here]
+
+---
+
+
diff --git a/src/modules/bmm/workflows/1-analysis/research/technical-steps/step-02-technical-overview.md b/src/modules/bmm/workflows/1-analysis/research/technical-steps/step-02-technical-overview.md
new file mode 100644
index 00000000..64151336
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/research/technical-steps/step-02-technical-overview.md
@@ -0,0 +1,185 @@
+# Technical Research Step 2: Technical Overview
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+- ✅ ALWAYS use {{current_year}} web searches for current technical data
+- 📋 YOU ARE A TECHNICAL ANALYST, not content generator
+- 💬 FOCUS on technical architecture and implementation patterns
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] continue option after technical overview content generation
+- 💾 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
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from step-01 are available
+- Focus on technical architecture and implementation landscape
+- Web search capabilities with source verification are enabled
+- May need to search for current technical trends and frameworks
+
+## YOUR TASK:
+
+Conduct comprehensive technical overview using current {{current_year}} web data with emphasis on architecture patterns and implementation approaches.
+
+## TECHNICAL OVERVIEW SEQUENCE:
+
+### 1. Begin Technical Overview
+
+Start with technical research approach:
+"Now I'll conduct **technical overview analysis** using current {{current_year}} web data to understand the technical landscape for [technology/domain].
+
+**Technical Overview Focus:**
+
+- Current technical architecture patterns and frameworks
+- Implementation approaches and best practices
+- Technology stack evolution and trends
+- Integration patterns and interoperability
+- Performance and scalability considerations
+
+**Let me search for current technical landscape information.**"
+
+### 2. Web Search for Technical Architecture
+
+Search for current architecture patterns:
+`WebSearch: "[technology/domain] architecture patterns frameworks {{current_year}}"`
+
+**Architecture focus:**
+
+- Current architectural patterns and design principles
+- Frameworks and platforms commonly used
+- Microservices, monolith, and hybrid approaches
+- Cloud-native and edge computing patterns
+
+### 3. Web Search for Implementation Approaches
+
+Search for current implementation practices:
+`WebSearch: "[technology/domain] implementation best practices {{current_year}}"`
+
+**Implementation focus:**
+
+- Development methodologies and approaches
+- Code organization and structure patterns
+- Testing and quality assurance practices
+- Deployment and operations strategies
+
+### 4. Web Search for Technology Stack Trends
+
+Search for current technology trends:
+`WebSearch: "[technology/domain] technology stack trends {{current_year}}"`
+
+**Stack focus:**
+
+- Programming languages and frameworks popularity
+- Database and storage technologies
+- APIs and communication protocols
+- Development tools and platforms
+
+### 5. Generate Technical Overview Content
+
+Prepare technical analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Technical Overview
+
+### Current Architecture Patterns
+
+[Architecture patterns analysis with source citations]
+_Source: [URL with {{current_year}} architecture data]_
+
+### Implementation Approaches
+
+[Implementation approaches analysis with source citations]
+_Source: [URL with {{current_year}} implementation data]_
+
+### Technology Stack Evolution
+
+[Technology stack analysis with source citations]
+_Source: [URL with {{current_year}} technology data]_
+
+### Integration and Interoperability
+
+[Integration patterns analysis with source citations]
+_Source: [URL with {{current_year}} integration data]_
+
+### Performance and Scalability Patterns
+
+[Performance patterns analysis with source citations]
+_Source: [URL with {{current_year}} performance data]_
+
+### Development and Operations Practices
+
+[DevOps practices analysis with source citations]
+_Source: [URL with {{current_year}} DevOps data]_
+```
+
+### 6. Present Analysis and Continue Option
+
+Show the generated technical overview and present continue option:
+"I've completed the **technical overview analysis** using current {{current_year}} data to understand the technical landscape.
+
+**Key Technical Findings:**
+
+- Current architecture patterns and frameworks identified
+- Implementation approaches and best practices mapped
+- Technology stack evolution and trends documented
+- Integration patterns and interoperability analyzed
+- Performance and scalability considerations captured
+
+**Ready to proceed to architectural patterns?**
+[C] Continue - Save this to the document and move to architectural patterns
+
+### 7. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- Append the final content to the research document
+- Update frontmatter: `stepsCompleted: [1, 2]`
+- Load: `./step-03-architectural-patterns.md`
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the research document using the structure from step 5.
+
+## SUCCESS METRICS:
+
+✅ Architecture patterns identified with current {{current_year}} citations
+✅ Implementation approaches clearly documented
+✅ Technology stack evolution thoroughly analyzed
+✅ Integration patterns and interoperability mapped
+✅ Performance and scalability considerations captured
+✅ [C] continue option presented and handled correctly
+✅ Content properly appended to document when C selected
+✅ Proper routing to architectural patterns step
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in technical web searches
+❌ Missing critical architecture patterns or frameworks
+❌ Not identifying current implementation best practices
+❌ Incomplete technology stack evolution analysis
+❌ Not presenting [C] continue option after content generation
+❌ Appending content without user selecting 'C'
+
+## TECHNICAL RESEARCH PROTOCOLS:
+
+- Search for technical documentation and architecture guides
+- Use industry technical publications and conference proceedings
+- Research open-source projects and their architectures
+- Note technology adoption patterns and migration trends
+- Research performance benchmarking and optimization techniques
+
+## NEXT STEP:
+
+After user selects 'C' and content is saved to document, load `./step-03-architectural-patterns.md` to focus on specific architectural patterns and design decisions.
+
+Remember: Always emphasize current {{current_year}} technical data and rigorous source verification!
diff --git a/src/modules/bmm/workflows/1-analysis/research/technical-steps/step-03-architectural-patterns.md b/src/modules/bmm/workflows/1-analysis/research/technical-steps/step-03-architectural-patterns.md
new file mode 100644
index 00000000..7355a9ad
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/research/technical-steps/step-03-architectural-patterns.md
@@ -0,0 +1,190 @@
+# Technical Research Step 3: Architectural Patterns
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+- ✅ ALWAYS use {{current_year}} web searches for current architectural data
+- 📋 YOU ARE A SYSTEMS ARCHITECT, not content generator
+- 💬 FOCUS on architectural patterns and design decisions
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] continue option after architectural patterns content generation
+- 💾 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
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- Focus on architectural patterns and design decisions
+- Web search capabilities with source verification are enabled
+- May need to search for specific architectural frameworks and patterns
+
+## YOUR TASK:
+
+Conduct comprehensive architectural patterns analysis using current {{current_year}} web data with emphasis on design decisions and implementation approaches.
+
+## ARCHITECTURAL PATTERNS SEQUENCE:
+
+### 1. Begin Architectural Patterns Analysis
+
+Start with architectural research approach:
+"Now I'll focus on **architectural patterns and design decisions** using current {{current_year}} data to understand effective architecture approaches for [technology/domain].
+
+**Architectural Patterns Focus:**
+
+- System architecture patterns and their trade-offs
+- Design principles and best practices
+- Scalability and maintainability considerations
+- Integration and communication patterns
+- Security and performance architectural considerations
+
+**Let me search for current architectural patterns and approaches.**"
+
+### 2. Web Search for System Architecture Patterns
+
+Search for current architecture patterns:
+`WebSearch: "system architecture patterns best practices {{current_year}}"`
+
+**Architecture focus:**
+
+- Microservices, monolithic, and serverless patterns
+- Event-driven and reactive architectures
+- Domain-driven design patterns
+- Cloud-native and edge architecture patterns
+
+### 3. Web Search for Design Principles
+
+Search for current design principles:
+`WebSearch: "software design principles patterns {{current_year}}"`
+
+**Design focus:**
+
+- SOLID principles and their application
+- Clean architecture and hexagonal architecture
+- API design and GraphQL vs REST patterns
+- Database design and data architecture patterns
+
+### 4. Web Search for Scalability Patterns
+
+Search for current scalability approaches:
+`WebSearch: "scalability architecture patterns {{current_year}}"`
+
+**Scalability focus:**
+
+- Horizontal vs vertical scaling patterns
+- Load balancing and caching strategies
+- Distributed systems and consensus patterns
+- Performance optimization techniques
+
+### 5. Generate Architectural Patterns Content
+
+Prepare architectural analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Architectural Patterns and Design
+
+### System Architecture Patterns
+
+[System architecture patterns analysis with source citations]
+_Source: [URL with {{current_year}} architecture data]_
+
+### Design Principles and Best Practices
+
+[Design principles analysis with source citations]
+_Source: [URL with {{current_year}} design data]_
+
+### Scalability and Performance Patterns
+
+[Scalability patterns analysis with source citations]
+_Source: [URL with {{current_year}} scalability data]_
+
+### Integration and Communication Patterns
+
+[Integration patterns analysis with source citations]
+_Source: [URL with {{current_year}} integration data]_
+
+### Security Architecture Patterns
+
+[Security patterns analysis with source citations]
+_Source: [URL with {{current_year}} security data]_
+
+### Data Architecture Patterns
+
+[Data architecture analysis with source citations]
+_Source: [URL with {{current_year}} data architecture data]_
+
+### Deployment and Operations Architecture
+
+[Deployment architecture analysis with source citations]
+_Source: [URL with {{current_year}} deployment data]_
+```
+
+### 6. Present Analysis and Continue Option
+
+Show the generated architectural patterns and present continue option:
+"I've completed the **architectural patterns analysis** using current {{current_year}} data to understand effective architecture approaches.
+
+**Key Architectural Findings:**
+
+- System architecture patterns and trade-offs clearly mapped
+- Design principles and best practices thoroughly documented
+- Scalability and performance patterns identified
+- Integration and communication patterns analyzed
+- Security and data architecture considerations captured
+
+**Ready to proceed to implementation research?**
+[C] Continue - Save this to the document and move to implementation research
+
+### 7. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- Append the final content to the research document
+- Update frontmatter: `stepsCompleted: [1, 2, 3]`
+- Load: `./step-04-implementation-research.md`
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the research document using the structure from step 5.
+
+## SUCCESS METRICS:
+
+✅ System architecture patterns identified with current {{current_year}} citations
+✅ Design principles clearly documented and analyzed
+✅ Scalability and performance patterns thoroughly mapped
+✅ Integration and communication patterns captured
+✅ Security and data architecture considerations analyzed
+✅ [C] continue option presented and handled correctly
+✅ Content properly appended to document when C selected
+✅ Proper routing to implementation research step
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in architectural web searches
+❌ Missing critical system architecture patterns
+❌ Not analyzing design trade-offs and considerations
+❌ Incomplete scalability or performance patterns analysis
+❌ Not presenting [C] continue option after content generation
+❌ Appending content without user selecting 'C'
+
+## ARCHITECTURAL RESEARCH PROTOCOLS:
+
+- Search for architecture documentation and pattern catalogs
+- Use architectural conference proceedings and case studies
+- Research successful system architectures and their evolution
+- Note architectural decision records (ADRs) and rationales
+- Research architecture assessment and evaluation frameworks
+
+## NEXT STEP:
+
+After user selects 'C' and content is saved to document, load `./step-04-implementation-research.md` to focus on implementation approaches and technology adoption.
+
+Remember: Always emphasize current {{current_year}} architectural data and rigorous source verification!
diff --git a/src/modules/bmm/workflows/1-analysis/research/technical-steps/step-04-implementation-research.md b/src/modules/bmm/workflows/1-analysis/research/technical-steps/step-04-implementation-research.md
new file mode 100644
index 00000000..af6be3cc
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/research/technical-steps/step-04-implementation-research.md
@@ -0,0 +1,230 @@
+# Technical Research Step 4: Implementation Research
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+- ✅ ALWAYS use {{current_year}} web searches for current implementation data
+- 📋 YOU ARE AN IMPLEMENTATION ENGINEER, not content generator
+- 💬 FOCUS on implementation approaches and technology adoption
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] complete option after implementation research content generation
+- 💾 ONLY save when user chooses C (Complete)
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before completing workflow
+- 🚫 FORBIDDEN to complete workflow until C is selected
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- Focus on implementation approaches and technology adoption strategies
+- Web search capabilities with source verification are enabled
+- This is the final step in the technical research workflow
+
+## YOUR TASK:
+
+Conduct comprehensive implementation research using current {{current_year}} web data with emphasis on practical implementation approaches and technology adoption.
+
+## IMPLEMENTATION RESEARCH SEQUENCE:
+
+### 1. Begin Implementation Research
+
+Start with implementation research approach:
+"Now I'll complete our technical research with **implementation approaches and technology adoption** analysis using current {{current_year}} data.
+
+**Implementation Research Focus:**
+
+- Technology adoption strategies and migration patterns
+- Development workflows and tooling ecosystems
+- Testing, deployment, and operational practices
+- Team organization and skill requirements
+- Cost optimization and resource management
+
+**Let me search for current implementation and adoption strategies.**"
+
+### 2. Web Search for Technology Adoption
+
+Search for current adoption strategies:
+`WebSearch: "technology adoption strategies migration {{current_year}}"`
+
+**Adoption focus:**
+
+- Technology migration patterns and approaches
+- Gradual adoption vs big bang strategies
+- Legacy system modernization approaches
+- Vendor evaluation and selection criteria
+
+### 3. Web Search for Development Workflows
+
+Search for current development practices:
+`WebSearch: "software development workflows tooling {{current_year}}"`
+
+**Workflow focus:**
+
+- CI/CD pipelines and automation tools
+- Code quality and review processes
+- Testing strategies and frameworks
+- Collaboration and communication tools
+
+### 4. Web Search for Operational Excellence
+
+Search for current operational practices:
+`WebSearch: "DevOps operations best practices {{current_year}}"`
+
+**Operations focus:**
+
+- Monitoring and observability practices
+- Incident response and disaster recovery
+- Infrastructure as code and automation
+- Security operations and compliance automation
+
+### 5. Generate Implementation Research Content
+
+Prepare implementation analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Implementation Approaches and Technology Adoption
+
+### Technology Adoption Strategies
+
+[Technology adoption analysis with source citations]
+_Source: [URL with {{current_year}} adoption data]_
+
+### Development Workflows and Tooling
+
+[Development workflows analysis with source citations]
+_Source: [URL with {{current_year}} development data]_
+
+### Testing and Quality Assurance
+
+[Testing approaches analysis with source citations]
+_Source: [URL with {{current_year}} testing data]_
+
+### Deployment and Operations Practices
+
+[Deployment practices analysis with source citations]
+_Source: [URL with {{current_year}} deployment data]_
+
+### Team Organization and Skills
+
+[Team organization analysis with source citations]
+_Source: [URL with {{current_year}} team data]_
+
+### Cost Optimization and Resource Management
+
+[Cost optimization analysis with source citations]
+_Source: [URL with {{current_year}} optimization data]_
+
+### Risk Assessment and Mitigation
+
+[Risk mitigation analysis with source citations]
+_Source: [URL with {{current_year}} risk data]_
+
+## Technical Research Recommendations
+
+### Implementation Roadmap
+
+[Implementation roadmap recommendations]
+
+### Technology Stack Recommendations
+
+[Technology stack suggestions]
+
+### Skill Development Requirements
+
+[Skill development recommendations]
+
+### Success Metrics and KPIs
+
+[Success measurement framework]
+```
+
+### 6. Present Analysis and Complete Option
+
+Show the generated implementation research and present complete option:
+"I've completed the **implementation research and technology adoption** analysis using current {{current_year}} data, finalizing our comprehensive technical research.
+
+**Implementation Highlights:**
+
+- Technology adoption strategies and migration patterns documented
+- Development workflows and tooling ecosystems analyzed
+- Testing, deployment, and operational practices mapped
+- Team organization and skill requirements identified
+- Cost optimization and resource management strategies provided
+
+**This completes our technical research covering:**
+
+- Technical overview and landscape analysis
+- Architectural patterns and design decisions
+- Implementation approaches and technology adoption
+- Practical recommendations and implementation roadmap
+
+**Ready to complete the technical research report?**
+[C] Complete Research - Save final document and conclude
+
+### 7. Handle Complete Selection
+
+#### If 'C' (Complete Research):
+
+- Append the final content to the research document
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
+- Complete the technical research workflow
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the research document using the structure from step 5.
+
+## SUCCESS METRICS:
+
+✅ Technology adoption strategies identified with current {{current_year}} citations
+✅ Development workflows and tooling thoroughly analyzed
+✅ Testing and deployment practices clearly documented
+✅ Team organization and skill requirements mapped
+✅ Cost optimization and risk mitigation strategies provided
+✅ [C] complete option presented and handled correctly
+✅ Content properly appended to document when C selected
+✅ Technical research workflow completed successfully
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in implementation web searches
+❌ Missing critical technology adoption strategies
+❌ Not providing practical implementation guidance
+❌ Incomplete development workflows or operational practices analysis
+❌ Not presenting completion option for research workflow
+❌ Appending content without user selecting 'C'
+
+## IMPLEMENTATION RESEARCH PROTOCOLS:
+
+- Search for implementation case studies and success stories
+- Research technology migration patterns and lessons learned
+- Identify common implementation challenges and solutions
+- Research development tooling ecosystem evaluations
+- Analyze operational excellence frameworks and maturity models
+
+## TECHNICAL RESEARCH WORKFLOW COMPLETION:
+
+When 'C' is selected:
+
+- All technical research steps completed
+- Comprehensive technical research document generated
+- All sections appended with source citations
+- Technical research workflow status updated
+- Final implementation recommendations provided to user
+
+## NEXT STEPS:
+
+Technical research workflow complete. User may:
+
+- Use technical research to inform architecture decisions
+- Conduct additional research on specific technologies
+- Combine technical research with other research types for comprehensive insights
+- Move forward with implementation based on technical insights
+
+Congratulations on completing comprehensive technical research with current {{current_year}} data! 🎉
diff --git a/src/modules/bmm/workflows/1-analysis/research/template-deep-prompt.md b/src/modules/bmm/workflows/1-analysis/research/template-deep-prompt.md
deleted file mode 100644
index 18f97d14..00000000
--- a/src/modules/bmm/workflows/1-analysis/research/template-deep-prompt.md
+++ /dev/null
@@ -1,94 +0,0 @@
-# Deep Research Prompt
-
-**Generated:** {{date}}
-**Created by:** {{user_name}}
-**Target Platform:** {{target_platform}}
-
----
-
-## Research Prompt (Ready to Use)
-
-### Research Question
-
-{{research_topic}}
-
-### Research Goal and Context
-
-**Objective:** {{research_goal}}
-
-**Context:**
-{{research_persona}}
-
-### Scope and Boundaries
-
-**Temporal Scope:** {{temporal_scope}}
-
-**Geographic Scope:** {{geographic_scope}}
-
-**Thematic Focus:**
-{{thematic_boundaries}}
-
-### Information Requirements
-
-**Types of Information Needed:**
-{{information_types}}
-
-**Preferred Sources:**
-{{preferred_sources}}
-
-### Output Structure
-
-**Format:** {{output_format}}
-
-**Required Sections:**
-{{key_sections}}
-
-**Depth Level:** {{depth_level}}
-
-### Research Methodology
-
-**Keywords and Technical Terms:**
-{{research_keywords}}
-
-**Special Requirements:**
-{{special_requirements}}
-
-**Validation Criteria:**
-{{validation_criteria}}
-
-### Follow-up Strategy
-
-{{follow_up_strategy}}
-
----
-
-## Complete Research Prompt (Copy and Paste)
-
-```
-{{deep_research_prompt}}
-```
-
----
-
-## Platform-Specific Usage Tips
-
-{{platform_tips}}
-
----
-
-## Research Execution Checklist
-
-{{execution_checklist}}
-
----
-
-## Metadata
-
-**Workflow:** BMad Research Workflow - Deep Research Prompt Generator v2.0
-**Generated:** {{date}}
-**Research Type:** Deep Research Prompt
-**Platform:** {{target_platform}}
-
----
-
-_This research prompt was generated using the BMad Method Research Workflow, incorporating best practices from ChatGPT Deep Research, Gemini Deep Research, Grok DeepSearch, and Claude Projects (2025)._
diff --git a/src/modules/bmm/workflows/1-analysis/research/template-market.md b/src/modules/bmm/workflows/1-analysis/research/template-market.md
deleted file mode 100644
index ddc033f8..00000000
--- a/src/modules/bmm/workflows/1-analysis/research/template-market.md
+++ /dev/null
@@ -1,347 +0,0 @@
-# Market Research Report: {{product_name}}
-
-**Date:** {{date}}
-**Prepared by:** {{user_name}}
-**Research Depth:** {{research_depth}}
-
----
-
-## Executive Summary
-
-{{executive_summary}}
-
-### Key Market Metrics
-
-- **Total Addressable Market (TAM):** {{tam_calculation}}
-- **Serviceable Addressable Market (SAM):** {{sam_calculation}}
-- **Serviceable Obtainable Market (SOM):** {{som_scenarios}}
-
-### Critical Success Factors
-
-{{key_success_factors}}
-
----
-
-## 1. Research Objectives and Methodology
-
-### Research Objectives
-
-{{research_objectives}}
-
-### Scope and Boundaries
-
-- **Product/Service:** {{product_description}}
-- **Market Definition:** {{market_definition}}
-- **Geographic Scope:** {{geographic_scope}}
-- **Customer Segments:** {{segment_boundaries}}
-
-### Research Methodology
-
-{{research_methodology}}
-
-### Data Sources
-
-{{source_credibility_notes}}
-
----
-
-## 2. Market Overview
-
-### Market Definition
-
-{{market_definition}}
-
-### Market Size and Growth
-
-#### Total Addressable Market (TAM)
-
-**Methodology:** {{tam_methodology}}
-
-{{tam_calculation}}
-
-#### Serviceable Addressable Market (SAM)
-
-{{sam_calculation}}
-
-#### Serviceable Obtainable Market (SOM)
-
-{{som_scenarios}}
-
-### Market Intelligence Summary
-
-{{market_intelligence_raw}}
-
-### Key Data Points
-
-{{key_data_points}}
-
----
-
-## 3. Market Trends and Drivers
-
-### Key Market Trends
-
-{{market_trends}}
-
-### Growth Drivers
-
-{{growth_drivers}}
-
-### Market Inhibitors
-
-{{market_inhibitors}}
-
-### Future Outlook
-
-{{future_outlook}}
-
----
-
-## 4. Customer Analysis
-
-### Target Customer Segments
-
-{{#segment_profile_1}}
-
-#### Segment 1
-
-{{segment_profile_1}}
-{{/segment_profile_1}}
-
-{{#segment_profile_2}}
-
-#### Segment 2
-
-{{segment_profile_2}}
-{{/segment_profile_2}}
-
-{{#segment_profile_3}}
-
-#### Segment 3
-
-{{segment_profile_3}}
-{{/segment_profile_3}}
-
-{{#segment_profile_4}}
-
-#### Segment 4
-
-{{segment_profile_4}}
-{{/segment_profile_4}}
-
-{{#segment_profile_5}}
-
-#### Segment 5
-
-{{segment_profile_5}}
-{{/segment_profile_5}}
-
-### Jobs-to-be-Done Analysis
-
-{{jobs_to_be_done}}
-
-### Pricing Analysis and Willingness to Pay
-
-{{pricing_analysis}}
-
----
-
-## 5. Competitive Landscape
-
-### Market Structure
-
-{{market_structure}}
-
-### Competitor Analysis
-
-{{#competitor_analysis_1}}
-
-#### Competitor 1
-
-{{competitor_analysis_1}}
-{{/competitor_analysis_1}}
-
-{{#competitor_analysis_2}}
-
-#### Competitor 2
-
-{{competitor_analysis_2}}
-{{/competitor_analysis_2}}
-
-{{#competitor_analysis_3}}
-
-#### Competitor 3
-
-{{competitor_analysis_3}}
-{{/competitor_analysis_3}}
-
-{{#competitor_analysis_4}}
-
-#### Competitor 4
-
-{{competitor_analysis_4}}
-{{/competitor_analysis_4}}
-
-{{#competitor_analysis_5}}
-
-#### Competitor 5
-
-{{competitor_analysis_5}}
-{{/competitor_analysis_5}}
-
-### Competitive Positioning
-
-{{competitive_positioning}}
-
----
-
-## 6. Industry Analysis
-
-### Porter's Five Forces Assessment
-
-{{porters_five_forces}}
-
-### Technology Adoption Lifecycle
-
-{{adoption_lifecycle}}
-
-### Value Chain Analysis
-
-{{value_chain_analysis}}
-
----
-
-## 7. Market Opportunities
-
-### Identified Opportunities
-
-{{market_opportunities}}
-
-### Opportunity Prioritization Matrix
-
-{{opportunity_prioritization}}
-
----
-
-## 8. Strategic Recommendations
-
-### Go-to-Market Strategy
-
-{{gtm_strategy}}
-
-#### Positioning Strategy
-
-{{positioning_strategy}}
-
-#### Target Segment Sequencing
-
-{{segment_sequencing}}
-
-#### Channel Strategy
-
-{{channel_strategy}}
-
-#### Pricing Strategy
-
-{{pricing_recommendations}}
-
-### Implementation Roadmap
-
-{{implementation_roadmap}}
-
----
-
-## 9. Risk Assessment
-
-### Risk Analysis
-
-{{risk_assessment}}
-
-### Mitigation Strategies
-
-{{mitigation_strategies}}
-
----
-
-## 10. Financial Projections
-
-{{#financial_projections}}
-{{financial_projections}}
-{{/financial_projections}}
-
----
-
-## Appendices
-
-### Appendix A: Data Sources and References
-
-{{data_sources}}
-
-### Appendix B: Detailed Calculations
-
-{{detailed_calculations}}
-
-### Appendix C: Additional Analysis
-
-{{#appendices}}
-{{appendices}}
-{{/appendices}}
-
-### Appendix D: Glossary of Terms
-
-{{glossary}}
-
----
-
-## References and Sources
-
-**CRITICAL: All data in this report must be verifiable through the sources listed below**
-
-### Market Size and Growth Data Sources
-
-{{sources_market_size}}
-
-### Competitive Intelligence Sources
-
-{{sources_competitive}}
-
-### Customer Research Sources
-
-{{sources_customer}}
-
-### Industry Trends and Analysis Sources
-
-{{sources_trends}}
-
-### Additional References
-
-{{sources_additional}}
-
-### Source Quality Assessment
-
-- **High Credibility Sources (2+ corroborating):** {{high_confidence_count}} claims
-- **Medium Credibility (single source):** {{medium_confidence_count}} claims
-- **Low Credibility (needs verification):** {{low_confidence_count}} claims
-
-**Note:** Any claim marked [Low Confidence] or [Single source] should be independently verified before making critical business decisions.
-
----
-
-## Document Information
-
-**Workflow:** BMad Market Research Workflow v1.0
-**Generated:** {{date}}
-**Next Review:** {{next_review_date}}
-**Classification:** {{classification}}
-
-### Research Quality Metrics
-
-- **Data Freshness:** Current as of {{date}}
-- **Source Reliability:** {{source_reliability_score}}
-- **Confidence Level:** {{confidence_level}}
-- **Total Sources Cited:** {{total_sources}}
-- **Web Searches Conducted:** {{search_count}}
-
----
-
-_This market research report was generated using the BMad Method Market Research Workflow, combining systematic analysis frameworks with real-time market intelligence gathering. All factual claims are backed by cited sources with verification dates._
diff --git a/src/modules/bmm/workflows/1-analysis/research/template-technical.md b/src/modules/bmm/workflows/1-analysis/research/template-technical.md
deleted file mode 100644
index 8bb9c442..00000000
--- a/src/modules/bmm/workflows/1-analysis/research/template-technical.md
+++ /dev/null
@@ -1,245 +0,0 @@
-# Technical Research Report: {{technical_question}}
-
-**Date:** {{date}}
-**Prepared by:** {{user_name}}
-**Project Context:** {{project_context}}
-
----
-
-## Executive Summary
-
-{{recommendations}}
-
-### Key Recommendation
-
-**Primary Choice:** [Technology/Pattern Name]
-
-**Rationale:** [2-3 sentence summary]
-
-**Key Benefits:**
-
-- [Benefit 1]
-- [Benefit 2]
-- [Benefit 3]
-
----
-
-## 1. Research Objectives
-
-### Technical Question
-
-{{technical_question}}
-
-### Project Context
-
-{{project_context}}
-
-### Requirements and Constraints
-
-#### Functional Requirements
-
-{{functional_requirements}}
-
-#### Non-Functional Requirements
-
-{{non_functional_requirements}}
-
-#### Technical Constraints
-
-{{technical_constraints}}
-
----
-
-## 2. Technology Options Evaluated
-
-{{technology_options}}
-
----
-
-## 3. Detailed Technology Profiles
-
-{{#tech_profile_1}}
-
-### Option 1: [Technology Name]
-
-{{tech_profile_1}}
-{{/tech_profile_1}}
-
-{{#tech_profile_2}}
-
-### Option 2: [Technology Name]
-
-{{tech_profile_2}}
-{{/tech_profile_2}}
-
-{{#tech_profile_3}}
-
-### Option 3: [Technology Name]
-
-{{tech_profile_3}}
-{{/tech_profile_3}}
-
-{{#tech_profile_4}}
-
-### Option 4: [Technology Name]
-
-{{tech_profile_4}}
-{{/tech_profile_4}}
-
-{{#tech_profile_5}}
-
-### Option 5: [Technology Name]
-
-{{tech_profile_5}}
-{{/tech_profile_5}}
-
----
-
-## 4. Comparative Analysis
-
-{{comparative_analysis}}
-
-### Weighted Analysis
-
-**Decision Priorities:**
-{{decision_priorities}}
-
-{{weighted_analysis}}
-
----
-
-## 5. Trade-offs and Decision Factors
-
-{{use_case_fit}}
-
-### Key Trade-offs
-
-[Comparison of major trade-offs between top options]
-
----
-
-## 6. Real-World Evidence
-
-{{real_world_evidence}}
-
----
-
-## 7. Architecture Pattern Analysis
-
-{{#architecture_pattern_analysis}}
-{{architecture_pattern_analysis}}
-{{/architecture_pattern_analysis}}
-
----
-
-## 8. Recommendations
-
-{{recommendations}}
-
-### Implementation Roadmap
-
-1. **Proof of Concept Phase**
- - [POC objectives and timeline]
-
-2. **Key Implementation Decisions**
- - [Critical decisions to make during implementation]
-
-3. **Migration Path** (if applicable)
- - [Migration approach from current state]
-
-4. **Success Criteria**
- - [How to validate the decision]
-
-### Risk Mitigation
-
-{{risk_mitigation}}
-
----
-
-## 9. Architecture Decision Record (ADR)
-
-{{architecture_decision_record}}
-
----
-
-## 10. References and Resources
-
-### Documentation
-
-- [Links to official documentation]
-
-### Benchmarks and Case Studies
-
-- [Links to benchmarks and real-world case studies]
-
-### Community Resources
-
-- [Links to communities, forums, discussions]
-
-### Additional Reading
-
-- [Links to relevant articles, papers, talks]
-
----
-
-## Appendices
-
-### Appendix A: Detailed Comparison Matrix
-
-[Full comparison table with all evaluated dimensions]
-
-### Appendix B: Proof of Concept Plan
-
-[Detailed POC plan if needed]
-
-### Appendix C: Cost Analysis
-
-[TCO analysis if performed]
-
----
-
-## References and Sources
-
-**CRITICAL: All technical claims, versions, and benchmarks must be verifiable through sources below**
-
-### Official Documentation and Release Notes
-
-{{sources_official_docs}}
-
-### Performance Benchmarks and Comparisons
-
-{{sources_benchmarks}}
-
-### Community Experience and Reviews
-
-{{sources_community}}
-
-### Architecture Patterns and Best Practices
-
-{{sources_architecture}}
-
-### Additional Technical References
-
-{{sources_additional}}
-
-### Version Verification
-
-- **Technologies Researched:** {{technology_count}}
-- **Versions Verified ({{current_year}}):** {{verified_versions_count}}
-- **Sources Requiring Update:** {{outdated_sources_count}}
-
-**Note:** All version numbers were verified using current {{current_year}} sources. Versions may change - always verify latest stable release before implementation.
-
----
-
-## Document Information
-
-**Workflow:** BMad Research Workflow - Technical Research v2.0
-**Generated:** {{date}}
-**Research Type:** Technical/Architecture Research
-**Next Review:** [Date for review/update]
-**Total Sources Cited:** {{total_sources}}
-
----
-
-_This technical research report was generated using the BMad Method Research Workflow, combining systematic technology evaluation frameworks with real-time research and analysis. All version numbers and technical claims are backed by current {{current_year}} sources._
diff --git a/src/modules/bmm/workflows/1-analysis/research/workflow.md b/src/modules/bmm/workflows/1-analysis/research/workflow.md
new file mode 100644
index 00000000..b7a88da5
--- /dev/null
+++ b/src/modules/bmm/workflows/1-analysis/research/workflow.md
@@ -0,0 +1,145 @@
+---
+name: Research Workflow
+description: Conduct comprehensive research across multiple domains using current web data and verified sources - Market, Technical, Domain and other research types.
+---
+
+# Research Workflow
+
+**Goal:** Conduct comprehensive research across multiple domains using current web data and verified sources
+
+**Your Role:** You are a research facilitator and web data analyst working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **micro-file architecture** with **routing-based discovery**:
+
+- Each research type has its own step folder
+- Step 01 discovers research type and routes to appropriate sub-workflow
+- Sequential progression within each research type
+- Document state tracked in frontmatter
+
+---
+
+## INITIALIZATION
+
+### Configuration Loading
+
+Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve:
+
+- `project_name`, `output_folder`, `user_name`
+- `communication_language`, `document_output_language`, `user_skill_level`
+- `date`, `current_year`, `current_month` as system-generated values
+- `enable_web_research = true` (web research is default behavior)
+
+### Paths
+
+- `installed_path` = `{project-root}/{bmad_folder}/bmm/workflows/1-analysis/research`
+- `template_path` = `{installed_path}/research.template.md`
+- `default_output_file` = `{output_folder}/analysis/research/{{research_type}}-{{topic}}-research-{{date}}.md` (dynamic based on research type)
+
+---
+
+## RESEARCH BEHAVIOR
+
+### Web Research Standards
+
+- **Current Data Only**: Always use {{current_year}} in web searches
+- **Source Verification**: Require citations for all factual claims
+- **Anti-Hallucination Protocol**: Never present information without verified sources
+- **Multiple Sources**: Require at least 2 independent sources for critical claims
+- **Conflict Resolution**: Present conflicting views and note discrepancies
+- **Confidence Levels**: Flag uncertain data with [High/Medium/Low Confidence]
+
+### Source Quality Standards
+
+- **Distinguish Clearly**: Facts (from sources) vs Analysis (interpretation) vs Speculation
+- **URL Citation**: Always include source URLs when presenting web search data
+- **Critical Claims**: Market size, growth rates, competitive data need verification
+- **Fact Checking**: Apply fact-checking to critical data points
+
+---
+
+## EXECUTION
+
+Execute research type discovery and routing:
+
+### Research Type Discovery
+
+**Your Role:** You are a research facilitator and web data analyst working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.
+
+**Research Standards:**
+
+- **Anti-Hallucination Protocol**: Never present information without verified sources
+- **Current Data Only**: Always use {{current_year}} in web searches
+- **Source Citation**: Always include URLs for factual claims from web searches
+- **Multiple Sources**: Require 2+ independent sources for critical claims
+- **Conflict Resolution**: Present conflicting views and note discrepancies
+- **Confidence Levels**: Flag uncertain data with [High/Medium/Low Confidence]
+
+### Collaborative Research Discovery
+
+"Welcome {{user_name}}! I'm excited to work with you as your research partner. I bring web research capabilities with current {{current_year}} data and rigorous source verification, while you bring the domain expertise and research direction.
+
+\*\*What would you like to research today?"
+
+### Research Type Identification
+
+Listen for research type indicators and present options:
+
+**Research Options:**
+
+1. **Market Research** - Market size, growth, competition, customer insights
+2. **Domain Research** - Industry analysis, regulations, technology trends in specific domain
+3. **Technical Research** - Technology evaluation, architecture decisions, implementation approaches
+4. **Deep Research Prompt** - Creating structured research prompts for AI platforms
+
+### Research Type Routing
+
+Based on user selection, route to appropriate sub-workflow:
+
+#### If Market Research:
+
+- Set `research_type = "market"`
+- Set output file: `{output_folder}/analysis/research/market-{{topic}}-research-{{date}}.md`
+- Load: `./market-steps/step-01-init.md`
+
+#### If Domain Research:
+
+- Set `research_type = "domain"`
+- Set output file: `{output_folder}/analysis/research/domain-{{topic}}-research-{{date}}.md`
+- Load: `./domain-steps/step-01-init.md`
+
+#### If Technical Research:
+
+- Set `research_type = "technical"`
+- Set output file: `{output_folder}/analysis/research/technical-{{topic}}-research-{{date}}.md`
+- Load: `./technical-steps/step-01-init.md`
+
+#### If Deep Research Prompt:
+
+- Set `research_type = "deep-prompt"`
+- Set output file: `{output_folder}/analysis/research/deep-prompt-{{topic}}-research-{{date}}.md`
+- Load: `./deep-prompt-steps/step-01-init.md`
+
+### Document Initialization
+
+Create research document with proper metadata:
+
+```yaml
+---
+stepsCompleted: [1]
+inputDocuments: []
+workflowType: 'research'
+lastStep: 1
+research_type: '{{research_type}}'
+user_name: '{{user_name}}'
+date: '{{date}}'
+current_year: '{{current_year}}'
+web_research_enabled: true
+source_verification: true
+---
+```
+
+**Note:** All research workflows emphasize current web data with {{current_year}} searches and rigorous source verification.
diff --git a/src/modules/bmm/workflows/1-analysis/research/workflow.yaml b/src/modules/bmm/workflows/1-analysis/research/workflow.yaml
deleted file mode 100644
index f1e0ca5e..00000000
--- a/src/modules/bmm/workflows/1-analysis/research/workflow.yaml
+++ /dev/null
@@ -1,62 +0,0 @@
-# Research Workflow - Multi-Type Research System
-name: research
-description: "Adaptive research workflow supporting multiple research types: market research, deep research prompt generation, technical/architecture evaluation, competitive intelligence, user research, and domain analysis"
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-document_output_language: "{config_source}:document_output_language"
-user_skill_level: "{config_source}:user_skill_level"
-date: system-generated
-current_year: system-generated
-current_month: system-generated
-
-# Research behavior - WEB RESEARCH IS DEFAULT
-enable_web_research: true
-
-# Source tracking and verification - CRITICAL FOR ACCURACY
-require_citations: true
-require_source_urls: true
-minimum_sources_per_claim: 2
-fact_check_critical_data: true
-
-# Workflow components - ROUTER PATTERN
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/research"
-instructions: "{installed_path}/instructions-router.md" # Router loads specific instruction sets
-validation: "{installed_path}/checklist.md"
-
-# Research type specific instructions (loaded by router)
-instructions_market: "{installed_path}/instructions-market.md"
-instructions_deep_prompt: "{installed_path}/instructions-deep-prompt.md"
-instructions_technical: "{installed_path}/instructions-technical.md"
-
-# Templates (loaded based on research type)
-template_market: "{installed_path}/template-market.md"
-template_deep_prompt: "{installed_path}/template-deep-prompt.md"
-template_technical: "{installed_path}/template-technical.md"
-
-# Output configuration (dynamic based on research type selected in router)
-default_output_file: "{output_folder}/research-{{research_type}}-{{date}}.md"
-
-standalone: true
-
-web_bundle:
- name: "research"
- description: "Adaptive research workflow supporting multiple research types: market research, deep research prompt generation, technical/architecture evaluation, competitive intelligence, user research, and domain analysis"
- author: "BMad"
- instructions: "{bmad_folder}/bmm/workflows/1-analysis/research/instructions-router.md" # Router loads specific instruction sets
- validation: "{bmad_folder}/bmm/workflows/1-analysis/research/checklist.md"
- web_bundle_files:
- - "{bmad_folder}/bmm/workflows/1-analysis/research/instructions-router.md"
- - "{bmad_folder}/bmm/workflows/1-analysis/research/instructions-market.md"
- - "{bmad_folder}/bmm/workflows/1-analysis/research/instructions-deep-prompt.md"
- - "{bmad_folder}/bmm/workflows/1-analysis/research/instructions-technical.md"
- - "{bmad_folder}/bmm/workflows/1-analysis/research/template-market.md"
- - "{bmad_folder}/bmm/workflows/1-analysis/research/template-deep-prompt.md"
- - "{bmad_folder}/bmm/workflows/1-analysis/research/template-technical.md"
- - "{bmad_folder}/bmm/workflows/1-analysis/research/checklist.md"
- - "{bmad_folder}/bmm/workflows/1-analysis/research/checklist-deep-prompt.md"
- - "{bmad_folder}/bmm/workflows/1-analysis/research/checklist-technical.md"
diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01-init.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01-init.md
index c4bb9740..8e08eac1 100644
--- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01-init.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01-init.md
@@ -52,24 +52,34 @@ If no document exists or no `stepsCompleted` in frontmatter:
Discover and load context documents using smart discovery:
-**PRD (Priority: Sharded → Whole):**
+**PRD (Priority: Analysis → Main → Sharded → Whole):**
-1. Check for sharded PRD folder: `{output_folder}/*prd*/**/*.md`
-2. If folder exists: Load EVERY file in that folder completely for UX context
-3. If no folder exists: Try whole file: `{output_folder}/*prd*.md`
-4. Add discovered files to `inputDocuments` frontmatter
+1. Check analysis folder: `{output_folder}/analysis/*prd*.md`
+2. If no analysis files: Try main folder: `{output_folder}/*prd*.md`
+3. If no main files: Check for sharded PRD folder: `{output_folder}/*prd*/**/*.md`
+4. If sharded folder exists: Load EVERY file in that folder completely for UX context
+5. Add discovered files to `inputDocuments` frontmatter
-**Product Brief (Priority: Sharded → Whole):**
+**Product Brief (Priority: Analysis → Main → Sharded → Whole):**
-1. Check for sharded brief folder: `{output_folder}/*brief*/**/*.md`
-2. If folder exists: Load EVERY file in that folder completely
-3. If no folder exists: Try whole file: `{output_folder}/*brief*.md`
-4. Add discovered files to `inputDocuments` frontmatter
+1. Check analysis folder: `{output_folder}/analysis/*brief*.md`
+2. If no analysis files: Try main folder: `{output_folder}/*brief*.md`
+3. If no main files: Check for sharded brief folder: `{output_folder}/*brief*/**/*.md`
+4. If sharded folder exists: Load EVERY file in that folder completely
+5. Add discovered files to `inputDocuments` frontmatter
-**Other Context (Priority: Sharded → Whole):**
+**Research Documents (Priority: Analysis → Main → Sharded → Whole):**
-- Epics: `{output_folder}/*epic*/**/*.md` or `{output_folder}/*epic*.md`
-- Brainstorming: `{output_folder}/*brainstorm*/**/*.md` or `{output_folder}/*brainstorm*.md`
+1. Check analysis folder: `{output_folder}/analysis/research/*research*.md`
+2. If no analysis files: Try main folder: `{output_folder}/*research*.md`
+3. If no main files: Check for sharded research folder: `{output_folder}/*research*/**/*.md`
+4. Load useful research files completely
+5. Add discovered files to `inputDocuments` frontmatter
+
+**Other Context (Priority: Analysis → Main → Sharded):**
+
+- Epics: `{output_folder}/analysis/*epic*.md` or `{output_folder}/*epic*.md` or `{output_folder}/*epic*/**/*.md`
+- Brainstorming: `{output_folder}/analysis/brainstorming/*brainstorming*.md` or `{output_folder}/*brainstorming*.md`
**Loading Rules:**
diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md
index dff0595c..03514f8d 100644
--- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md
@@ -38,11 +38,13 @@ Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve:
### Input Document Discovery
-Discover context documents for UX context:
+Discover context documents for UX context (Priority: Analysis folder first, then main folder, then sharded):
-- PRD: `{output_folder}/*prd*/**/*.md` or `{output_folder}/*prd*.md`
-- Product brief: `{output_folder}/*brief*/**/*.md` or `{output_folder}/*brief*.md`
-- Epics: `{output_folder}/*epic*/**/*.md` or `{output_folder}/*epic*.md`
+- PRD: `{output_folder}/analysis/*prd*.md` or `{output_folder}/*prd*.md` or `{output_folder}/*prd*/**/*.md`
+- Product brief: `{output_folder}/analysis/*brief*.md` or `{output_folder}/*brief*.md` or `{output_folder}/*brief*/**/*.md`
+- Epics: `{output_folder}/analysis/*epic*.md` or `{output_folder}/*epic*.md` or `{output_folder}/*epic*/**/*.md`
+- Research: `{output_folder}/analysis/research/*research*.md` or `{output_folder}/*research*.md` or `{output_folder}/*research*/**/*.md`
+- Brainstorming: `{output_folder}/analysis/brainstorming/*brainstorming*.md` or `{output_folder}/*brainstorming*.md`
---
diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-01-init.md b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-01-init.md
index 8d49e05d..f0ea336a 100644
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-01-init.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-01-init.md
@@ -52,19 +52,27 @@ If no document exists or no `stepsCompleted` in frontmatter:
Discover and load context documents using smart discovery:
-**Product Brief (Priority: Sharded → Whole):**
+**Product Brief (Priority: Analysis → Main → Sharded → Whole):**
-1. Check for sharded brief folder: `{output_folder}/*brief*/**/*.md`
-2. If folder exists: Load EVERY file in that folder completely to build comprehensive brief context
-3. If no folder exists: Try whole file: `{output_folder}/*brief*.md`
-4. Add discovered files to `inputDocuments` frontmatter
+1. Check analysis folder: `{output_folder}/analysis/*brief*.md`
+2. If no analysis files: Try main folder: `{output_folder}/*brief*.md`
+3. If no main files: Check for sharded brief folder: `{output_folder}/*brief*/**/*.md`
+4. If sharded folder exists: Load EVERY file in that folder completely
+5. Add discovered files to `inputDocuments` frontmatter
-**Research Documents (Priority: Sharded → Whole):**
+**Research Documents (Priority: Analysis → Main → Sharded → Whole):**
-1. Check for sharded research folder: `{output_folder}/*research*/**/*.md`
-2. If folder exists: Load useful research files completely
-3. If no folder exists: Try whole file: `{output_folder}/*research*.md`
-4. Add discovered files to `inputDocuments` frontmatter
+1. Check analysis folder: `{output_folder}/analysis/research/*research*.md`
+2. If no analysis files: Try main folder: `{output_folder}/*research*.md`
+3. If no main files: Check for sharded research folder: `{output_folder}/*research*/**/*.md`
+4. Load useful research files completely
+5. Add discovered files to `inputDocuments` frontmatter
+
+**Brainstorming Documents (Priority: Analysis → Main):**
+
+1. Check analysis folder: `{output_folder}/analysis/brainstorming/*brainstorming*.md`
+2. If no analysis files: Try main folder: `{output_folder}/*brainstorming*.md`
+3. Add discovered files to `inputDocuments` frontmatter
**Project Documentation (Existing Projects):**
diff --git a/src/modules/bmm/workflows/3-solutioning/architecture/workflow.yaml b/src/modules/bmm/workflows/3-solutioning/architecture/workflow.yaml
index a88e017a..21e49033 100644
--- a/src/modules/bmm/workflows/3-solutioning/architecture/workflow.yaml
+++ b/src/modules/bmm/workflows/3-solutioning/architecture/workflow.yaml
@@ -13,27 +13,41 @@ user_skill_level: "{config_source}:user_skill_level"
date: system-generated
# Smart input file references - handles both whole docs and sharded docs
-# Priority: Whole document first, then sharded version
+# Priority: Analysis folder first, then main folder, then sharded version
# Strategy: How to load sharded documents (FULL_LOAD, SELECTIVE_LOAD, INDEX_GUIDED)
input_file_patterns:
prd:
description: "Product requirements and features"
- whole: "{output_folder}/*prd*.md"
- sharded: "{output_folder}/*prd*/index.md"
+ whole: ["{output_folder}/analysis/*prd*.md", "{output_folder}/*prd*.md"]
+ sharded: ["{output_folder}/*prd*/index.md"]
load_strategy: "FULL_LOAD"
epics:
description: "Epic and story breakdown (optional - uses PRD FRs if not present)"
- whole: "{output_folder}/*epic*.md"
- sharded: "{output_folder}/*epic*/index.md"
+ whole: ["{output_folder}/analysis/*epic*.md", "{output_folder}/*epic*.md"]
+ sharded: ["{output_folder}/*epic*/index.md"]
load_strategy: "FULL_LOAD"
ux_design:
description: "UX design specification (optional)"
- whole: "{output_folder}/*ux*.md"
- sharded: "{output_folder}/*ux*/index.md"
+ whole: ["{output_folder}/analysis/*ux*.md", "{output_folder}/*ux*.md"]
+ sharded: ["{output_folder}/*ux*/index.md"]
+ load_strategy: "FULL_LOAD"
+ product_brief:
+ description: "Product brief and brainstorming results (optional)"
+ whole: ["{output_folder}/analysis/*brief*.md", "{output_folder}/*brief*.md"]
+ sharded: ["{output_folder}/*brief*/index.md"]
+ load_strategy: "FULL_LOAD"
+ research:
+ description: "Research documents (optional)"
+ whole: ["{output_folder}/analysis/research/*research*.md", "{output_folder}/*research*.md"]
+ sharded: ["{output_folder}/*research*/index.md"]
+ load_strategy: "FULL_LOAD"
+ brainstorming:
+ description: "Brainstorming session results (optional)"
+ whole: ["{output_folder}/analysis/brainstorming/*brainstorming*.md", "{output_folder}/*brainstorming*.md"]
load_strategy: "FULL_LOAD"
document_project:
description: "Brownfield project documentation (optional)"
- sharded: "{output_folder}/index.md"
+ sharded: ["{output_folder}/index.md"]
load_strategy: "INDEX_GUIDED"
# Module path and component files