Merge ddd0e8fbf2 into a0732df56c

src/core/agents/bmad-master.agent.yaml

@@ -32,7 +32,7 @@ agent:
       description: "List Workflows"
 
     - trigger: "party-mode"
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
       description: "Group chat with all agents"
 
   # Empty prompts section (no custom prompts for this agent)

src/core/agents/bmad-web-orchestrator.agent.xml

@@ -105,7 +105,7 @@
     <item cmd="*help">Show numbered command list</item>
     <item cmd="*list-agents">List all available agents with their capabilities</item>
     <item cmd="*agents [agent-name]">Transform into a specific agent</item>
-    <item cmd="*party-mode" workflow="{bmad_folder}/core/workflows/party-mode/workflow.yaml">Enter group chat with all agents
+    <item cmd="*party-mode" exec="{bmad_folder}/core/workflows/party-mode/workflow.md">Enter group chat with all agents
       simultaneously</item>
     <item cmd="*advanced-elicitation" task="{bmad_folder}/core/tasks/advanced-elicitation.xml">Push agent to perform advanced elicitation</item>
     <item cmd="*exit">Exit current session</item>

src/core/workflows/brainstorming/README.md

@@ -1,261 +0,0 @@
----
-last-redoc-date: 2025-09-28
----
-
-# Brainstorming Session Workflow
-
-## Overview
-
-The brainstorming workflow facilitates interactive brainstorming sessions using diverse creative techniques. This workflow acts as an AI facilitator guiding users through various ideation methods to generate and refine creative solutions in a structured, energetic, and highly interactive manner.
-
-## Key Features
-
-- **36 Creative Techniques**: Comprehensive library spanning collaborative, structured, creative, deep, theatrical, wild, and introspective approaches
-- **Interactive Facilitation**: AI acts as a skilled facilitator using "Yes, and..." methodology
-- **Flexible Approach Selection**: User-guided, AI-recommended, random, or progressive technique flows
-- **Context-Aware Sessions**: Supports domain-specific brainstorming through context document input
-- **Systematic Organization**: Converges ideas into immediate opportunities, future innovations, and moonshots
-- **Action Planning**: Prioritizes top ideas with concrete next steps and timelines
-- **Session Documentation**: Comprehensive structured reports capturing all insights and outcomes
-
-## Usage
-
-### Configuration
-
-The workflow leverages configuration from `{bmad_folder}/core/config.yaml`:
-
-- **output_folder**: Where session results are saved
-- **user_name**: Session participant identification
-
-And the following has a default or can be passed in as an override for custom brainstorming scenarios.
-
-- **brain_techniques**: CSV database of 36 creative techniques, default is `./brain-methods.csv`
-
-## Workflow Structure
-
-### Files Included
-
-```
-brainstorming/
-├── workflow.yaml           # Configuration and metadata
-├── instructions.md         # Step-by-step execution guide
-├── template.md            # Session report structure
-├── brain-methods.csv      # Database of 36 creative techniques
-└── README.md              # This file
-```
-
-## Creative Techniques Library
-
-The workflow includes 36 techniques organized into 7 categories:
-
-### Collaborative Techniques
-
-- **Yes And Building**: Build momentum through positive additions
-- **Brain Writing Round Robin**: Silent idea generation with sequential building
-- **Random Stimulation**: Use random catalysts for unexpected connections
-- **Role Playing**: Generate solutions from multiple stakeholder perspectives
-
-### Structured Approaches
-
-- **SCAMPER Method**: Systematic creativity through seven lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse)
-- **Six Thinking Hats**: Explore through six perspectives (facts/emotions/benefits/risks/creativity/process)
-- **Mind Mapping**: Visual branching from central concepts
-- **Resource Constraints**: Innovation through extreme limitations
-
-### Creative Methods
-
-- **What If Scenarios**: Explore radical possibilities by questioning constraints
-- **Analogical Thinking**: Find solutions through domain parallels
-- **Reversal Inversion**: Flip problems upside down for fresh angles
-- **First Principles Thinking**: Strip away assumptions to rebuild from fundamentals
-- **Forced Relationships**: Connect unrelated concepts for innovation
-- **Time Shifting**: Explore solutions across different time periods
-- **Metaphor Mapping**: Use extended metaphors as thinking tools
-
-### Deep Analysis
-
-- **Five Whys**: Drill down through causation layers to root causes
-- **Morphological Analysis**: Systematically explore parameter combinations
-- **Provocation Technique**: Extract useful ideas from absurd starting points
-- **Assumption Reversal**: Challenge and flip core assumptions
-- **Question Storming**: Generate questions before seeking answers
-
-### Theatrical Approaches
-
-- **Time Travel Talk Show**: Interview past/present/future selves
-- **Alien Anthropologist**: Examine through completely foreign eyes
-- **Dream Fusion Laboratory**: Start with impossible solutions, work backwards
-- **Emotion Orchestra**: Let different emotions lead separate sessions
-- **Parallel Universe Cafe**: Explore under alternative reality rules
-
-### Wild Methods
-
-- **Chaos Engineering**: Deliberately break things to discover robust solutions
-- **Guerrilla Gardening Ideas**: Plant unexpected solutions in unlikely places
-- **Pirate Code Brainstorm**: Take what works from anywhere and remix
-- **Zombie Apocalypse Planning**: Design for extreme survival scenarios
-- **Drunk History Retelling**: Explain with uninhibited simplicity
-
-### Introspective Delight
-
-- **Inner Child Conference**: Channel pure childhood curiosity
-- **Shadow Work Mining**: Explore what you're avoiding or resisting
-- **Values Archaeology**: Excavate deep personal values driving decisions
-- **Future Self Interview**: Seek wisdom from your wiser future self
-- **Body Wisdom Dialogue**: Let physical sensations guide ideation
-
-## Workflow Process
-
-### Phase 1: Session Setup (Step 1)
-
-- Context gathering (topic, goals, constraints)
-- Domain-specific guidance if context document provided
-- Session scope definition (broad exploration vs. focused ideation)
-
-### Phase 2: Approach Selection (Step 2)
-
-- **User-Selected**: Browse and choose specific techniques
-- **AI-Recommended**: Tailored technique suggestions based on context
-- **Random Selection**: Surprise technique for creative breakthrough
-- **Progressive Flow**: Multi-technique journey from broad to focused
-
-### Phase 3: Interactive Facilitation (Step 3)
-
-- Master facilitator approach using questions, not answers
-- "Yes, and..." building methodology
-- Energy monitoring and technique switching
-- Real-time idea capture and momentum building
-- Quantity over quality focus (aim: 100 ideas in 60 minutes)
-
-### Phase 4: Convergent Organization (Step 4)
-
-- Review and categorize all generated ideas
-- Identify patterns and themes across techniques
-- Sort into three priority buckets for action planning
-
-### Phase 5: Insight Extraction (Step 5)
-
-- Surface recurring themes across multiple techniques
-- Identify key realizations and surprising connections
-- Extract deeper patterns and meta-insights
-
-### Phase 6: Action Planning (Step 6)
-
-- Prioritize top 3 ideas for implementation
-- Define concrete next steps for each priority
-- Determine resource needs and realistic timelines
-
-### Phase 7: Session Reflection (Step 7)
-
-- Analyze what worked well and areas for further exploration
-- Recommend follow-up techniques and next session planning
-- Capture emergent questions for future investigation
-
-### Phase 8: Report Generation (Step 8)
-
-- Compile comprehensive structured report
-- Calculate total ideas generated and techniques used
-- Format all content for sharing and future reference
-
-## Output
-
-### Generated Files
-
-- **Primary output**: Structured session report saved to `{output_folder}/brainstorming-session-results-{date}.md`
-- **Context integration**: Links to previous brainstorming sessions if available
-
-### Output Structure
-
-1. **Executive Summary** - Topic, goals, techniques used, total ideas generated, key themes
-2. **Technique Sessions** - Detailed capture of each technique's ideation process
-3. **Idea Categorization** - Immediate opportunities, future innovations, moonshots, insights
-4. **Action Planning** - Top 3 priorities with rationale, steps, resources, timelines
-5. **Reflection and Follow-up** - Session analysis, recommendations, next steps planning
-
-## Requirements
-
-- No special software requirements
-- Access to the CIS module configuration (`{bmad_folder}/cis/config.yaml`)
-- Active participation and engagement throughout the interactive session
-- Optional: Domain context document for focused brainstorming
-
-## Best Practices
-
-### Before Starting
-
-1. **Define Clear Intent**: Know whether you want broad exploration or focused problem-solving
-2. **Gather Context**: Prepare any relevant background documents or domain knowledge
-3. **Set Time Expectations**: Plan for 45-90 minutes for a comprehensive session
-4. **Create Open Environment**: Ensure distraction-free space for creative thinking
-
-### During Execution
-
-1. **Embrace Quantity**: Generate many ideas without self-censoring
-2. **Build with "Yes, And"**: Accept and expand on ideas rather than judging
-3. **Stay Curious**: Follow unexpected connections and tangents
-4. **Trust the Process**: Let the facilitator guide you through technique transitions
-5. **Capture Everything**: Document all ideas, even seemingly silly ones
-6. **Monitor Energy**: Communicate when you need technique changes or breaks
-
-### After Completion
-
-1. **Review Within 24 Hours**: Re-read the report while insights are fresh
-2. **Act on Quick Wins**: Implement immediate opportunities within one week
-3. **Schedule Follow-ups**: Plan development sessions for promising concepts
-4. **Share Selectively**: Distribute relevant insights to appropriate stakeholders
-
-## Facilitation Principles
-
-The AI facilitator operates using these core principles:
-
-- **Ask, Don't Tell**: Use questions to draw out participant's own ideas
-- **Build, Don't Judge**: Use "Yes, and..." methodology, never "No, but..."
-- **Quantity Over Quality**: Aim for volume in generation phase
-- **Defer Judgment**: Evaluation comes after generation is complete
-- **Stay Curious**: Show genuine interest in participant's unique perspectives
-- **Monitor Energy**: Adapt technique and pace to participant's engagement level
-
-## Example Session Flow
-
-### Progressive Technique Flow
-
-1. **Mind Mapping** (10 min) - Build the landscape of possibilities
-2. **SCAMPER** (15 min) - Systematic exploration of improvement angles
-3. **Six Thinking Hats** (15 min) - Multiple perspectives on solutions
-4. **Forced Relationships** (10 min) - Creative synthesis of unexpected connections
-
-### Energy Checkpoints
-
-- After 15-20 minutes: "Should we continue with this technique or try something new?"
-- Before convergent phase: "Are you ready to start organizing ideas, or explore more?"
-- During action planning: "How's your energy for the final planning phase?"
-
-## Customization
-
-To customize this workflow:
-
-1. **Add New Techniques**: Extend `brain-methods.csv` with additional creative methods
-2. **Modify Facilitation Style**: Adjust prompts in `instructions.md` for different energy levels
-3. **Update Report Structure**: Modify `template.md` to include additional analysis sections
-4. **Create Domain Variants**: Develop specialized technique sets for specific industries
-
-## Version History
-
-- **v1.0.0** - Initial release
-  - 36 creative techniques across 7 categories
-  - Interactive facilitation with energy monitoring
-  - Comprehensive structured reporting
-  - Context-aware session guidance
-
-## Support
-
-For issues or questions:
-
-- Review technique descriptions in `brain-methods.csv` for facilitation guidance
-- Consult the workflow instructions in `instructions.md` for step-by-step details
-- Reference the template structure in `template.md` for output expectations
-- Follow BMAD documentation standards for workflow customization
-
----
-
-_Part of the BMad Method v6 - Creative Ideation and Synthesis (CIS) Module_

src/core/workflows/brainstorming/brain-methods.csv

@@ -1,36 +1,62 @@
-category,technique_name,description,facilitation_prompts,best_for,energy_level,typical_duration
+category,technique_name,description
-collaborative,Yes And Building,Build momentum through positive additions where each idea becomes a launching pad for the next - creates energetic collaborative flow,Yes and we could also...|Building on that idea...|That reminds me of...|What if we added?,team-building,high,15-20
+collaborative,Yes And Building,"Build momentum through positive additions where each idea becomes a launching pad - use prompts like 'Yes and we could also...' or 'Building on that idea...' to create energetic collaborative flow that builds upon previous contributions"
-collaborative,Brain Writing Round Robin,Silent idea generation followed by building on others' written concepts - gives quieter voices equal contribution while maintaining documentation,Write your idea silently|Pass to the next person|Build on what you received|Keep ideas flowing,quiet-voices,moderate,20-25
+collaborative,Brain Writing Round Robin,"Silent idea generation followed by building on others' written concepts - gives quieter voices equal contribution while maintaining documentation through the sequence of writing silently, passing ideas, and building on received concepts"
-collaborative,Random Stimulation,Use random words/images as creative catalysts to force unexpected connections - breaks through mental blocks with serendipitous inspiration,Pick a random word/image|How does this relate?|What connections do you see?|Force a relationship
+collaborative,Random Stimulation,"Use random words/images as creative catalysts to force unexpected connections - breaks through mental blocks with serendipitous inspiration by asking how random elements relate, what connections exist, and forcing relationships"
-collaborative,Role Playing,Generate solutions from multiple stakeholder perspectives - builds empathy while ensuring comprehensive consideration of all viewpoints,Think as a [role]|What would they want?|How would they approach this?|What matters to them?
+collaborative,Role Playing,"Generate solutions from multiple stakeholder perspectives to build empathy while ensuring comprehensive consideration - embody different roles by asking what they want, how they'd approach problems, and what matters most to them"
-creative,What If Scenarios,Explore radical possibilities by questioning all constraints and assumptions - perfect for breaking through stuck thinking and discovering unexpected opportunities,What if we had unlimited resources?|What if the opposite were true?|What if this problem didn't exist?,innovation,high,15-20
+collaborative,Ideation Relay Race,"Rapid-fire idea building under time pressure creates urgency and breakthroughs - structure with 30-second additions, quick building on ideas, and fast passing to maintain creative momentum and prevent overthinking"
-creative,Analogical Thinking,Find creative solutions by drawing parallels to other domains - helps transfer successful patterns from one context to another,This is like what?|How is this similar to...?|What other examples come to mind?
+creative,What If Scenarios,"Explore radical possibilities by questioning all constraints and assumptions - perfect for breaking through stuck thinking using prompts like 'What if we had unlimited resources?' 'What if the opposite were true?' or 'What if this problem didn't exist?'"
-creative,Reversal Inversion,Deliberately flip problems upside down to reveal hidden assumptions and fresh angles - great when conventional approaches aren't working,What if we did the opposite?|How could we make this worse?|What's the reverse approach?
+creative,Analogical Thinking,"Find creative solutions by drawing parallels to other domains - transfer successful patterns by asking 'This is like what?' 'How is this similar to...' and 'What other examples come to mind?' to connect to existing solutions"
-creative,First Principles Thinking,Strip away assumptions to rebuild from fundamental truths - essential for breakthrough innovation and solving complex problems,What do we know for certain?|What are the fundamental truths?|If we started from scratch?
+creative,Reversal Inversion,"Deliberately flip problems upside down to reveal hidden assumptions and fresh angles - great when conventional approaches fail by asking 'What if we did the opposite?' 'How could we make this worse?' and 'What's the reverse approach?'"
-creative,Forced Relationships,Connect unrelated concepts to spark innovative bridges - excellent for generating unexpected solutions through creative collision,Take these two unrelated things|Find connections between them|What bridges exist?|How could they work together?
+creative,First Principles Thinking,"Strip away assumptions to rebuild from fundamental truths - essential for breakthrough innovation by asking 'What do we know for certain?' 'What are the fundamental truths?' and 'If we started from scratch?'"
-creative,Time Shifting,Explore how solutions would work across different time periods - reveals constraints and opportunities by changing temporal context,How would this work in the past?|What about 100 years from now?|Different era constraints?|Time-based solutions?
+creative,Forced Relationships,"Connect unrelated concepts to spark innovative bridges through creative collision - take two unrelated things, find connections between them, identify bridges, and explore how they could work together to generate unexpected solutions"
-creative,Metaphor Mapping,Use extended metaphors as thinking tools to explore problems from new angles - transforms abstract challenges into tangible narratives,This problem is like a [metaphor]|Extend the metaphor|What elements map over?|What insights emerge?
+creative,Time Shifting,"Explore solutions across different time periods to reveal constraints and opportunities by asking 'How would this work in the past?' 'What about 100 years from now?' 'Different era constraints?' and 'What time-based solutions apply?'"
-deep,Five Whys,Drill down through layers of causation to uncover root causes - essential for solving problems at their source rather than treating symptoms,Why did this happen?|Why is that?|And why is that true?|What's behind that?|Why ultimately?,problem-solving,moderate,10-15
+creative,Metaphor Mapping,"Use extended metaphors as thinking tools to explore problems from new angles - transforms abstract challenges into tangible narratives by asking 'This problem is like a metaphor,' extending the metaphor, and mapping elements to discover insights"
-deep,Morphological Analysis,Systematically explore all possible parameter combinations - perfect for complex systems requiring comprehensive solution mapping,What are the key parameters?|List options for each|Try different combinations|What patterns emerge?
+creative,Cross-Pollination,"Transfer solutions from completely different industries or domains to spark breakthrough innovations by asking how industry X would solve this, what patterns work in field Y, and how to adapt solutions from domain Z"
-deep,Provocation Technique,Use deliberately provocative statements to extract useful ideas from seemingly absurd starting points - catalyzes breakthrough thinking,What if [provocative statement]?|How could this be useful?|What idea does this trigger?|Extract the principle
+creative,Concept Blending,"Merge two or more existing concepts to create entirely new categories - goes beyond simple combination to genuine innovation by asking what emerges when concepts merge, what new category is created, and how the blend transcends original ideas"
-deep,Assumption Reversal,Challenge and flip core assumptions to rebuild from new foundations - essential for paradigm shifts and fresh perspectives,What assumptions are we making?|What if the opposite were true?|Challenge each assumption|Rebuild from new assumptions
+creative,Reverse Brainstorming,"Generate problems instead of solutions to identify hidden opportunities and unexpected pathways by asking 'What could go wrong?' 'How could we make this fail?' and 'What problems could we create?' to reveal solution insights"
-deep,Question Storming,Generate questions before seeking answers to properly define the problem space - ensures you're solving the right problem,Only ask questions|No answers allowed yet|What don't we know?|What should we be asking?
+creative,Sensory Exploration,"Engage all five senses to discover multi-dimensional solution spaces beyond purely analytical thinking by asking what ideas feel, smell, taste, or sound like, and how different senses engage with the problem space"
-introspective_delight,Inner Child Conference,Channel pure childhood curiosity and wonder - rekindles playful exploration and innocent questioning that cuts through adult complications,What would 7-year-old you ask?|Why why why?|Make it fun again|No boring allowed
+deep,Five Whys,"Drill down through layers of causation to uncover root causes - essential for solving problems at source rather than symptoms by asking 'Why did this happen?' repeatedly until reaching fundamental drivers and ultimate causes"
-introspective_delight,Shadow Work Mining,Explore what you're actively avoiding or resisting - uncovers hidden insights by examining unconscious blocks and resistance patterns,What are you avoiding?|Where's the resistance?|What scares you about this?|Mine the shadows
+deep,Morphological Analysis,"Systematically explore all possible parameter combinations for complex systems requiring comprehensive solution mapping - identify key parameters, list options for each, try different combinations, and identify emerging patterns"
-introspective_delight,Values Archaeology,Excavate the deep personal values driving your decisions - clarifies authentic priorities by digging to bedrock motivations,What really matters here?|Why do you care?|Dig to bedrock values|What's non-negotiable?
+deep,Provocation Technique,"Use deliberately provocative statements to extract useful ideas from seemingly absurd starting points - catalyzes breakthrough thinking by asking 'What if provocative statement?' 'How could this be useful?' 'What idea triggers?' and 'Extract the principle'"
-introspective_delight,Future Self Interview,Seek wisdom from your wiser future self - gains long-term perspective through imagined temporal self-mentoring,Ask your 80-year-old self|What would you tell younger you?|Future wisdom speaks|Long-term perspective
+deep,Assumption Reversal,"Challenge and flip core assumptions to rebuild from new foundations - essential for paradigm shifts by asking 'What assumptions are we making?' 'What if the opposite were true?' 'Challenge each assumption' and 'Rebuild from new assumptions'"
-introspective_delight,Body Wisdom Dialogue,Let physical sensations and gut feelings guide ideation - taps somatic intelligence often ignored by purely mental approaches,What does your body say?|Where do you feel it?|Trust the tension|Follow physical cues
+deep,Question Storming,"Generate questions before seeking answers to properly define problem space - ensures solving the right problem by asking only questions, no answers yet, focusing on what we don't know, and identifying what we should be asking"
-structured,SCAMPER Method,Systematic creativity through seven lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse) - ideal for methodical product improvement and innovation,S-What could you substitute?|C-What could you combine?|A-How could you adapt?|M-What could you modify?|P-Put to other uses?|E-What could you eliminate?|R-What if reversed?
+deep,Constraint Mapping,"Identify and visualize all constraints to find promising pathways around or through limitations - ask what all constraints exist, which are real vs imagined, and how to work around or eliminate barriers to solution space"
-structured,Six Thinking Hats,Explore problems through six distinct perspectives (facts/emotions/benefits/risks/creativity/process) - ensures comprehensive analysis without conflict,White-What facts do we know?|Red-How do you feel about this?|Yellow-What are the benefits?|Black-What could go wrong?|Green-What creative alternatives?|Blue-How should we think about this?
+deep,Failure Analysis,"Study successful failures to extract valuable insights and avoid common pitfalls - learns from what didn't work by asking what went wrong, why it failed, what lessons emerged, and how to apply failure wisdom to current challenges"
-structured,Mind Mapping,Visually branch ideas from a central concept to discover connections and expand thinking - perfect for organizing complex thoughts and seeing the big picture,Put the main idea in center|What branches from this?|How do these connect?|What sub-branches emerge?
+deep,Emergent Thinking,"Allow solutions to emerge organically without forcing linear progression - embraces complexity and natural development by asking what patterns emerge, what wants to happen naturally, and what's trying to emerge from the system"
-structured,Resource Constraints,Generate innovative solutions by imposing extreme limitations - forces essential priorities and creative efficiency under pressure,What if you had only $1?|No technology allowed?|One hour to solve?|Minimal resources only?
+introspective_delight,Inner Child Conference,"Channel pure childhood curiosity and wonder to rekindle playful exploration - ask what 7-year-old you would ask, use 'why why why' questioning, make it fun again, and forbid boring thinking to access innocent questioning that cuts through adult complications"
-theatrical,Time Travel Talk Show,Interview your past/present/future selves for temporal wisdom - playful method for gaining perspective across different life stages,Interview your past self|What would future you say?|Different timeline perspectives|Cross-temporal dialogue
+introspective_delight,Shadow Work Mining,"Explore what you're actively avoiding or resisting to uncover hidden insights - examine unconscious blocks and resistance patterns by asking what you're avoiding, where's resistance, what scares you, and mining the shadows for buried wisdom"
-theatrical,Alien Anthropologist,Examine familiar problems through completely foreign eyes - reveals hidden assumptions by adopting an outsider's bewildered perspective,You're an alien observer|What seems strange?|How would you explain this?|Outside perspective insights
+introspective_delight,Values Archaeology,"Excavate deep personal values driving decisions to clarify authentic priorities - dig to bedrock motivations by asking what really matters, why you care, what's non-negotiable, and what core values guide your choices"
-theatrical,Dream Fusion Laboratory,Start with impossible fantasy solutions then reverse-engineer practical steps - makes ambitious thinking actionable through backwards design,Dream the impossible solution|Work backwards to reality|What steps bridge the gap?|Make magic practical
+introspective_delight,Future Self Interview,"Seek wisdom from wiser future self for long-term perspective - gain temporal self-mentoring by asking your 80-year-old self what they'd tell younger you, how future wisdom speaks, and what long-term perspective reveals"
-theatrical,Emotion Orchestra,Let different emotions lead separate brainstorming sessions then harmonize - uses emotional intelligence for comprehensive perspective,Angry perspective ideas|Joyful approach|Fearful considerations|Hopeful solutions|Harmonize all voices
+introspective_delight,Body Wisdom Dialogue,"Let physical sensations and gut feelings guide ideation - tap somatic intelligence often ignored by mental approaches by asking what your body says, where you feel it, trusting tension, and following physical cues for embodied wisdom"
-theatrical,Parallel Universe Cafe,Explore solutions under alternative reality rules - breaks conventional thinking by changing fundamental assumptions about how things work,Different physics universe|Alternative social norms|Changed historical events|Reality rule variations
+introspective_delight,Permission Giving,"Grant explicit permission to think impossible thoughts and break self-imposed creative barriers - give yourself permission to explore, try, experiment, and break free from limitations that constrain authentic creative expression"
-wild,Chaos Engineering,Deliberately break things to discover robust solutions - builds anti-fragility by stress-testing ideas against worst-case scenarios,What if everything went wrong?|Break it on purpose|How does it fail gracefully?|Build from the rubble
+structured,SCAMPER Method,"Systematic creativity through seven lenses for methodical product improvement and innovation - Substitute (what could you substitute), Combine (what could you combine), Adapt (how could you adapt), Modify (what could you modify), Put to other uses, Eliminate, Reverse"
-wild,Guerrilla Gardening Ideas,Plant unexpected solutions in unlikely places - uses surprise and unconventional placement for stealth innovation,Where's the least expected place?|Plant ideas secretly|Grow solutions underground|Surprise implementation
+structured,Six Thinking Hats,"Explore problems through six distinct perspectives without conflict - White Hat (facts), Red Hat (emotions), Yellow Hat (benefits), Black Hat (risks), Green Hat (creativity), Blue Hat (process) to ensure comprehensive analysis from all angles"
-wild,Pirate Code Brainstorm,Take what works from anywhere and remix without permission - encourages rule-bending rapid prototyping and maverick thinking,What would pirates steal?|Remix without asking|Take the best and run|No permission needed
+structured,Mind Mapping,"Visually branch ideas from central concept to discover connections and expand thinking - perfect for organizing complex thoughts and seeing big picture by putting main idea in center, branching concepts, and identifying sub-branches"
-wild,Zombie Apocalypse Planning,Design solutions for extreme survival scenarios - strips away all but essential functions to find core value,Society collapsed - now what?|Only basics work|Build from nothing|Survival mode thinking
+structured,Resource Constraints,"Generate innovative solutions by imposing extreme limitations - forces essential priorities and creative efficiency under pressure by asking what if you had only $1, no technology, one hour to solve, or minimal resources only"
-wild,Drunk History Retelling,Explain complex ideas with uninhibited simplicity - removes overthinking barriers to find raw truth through simplified expression,Explain it like you're tipsy|No filter needed|Raw unedited thoughts|Simplify to absurdity
+structured,Decision Tree Mapping,"Map out all possible decision paths and outcomes to reveal hidden opportunities and risks - visualizes complex choice architectures by identifying possible paths, decision points, and where different choices lead"
+structured,Solution Matrix,"Create systematic grid of problem variables and solution approaches to find optimal combinations and discover gaps - identify key variables, solution approaches, test combinations, and identify most effective pairings"
+structured,Trait Transfer,"Borrow attributes from successful solutions in unrelated domains to enhance approach - systematically adapts winning characteristics by asking what traits make success X work, how to transfer these traits, and what they'd look like here"
+theatrical,Time Travel Talk Show,"Interview past/present/future selves for temporal wisdom - playful method for gaining perspective across different life stages by interviewing past self, asking what future you'd say, and exploring different timeline perspectives"
+theatrical,Alien Anthropologist,"Examine familiar problems through completely foreign eyes - reveals hidden assumptions by adopting outsider's bewildered perspective by becoming alien observer, asking what seems strange, and getting outside perspective insights"
+theatrical,Dream Fusion Laboratory,"Start with impossible fantasy solutions then reverse-engineer practical steps - makes ambitious thinking actionable through backwards design by dreaming impossible solutions, working backwards to reality, and identifying bridging steps"
+theatrical,Emotion Orchestra,"Let different emotions lead separate brainstorming sessions then harmonize - uses emotional intelligence for comprehensive perspective by exploring angry perspectives, joyful approaches, fearful considerations, hopeful solutions, then harmonizing all voices"
+theatrical,Parallel Universe Cafe,"Explore solutions under alternative reality rules - breaks conventional thinking by changing fundamental assumptions about how things work by exploring different physics universes, alternative social norms, changed historical events, and reality rule variations"
+theatrical,Persona Journey,"Embody different archetypes or personas to access diverse wisdom through character exploration - become the archetype, ask how persona would solve this, and explore what character sees that normal thinking misses"
+wild,Chaos Engineering,"Deliberately break things to discover robust solutions - builds anti-fragility by stress-testing ideas against worst-case scenarios by asking what if everything went wrong, breaking on purpose, how it fails gracefully, and building from rubble"
+wild,Guerrilla Gardening Ideas,"Plant unexpected solutions in unlikely places - uses surprise and unconventional placement for stealth innovation by asking where's the least expected place, planting ideas secretly, growing solutions underground, and implementing with surprise"
+wild,Pirate Code Brainstorm,"Take what works from anywhere and remix without permission - encourages rule-bending rapid prototyping and maverick thinking by asking what pirates would steal, remixing without asking, taking best and running, and needing no permission"
+wild,Zombie Apocalypse Planning,"Design solutions for extreme survival scenarios - strips away all but essential functions to find core value by asking what happens when society collapses, what basics work, building from nothing, and thinking in survival mode"
+wild,Drunk History Retelling,"Explain complex ideas with uninhibited simplicity - removes overthinking barriers to find raw truth through simplified expression by explaining like you're tipsy, using no filter, sharing raw thoughts, and simplifying to absurdity"
+wild,Anti-Solution,"Generate ways to make the problem worse or more interesting - reveals hidden assumptions through destructive creativity by asking how to sabotage this, what would make it fail spectacularly, and how to create more problems to find solution insights"
+wild,Quantum Superposition,"Hold multiple contradictory solutions simultaneously until best emerges through observation and testing - explores how all solutions could be true simultaneously, how contradictions coexist, and what happens when outcomes are observed"
+wild,Elemental Forces,"Imagine solutions being sculpted by natural elements to tap into primal creative energies - explore how earth would sculpt this, what fire would forge, how water flows through this, and what air reveals to access elemental wisdom"
+biomimetic,Nature's Solutions,"Study how nature solves similar problems and adapt biological strategies to challenge - ask how nature would solve this, what ecosystems provide parallels, and what biological strategies apply to access 3.8 billion years of evolutionary wisdom"
+biomimetic,Ecosystem Thinking,"Analyze problem as ecosystem to identify symbiotic relationships, natural succession, and ecological principles - explore symbiotic relationships, natural succession application, and ecological principles for systems thinking"
+biomimetic,Evolutionary Pressure,"Apply evolutionary principles to gradually improve solutions through selective pressure and adaptation - ask how evolution would optimize this, what selective pressures apply, and how this adapts over time to harness natural selection wisdom"
+quantum,Observer Effect,"Recognize how observing and measuring solutions changes their behavior - uses quantum principles for innovation by asking how observing changes this, what measurement effects matter, and how to use observer effect advantageously"
+quantum,Entanglement Thinking,"Explore how different solution elements might be connected regardless of distance - reveals hidden relationships by asking what elements are entangled, how distant parts affect each other, and what hidden connections exist between solution components"
+quantum,Superposition Collapse,"Hold multiple potential solutions simultaneously until constraints force single optimal outcome - leverages quantum decision theory by asking what if all options were possible, what constraints force collapse, and which solution emerges when observed"
+cultural,Indigenous Wisdom,"Draw upon traditional knowledge systems and indigenous approaches overlooked by modern thinking - ask how specific cultures would approach this, what traditional knowledge applies, and what ancestral wisdom guides us to access overlooked problem-solving methods"
+cultural,Fusion Cuisine,"Mix cultural approaches and perspectives like fusion cuisine - creates innovation through cultural cross-pollination by asking what happens when mixing culture A with culture B, what cultural hybrids emerge, and what fusion creates"
+cultural,Ritual Innovation,"Apply ritual design principles to create transformative experiences and solutions - uses anthropological insights for human-centered design by asking what ritual would transform this, how to make it ceremonial, and what transformation this needs"
+cultural,Mythic Frameworks,"Use myths and archetypal stories as frameworks for understanding and solving problems - taps into collective unconscious by asking what myth parallels this, what archetypes are involved, and how mythic structure informs solution"

src/core/workflows/brainstorming/instructions.md

@@ -1,315 +0,0 @@
-# Brainstorming Session Instructions
-
-## Workflow
-
-<workflow>
-<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project_root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml</critical>
-
-<step n="1" goal="Session Setup">
-
-<action>Check if context data was provided with workflow invocation</action>
-
-<check if="data attribute was passed to this workflow">
-  <action>Load the context document from the data file path</action>
-  <action>Study the domain knowledge and session focus</action>
-  <action>Use the provided context to guide the session</action>
-  <action>Acknowledge the focused brainstorming goal</action>
-  <ask response="session_refinement">I see we're brainstorming about the specific domain outlined in the context. What particular aspect would you like to explore?</ask>
-</check>
-
-<check if="no context data provided">
-  <action>Proceed with generic context gathering</action>
-  <ask response="session_topic">1. What are we brainstorming about?</ask>
-  <ask response="stated_goals">2. Are there any constraints or parameters we should keep in mind?</ask>
-  <ask>3. Is the goal broad exploration or focused ideation on specific aspects?</ask>
-
-<critical>Wait for user response before proceeding. This context shapes the entire session.</critical>
-</check>
-
-<template-output>session_topic, stated_goals</template-output>
-
-</step>
-
-<step n="2" goal="Present Approach Options">
-
-Based on the context from Step 1, present these four approach options:
-
-<ask response="selection">
-1. **User-Selected Techniques** - Browse and choose specific techniques from our library
-2. **AI-Recommended Techniques** - Let me suggest techniques based on your context
-3. **Random Technique Selection** - Surprise yourself with unexpected creative methods
-4. **Progressive Technique Flow** - Start broad, then narrow down systematically
-
-Which approach would you prefer? (Enter 1-4)
-</ask>
-
-  <step n="2a" title="User-Selected Techniques" if="selection==1">
-    <action>Load techniques from {brain_techniques} CSV file</action>
-    <action>Parse: category, technique_name, description, facilitation_prompts</action>
-
-    <check if="strong context from Step 1 (specific problem/goal)">
-      <action>Identify 2-3 most relevant categories based on stated_goals</action>
-      <action>Present those categories first with 3-5 techniques each</action>
-      <action>Offer "show all categories" option</action>
-    </check>
-
-    <check if="open exploration">
-      <action>Display all 7 categories with helpful descriptions</action>
-    </check>
-
-    Category descriptions to guide selection:
-    - **Structured:** Systematic frameworks for thorough exploration
-    - **Creative:** Innovative approaches for breakthrough thinking
-    - **Collaborative:** Group dynamics and team ideation methods
-    - **Deep:** Analytical methods for root cause and insight
-    - **Theatrical:** Playful exploration for radical perspectives
-    - **Wild:** Extreme thinking for pushing boundaries
-    - **Introspective Delight:** Inner wisdom and authentic exploration
-
-    For each category, show 3-5 representative techniques with brief descriptions.
-
-    Ask in your own voice: "Which technique(s) interest you? You can choose by name, number, or tell me what you're drawn to."
-
-  </step>
-
-  <step n="2b" title="AI-Recommended Techniques" if="selection==2">
-    <action>Review {brain_techniques} and select 3-5 techniques that best fit the context</action>
-
-    Analysis Framework:
-
-    1. **Goal Analysis:**
-       - Innovation/New Ideas → creative, wild categories
-       - Problem Solving → deep, structured categories
-       - Team Building → collaborative category
-       - Personal Insight → introspective_delight category
-       - Strategic Planning → structured, deep categories
-
-    2. **Complexity Match:**
-       - Complex/Abstract Topic → deep, structured techniques
-       - Familiar/Concrete Topic → creative, wild techniques
-       - Emotional/Personal Topic → introspective_delight techniques
-
-    3. **Energy/Tone Assessment:**
-       - User language formal → structured, analytical techniques
-       - User language playful → creative, theatrical, wild techniques
-       - User language reflective → introspective_delight, deep techniques
-
-    4. **Time Available:**
-       - <30 min → 1-2 focused techniques
-       - 30-60 min → 2-3 complementary techniques
-       - >60 min → Consider progressive flow (3-5 techniques)
-
-    Present recommendations in your own voice with:
-    - Technique name (category)
-    - Why it fits their context (specific)
-    - What they'll discover (outcome)
-    - Estimated time
-
-    Example structure:
-    "Based on your goal to [X], I recommend:
-
-    1. **[Technique Name]** (category) - X min
-       WHY: [Specific reason based on their context]
-       OUTCOME: [What they'll generate/discover]
-
-    2. **[Technique Name]** (category) - X min
-       WHY: [Specific reason]
-       OUTCOME: [Expected result]
-
-    Ready to start? [c] or would you prefer different techniques? [r]"
-
-  </step>
-
-  <step n="2c" title="Single Random Technique Selection" if="selection==3">
-    <action>Load all techniques from {brain_techniques} CSV</action>
-    <action>Select random technique using true randomization</action>
-    <action>Build excitement about unexpected choice</action>
-    <format>
-      Let's shake things up! The universe has chosen:
-      **{{technique_name}}** - {{description}}
-    </format>
-  </step>
-
-  <step n="2d" title="Progressive Flow" if="selection==4">
-    <action>Design a progressive journey through {brain_techniques} based on session context</action>
-    <action>Analyze stated_goals and session_topic from Step 1</action>
-    <action>Determine session length (ask if not stated)</action>
-    <action>Select 3-4 complementary techniques that build on each other</action>
-
-    Journey Design Principles:
-    - Start with divergent exploration (broad, generative)
-    - Move through focused deep dive (analytical or creative)
-    - End with convergent synthesis (integration, prioritization)
-
-    Common Patterns by Goal:
-    - **Problem-solving:** Mind Mapping → Five Whys → Assumption Reversal
-    - **Innovation:** What If Scenarios → Analogical Thinking → Forced Relationships
-    - **Strategy:** First Principles → SCAMPER → Six Thinking Hats
-    - **Team Building:** Brain Writing → Yes And Building → Role Playing
-
-    Present your recommended journey with:
-    - Technique names and brief why
-    - Estimated time for each (10-20 min)
-    - Total session duration
-    - Rationale for sequence
-
-    Ask in your own voice: "How does this flow sound? We can adjust as we go."
-
-  </step>
-
-<critical>Create the output document using the template, and record at the {{session_start_plan}} documenting the chosen techniques, along with which approach was used. For all remaining steps, progressively add to the document throughout the brainstorming</critical>
-</step>
-
-<step n="3" goal="Execute Techniques Interactively">
-
-<critical>
-REMEMBER: YOU ARE A MASTER Brainstorming Creative FACILITATOR: Guide the user as a facilitator to generate their own ideas through questions, prompts, and examples. Don't brainstorm for them unless they explicitly request it.
-</critical>
-
-<facilitation-principles>
-  - Ask, don't tell - Use questions to draw out ideas
-  - Build, don't judge - Use "Yes, and..." never "No, but..."
-  - Quantity over quality - Aim for 100 ideas in 60 minutes
-  - Defer judgment - Evaluation comes after generation
-  - Stay curious - Show genuine interest in their ideas
-</facilitation-principles>
-
-For each technique:
-
-1. **Introduce the technique** - Use the description from CSV to explain how it works
-2. **Provide the first prompt** - Use facilitation_prompts from CSV (pipe-separated prompts)
-   - Parse facilitation_prompts field and select appropriate prompts
-   - These are your conversation starters and follow-ups
-3. **Wait for their response** - Let them generate ideas
-4. **Build on their ideas** - Use "Yes, and..." or "That reminds me..." or "What if we also..."
-5. **Ask follow-up questions** - "Tell me more about...", "How would that work?", "What else?"
-6. **Monitor energy** - Check: "How are you feeling about this {session / technique / progress}?"
-   - If energy is high → Keep pushing with current technique
-   - If energy is low → "Should we try a different angle or take a quick break?"
-7. **Keep momentum** - Celebrate: "Great! You've generated [X] ideas so far!"
-8. **Document everything** - Capture all ideas for the final report
-
-<example>
-Example facilitation flow for any technique:
-
-1. Introduce: "Let's try [technique_name]. [Adapt description from CSV to their context]."
-
-2. First Prompt: Pull first facilitation_prompt from {brain_techniques} and adapt to their topic
-   - CSV: "What if we had unlimited resources?"
-   - Adapted: "What if you had unlimited resources for [their_topic]?"
-
-3. Build on Response: Use "Yes, and..." or "That reminds me..." or "Building on that..."
-
-4. Next Prompt: Pull next facilitation_prompt when ready to advance
-
-5. Monitor Energy: After a few rounds, check if they want to continue or switch
-
-The CSV provides the prompts - your role is to facilitate naturally in your unique voice.
-</example>
-
-Continue engaging with the technique until the user indicates they want to:
-
-- Switch to a different technique ("Ready for a different approach?")
-- Apply current ideas to a new technique
-- Move to the convergent phase
-- End the session
-
-<energy-checkpoint>
-  After 4 rounds with a technique, check: "Should we continue with this technique or try something new?"
-</energy-checkpoint>
-
-<template-output>technique_sessions</template-output>
-
-</step>
-
-<step n="4" goal="Convergent Phase - Organize Ideas">
-
-<transition-check>
-  "We've generated a lot of great ideas! Are you ready to start organizing them, or would you like to explore more?"
-</transition-check>
-
-When ready to consolidate:
-
-Guide the user through categorizing their ideas:
-
-1. **Review all generated ideas** - Display everything captured so far
-2. **Identify patterns** - "I notice several ideas about X... and others about Y..."
-3. **Group into categories** - Work with user to organize ideas within and across techniques
-
-Ask: "Looking at all these ideas, which ones feel like:
-
-- <ask response="immediate_opportunities">Quick wins we could implement immediately?</ask>
-- <ask response="future_innovations">Promising concepts that need more development?</ask>
-- <ask response="moonshots">Bold moonshots worth pursuing long-term?"</ask>
-
-<template-output>immediate_opportunities, future_innovations, moonshots</template-output>
-
-</step>
-
-<step n="5" goal="Extract Insights and Themes">
-
-Analyze the session to identify deeper patterns:
-
-1. **Identify recurring themes** - What concepts appeared across multiple techniques? -> key_themes
-2. **Surface key insights** - What realizations emerged during the process? -> insights_learnings
-3. **Note surprising connections** - What unexpected relationships were discovered? -> insights_learnings
-
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</invoke-task>
-
-<template-output>key_themes, insights_learnings</template-output>
-
-</step>
-
-<step n="6" goal="Action Planning">
-
-<energy-check>
-  "Great work so far! How's your energy for the final planning phase?"
-</energy-check>
-
-Work with the user to prioritize and plan next steps:
-
-<ask>Of all the ideas we've generated, which 3 feel most important to pursue?</ask>
-
-For each priority:
-
-1. Ask why this is a priority
-2. Identify concrete next steps
-3. Determine resource needs
-4. Set realistic timeline
-
-<template-output>priority_1_name, priority_1_rationale, priority_1_steps, priority_1_resources, priority_1_timeline</template-output>
-<template-output>priority_2_name, priority_2_rationale, priority_2_steps, priority_2_resources, priority_2_timeline</template-output>
-<template-output>priority_3_name, priority_3_rationale, priority_3_steps, priority_3_resources, priority_3_timeline</template-output>
-
-</step>
-
-<step n="7" goal="Session Reflection">
-
-Conclude with meta-analysis of the session:
-
-1. **What worked well** - Which techniques or moments were most productive?
-2. **Areas to explore further** - What topics deserve deeper investigation?
-3. **Recommended follow-up techniques** - What methods would help continue this work?
-4. **Emergent questions** - What new questions arose that we should address?
-5. **Next session planning** - When and what should we brainstorm next?
-
-<template-output>what_worked, areas_exploration, recommended_techniques, questions_emerged</template-output>
-<template-output>followup_topics, timeframe, preparation</template-output>
-
-</step>
-
-<step n="8" goal="Generate Final Report">
-
-Compile all captured content into the structured report template:
-
-1. Calculate total ideas generated across all techniques
-2. List all techniques used with duration estimates
-3. Format all content according to template structure
-4. Ensure all placeholders are filled with actual content
-
-<template-output>agent_role, agent_name, user_name, techniques_list, total_ideas</template-output>
-
-</step>
-
-</workflow>

src/core/workflows/brainstorming/steps/step-01-session-setup.md

@@ -0,0 +1,196 @@
+# Step 1: Session Setup and Continuation Detection
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+- ✅ ALWAYS treat this as collaborative facilitation
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- 💬 FOCUS on session setup and continuation detection only
+- 🚪 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
+- Brain techniques loaded on-demand from CSV when needed
+
+## YOUR TASK:
+
+Initialize the brainstorming workflow by detecting continuation state and setting up session context.
+
+## INITIALIZATION SEQUENCE:
+
+### 1. Check for Existing Workflow
+
+First, check if the output document already exists:
+
+- Look for file at `{output_folder}/analysis/brainstorming-session-{{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. Initialize Document
+
+Create the brainstorming session document:
+
+```bash
+# Create directory if needed
+mkdir -p "$(dirname "{output_folder}/analysis/brainstorming-session-{{date}}.md")"
+
+# Initialize from template
+cp "{template_path}" "{output_folder}/analysis/brainstorming-session-{{date}}.md"
+```
+
+#### B. Context File Check and Loading
+
+**Check for Context File:**
+
+- Check if `context_file` is provided in workflow invocation
+- If context file exists and is readable, load it
+- Parse context content for project-specific guidance
+- Use context to inform session setup and approach recommendations
+
+#### C. Session Context Gathering
+
+"Welcome {{user_name}}! I'm excited to facilitate your brainstorming session. I'll guide you through proven creativity techniques to generate innovative ideas and breakthrough solutions.
+
+**Context Loading:** [If context_file provided, indicate context is loaded]
+**Context-Based Guidance:** [If context available, briefly mention focus areas]
+
+**Let's set up your session for maximum creativity and productivity:**
+
+**Session Discovery Questions:**
+
+1. **What are we brainstorming about?** (The central topic or challenge)
+2. **What specific outcomes are you hoping for?** (Types of ideas, solutions, or insights)"
+
+#### D. Process User Responses
+
+Wait for user responses, then:
+
+**Session Analysis:**
+"Based on your responses, I understand we're focusing on **[summarized topic]** with goals around **[summarized objectives]**.
+
+**Session Parameters:**
+
+- **Topic Focus:** [Clear topic articulation]
+- **Primary Goals:** [Specific outcome objectives]
+
+**Does this accurately capture what you want to achieve?**"
+
+#### E. Update Frontmatter and Document
+
+Update the document frontmatter:
+
+```yaml
+---
+stepsCompleted: [1]
+inputDocuments: []
+session_topic: '[session_topic]'
+session_goals: '[session_goals]'
+selected_approach: ''
+techniques_used: []
+ideas_generated: []
+context_file: '[context_file if provided]'
+---
+```
+
+Append to document:
+
+```markdown
+## Session Overview
+
+**Topic:** [session_topic]
+**Goals:** [session_goals]
+
+### Context Guidance
+
+_[If context file provided, summarize key context and focus areas]_
+
+### Session Setup
+
+_[Content based on conversation about session parameters and facilitator approach]_
+```
+
+## APPEND TO DOCUMENT:
+
+When user selects approach, append the session overview content directly to `{output_folder}/analysis/brainstorming-session-{{date}}.md` using the structure from above.
+
+#### E. Continue to Technique Selection
+
+"**Session setup complete!** I have a clear understanding of your goals and can select the perfect techniques for your brainstorming needs.
+
+**Ready to explore technique approaches?**
+[1] User-Selected Techniques - Browse our complete technique library
+[2] AI-Recommended Techniques - Get customized suggestions based on your goals
+[3] Random Technique Selection - Discover unexpected creative methods
+[4] Progressive Technique Flow - Start broad, then systematically narrow focus
+
+Which approach appeals to you most? (Enter 1-4)"
+
+### 4. Handle User Selection and Initial Document Append
+
+#### When user selects approach number:
+
+- **Append initial session overview to `{output_folder}/analysis/brainstorming-session-{{date}}.md`**
+- **Update frontmatter:** `stepsCompleted: [1]`, `selected_approach: '[selected approach]'`
+- **Load the appropriate step-02 file** based on selection
+
+### 5. Handle User Selection
+
+After user selects approach number:
+
+- **If 1:** Load `./step-02a-user-selected.md`
+- **If 2:** Load `./step-02b-ai-recommended.md`
+- **If 3:** Load `./step-02c-random-selection.md`
+- **If 4:** Load `./step-02d-progressive-flow.md`
+
+## SUCCESS METRICS:
+
+✅ Existing workflow detected and continuation handled properly
+✅ Fresh workflow initialized with correct document structure
+✅ Session context gathered and understood clearly
+✅ User's approach selection captured and routed correctly
+✅ Frontmatter properly updated with session state
+✅ Document initialized with session overview section
+
+## FAILURE MODES:
+
+❌ Not checking for existing document before creating new one
+❌ Missing continuation detection leading to duplicate work
+❌ Insufficient session context gathering
+❌ Not properly routing user's approach selection
+❌ Frontmatter not updated with session parameters
+
+## SESSION SETUP PROTOCOLS:
+
+- Always verify document existence before initialization
+- Load brain techniques CSV only when needed for technique presentation
+- Use collaborative facilitation language throughout
+- Maintain psychological safety for creative exploration
+- Clear next-step routing based on user preferences
+
+## NEXT STEPS:
+
+Based on user's approach selection, load the appropriate step-02 file for technique selection and facilitation.
+
+Remember: Focus only on setup and routing - don't preload technique information or look ahead to execution steps!

src/core/workflows/brainstorming/steps/step-01b-continue.md

@@ -0,0 +1,121 @@
+# Step 1b: Workflow Continuation
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ YOU ARE A CONTINUATION FACILITATOR, not a fresh starter
+- 🎯 RESPECT EXISTING WORKFLOW state and progress
+- 📋 UNDERSTAND PREVIOUS SESSION context and outcomes
+- 🔍 SEAMLESSLY RESUME from where user left off
+- 💬 MAINTAIN CONTINUITY in session flow and rapport
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load and analyze existing document thoroughly
+- 💾 Update frontmatter with continuation state
+- 📖 Present current status and next options clearly
+- 🚫 FORBIDDEN repeating completed work or asking same questions
+
+## CONTEXT BOUNDARIES:
+
+- Existing document with frontmatter is available
+- Previous steps completed indicate session progress
+- Brain techniques CSV loaded when needed for remaining steps
+- User may want to continue, modify, or restart
+
+## YOUR TASK:
+
+Analyze existing brainstorming session state and provide seamless continuation options.
+
+## CONTINUATION SEQUENCE:
+
+### 1. Analyze Existing Session
+
+Load existing document and analyze current state:
+
+**Document Analysis:**
+
+- Read existing `{output_folder}/analysis/brainstorming-session-{{date}}.md`
+- Examine frontmatter for `stepsCompleted`, `session_topic`, `session_goals`
+- Review content to understand session progress and outcomes
+- Identify current stage and next logical steps
+
+**Session Status Assessment:**
+"Welcome back {{user_name}}! I can see your brainstorming session on **[session_topic]** from **[date]**.
+
+**Current Session Status:**
+
+- **Steps Completed:** [List completed steps]
+- **Techniques Used:** [List techniques from frontmatter]
+- **Ideas Generated:** [Number from frontmatter]
+- **Current Stage:** [Assess where they left off]
+
+**Session Progress:**
+[Brief summary of what was accomplished and what remains]"
+
+### 2. Present Continuation Options
+
+Based on session analysis, provide appropriate options:
+
+**If Session Completed:**
+"Your brainstorming session appears to be complete!
+
+**Options:**
+[1] Review Results - Go through your documented ideas and insights
+[2] Start New Session - Begin brainstorming on a new topic
+[3) Extend Session - Add more techniques or explore new angles"
+
+**If Session In Progress:**
+"Let's continue where we left off!
+
+**Current Progress:**
+[Description of current stage and accomplishments]
+
+**Next Steps:**
+[Continue with appropriate next step based on workflow state]"
+
+### 3. Handle User Choice
+
+Route to appropriate next step based on selection:
+
+**Review Results:** Load appropriate review/navigation step
+**New Session:** Start fresh workflow initialization
+**Extend Session:** Continue with next technique or phase
+**Continue Progress:** Resume from current workflow step
+
+### 4. Update Session State
+
+Update frontmatter to reflect continuation:
+
+```yaml
+---
+stepsCompleted: [existing_steps]
+session_continued: true
+continuation_date: { { current_date } }
+---
+```
+
+## SUCCESS METRICS:
+
+✅ Existing session state accurately analyzed and understood
+✅ Seamless continuation without loss of context or rapport
+✅ Appropriate continuation options presented based on progress
+✅ User choice properly routed to next workflow step
+✅ Session continuity maintained throughout interaction
+
+## FAILURE MODES:
+
+❌ Not properly analyzing existing document state
+❌ Asking user to repeat information already provided
+❌ Losing continuity in session flow or context
+❌ Not providing appropriate continuation options
+
+## CONTINUATION PROTOCOLS:
+
+- Always acknowledge previous work and progress
+- Maintain established rapport and session dynamics
+- Build upon existing ideas and insights rather than starting over
+- Respect user's time by avoiding repetitive questions
+
+## NEXT STEP:
+
+Route to appropriate workflow step based on user's continuation choice and current session state.

src/core/workflows/brainstorming/steps/step-02a-user-selected.md

@@ -0,0 +1,224 @@
+# Step 2a: User-Selected Techniques
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ YOU ARE A TECHNIQUE LIBRARIAN, not a recommender
+- 🎯 LOAD TECHNIQUES ON-DEMAND from brain-methods.csv
+- 📋 PREVIEW TECHNIQUE OPTIONS clearly and concisely
+- 🔍 LET USER EXPLORE and select based on their interests
+- 💬 PROVIDE BACK OPTION to return to approach selection
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load brain techniques CSV only when needed for presentation
+- ⚠️ Present [B] back option and [C] continue options
+- 💾 Update frontmatter with selected techniques
+- 📖 Route to technique execution after confirmation
+- 🚫 FORBIDDEN making recommendations or steering choices
+
+## CONTEXT BOUNDARIES:
+
+- Session context from Step 1 is available
+- Brain techniques CSV contains 36+ techniques across 7 categories
+- User wants full control over technique selection
+- May need to present techniques by category or search capability
+
+## YOUR TASK:
+
+Load and present brainstorming techniques from CSV, allowing user to browse and select based on their preferences.
+
+## USER SELECTION SEQUENCE:
+
+### 1. Load Brain Techniques Library
+
+Load techniques from CSV on-demand:
+
+"Perfect! Let's explore our complete brainstorming techniques library. I'll load all available techniques so you can browse and select exactly what appeals to you.
+
+**Loading Brain Techniques Library...**"
+
+**Load CSV and parse:**
+
+- Read `brain-methods.csv`
+- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration
+- Organize by categories for browsing
+
+### 2. Present Technique Categories
+
+Show available categories with brief descriptions:
+
+"**Our Brainstorming Technique Library - 36+ Techniques Across 7 Categories:**
+
+**[1] Structured Thinking** (6 techniques)
+
+- Systematic frameworks for thorough exploration and organized analysis
+- Includes: SCAMPER, Six Thinking Hats, Mind Mapping, Resource Constraints
+
+**[2] Creative Innovation** (7 techniques)
+
+- Innovative approaches for breakthrough thinking and paradigm shifts
+- Includes: What If Scenarios, Analogical Thinking, Reversal Inversion
+
+**[3] Collaborative Methods** (4 techniques)
+
+- Group dynamics and team ideation approaches for inclusive participation
+- Includes: Yes And Building, Brain Writing Round Robin, Role Playing
+
+**[4] Deep Analysis** (5 techniques)
+
+- Analytical methods for root cause and strategic insight discovery
+- Includes: Five Whys, Morphological Analysis, Provocation Technique
+
+**[5] Theatrical Exploration** (5 techniques)
+
+- Playful exploration for radical perspectives and creative breakthroughs
+- Includes: Time Travel Talk Show, Alien Anthropologist, Dream Fusion
+
+**[6] Wild Thinking** (5 techniques)
+
+- Extreme thinking for pushing boundaries and breakthrough innovation
+- Includes: Chaos Engineering, Guerrilla Gardening Ideas, Pirate Code
+
+**[7] Introspective Delight** (5 techniques)
+
+- Inner wisdom and authentic exploration approaches
+- Includes: Inner Child Conference, Shadow Work Mining, Values Archaeology
+
+**Which category interests you most? Enter 1-7, or tell me what type of thinking you're drawn to.**"
+
+### 3. Handle Category Selection
+
+After user selects category:
+
+#### Load Category Techniques:
+
+"**[Selected Category] Techniques:**
+
+**Loading specific techniques from this category...**"
+
+**Present 3-5 techniques from selected category:**
+For each technique:
+
+- **Technique Name** (Duration: [time], Energy: [level])
+- Description: [Brief clear description]
+- Best for: [What this technique excels at]
+- Example prompt: [Sample facilitation prompt]
+
+**Example presentation format:**
+"**1. SCAMPER Method** (Duration: 20-30 min, Energy: Moderate)
+
+- Systematic creativity through seven lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse)
+- Best for: Product improvement, innovation challenges, systematic idea generation
+- Example prompt: "What could you substitute in your current approach to create something new?"
+
+**2. Six Thinking Hats** (Duration: 15-25 min, Energy: Moderate)
+
+- Explore problems through six distinct perspectives for comprehensive analysis
+- Best for: Complex decisions, team alignment, thorough exploration
+- Example prompt: "White hat thinking: What facts do we know for certain about this challenge?"
+
+### 4. Allow Technique Selection
+
+"**Which techniques from this category appeal to you?**
+
+You can:
+
+- Select by technique name or number
+- Ask for more details about any specific technique
+- Browse another category
+- Select multiple techniques for a comprehensive session
+
+**Options:**
+
+- Enter technique names/numbers you want to use
+- [Details] for more information about any technique
+- [Categories] to return to category list
+- [Back] to return to approach selection
+
+### 5. Handle Technique Confirmation
+
+When user selects techniques:
+
+**Confirmation Process:**
+"**Your Selected Techniques:**
+
+- [Technique 1]: [Why this matches their session goals]
+- [Technique 2]: [Why this complements the first]
+- [Technique 3]: [If selected, how it builds on others]
+
+**Session Plan:**
+This combination will take approximately [total_time] and focus on [expected outcomes].
+
+**Confirm these choices?**
+[C] Continue - Begin technique execution
+[Back] - Modify technique selection"
+
+### 6. Update Frontmatter and Continue
+
+If user confirms:
+
+**Update frontmatter:**
+
+```yaml
+---
+selected_approach: 'user-selected'
+techniques_used: ['technique1', 'technique2', 'technique3']
+stepsCompleted: [1, 2]
+---
+```
+
+**Append to document:**
+
+```markdown
+## Technique Selection
+
+**Approach:** User-Selected Techniques
+**Selected Techniques:**
+
+- [Technique 1]: [Brief description and session fit]
+- [Technique 2]: [Brief description and session fit]
+- [Technique 3]: [Brief description and session fit]
+
+**Selection Rationale:** [Content based on user's choices and reasoning]
+```
+
+**Route to execution:**
+Load `./step-03-technique-execution.md`
+
+### 7. Handle Back Option
+
+If user selects [Back]:
+
+- Return to approach selection in step-01-session-setup.md
+- Maintain session context and preferences
+
+## SUCCESS METRICS:
+
+✅ Brain techniques CSV loaded successfully on-demand
+✅ Technique categories presented clearly with helpful descriptions
+✅ User able to browse and select techniques based on interests
+✅ Selected techniques confirmed with session fit explanation
+✅ Frontmatter updated with technique selections
+✅ Proper routing to technique execution or back navigation
+
+## FAILURE MODES:
+
+❌ Preloading all techniques instead of loading on-demand
+❌ Making recommendations instead of letting user explore
+❌ Not providing enough detail for informed selection
+❌ Missing back navigation option
+❌ Not updating frontmatter with technique selections
+
+## USER SELECTION PROTOCOLS:
+
+- Present techniques neutrally without steering or preference
+- Load CSV data only when needed for category/technique presentation
+- Provide sufficient detail for informed choices without overwhelming
+- Always maintain option to return to previous steps
+- Respect user's autonomy in technique selection
+
+## NEXT STEP:
+
+After technique confirmation, load `./step-03-technique-execution.md` to begin facilitating the selected brainstorming techniques.
+
+Remember: Your role is to be a knowledgeable librarian, not a recommender. Let the user explore and choose based on their interests and intuition!

src/core/workflows/brainstorming/steps/step-02b-ai-recommended.md

@@ -0,0 +1,236 @@
+# Step 2b: AI-Recommended Techniques
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ YOU ARE A TECHNIQUE MATCHMAKER, using AI analysis to recommend optimal approaches
+- 🎯 ANALYZE SESSION CONTEXT from Step 1 for intelligent technique matching
+- 📋 LOAD TECHNIQUES ON-DEMAND from brain-methods.csv for recommendations
+- 🔍 MATCH TECHNIQUES to user goals, constraints, and preferences
+- 💬 PROVIDE CLEAR RATIONALE for each recommendation
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load brain techniques CSV only when needed for analysis
+- ⚠️ Present [B] back option and [C] continue options
+- 💾 Update frontmatter with recommended techniques
+- 📖 Route to technique execution after user confirmation
+- 🚫 FORBIDDEN generic recommendations without context analysis
+
+## CONTEXT BOUNDARIES:
+
+- Session context (`session_topic`, `session_goals`, constraints) from Step 1
+- Brain techniques CSV with 36+ techniques across 7 categories
+- User wants expert guidance in technique selection
+- Must analyze multiple factors for optimal matching
+
+## YOUR TASK:
+
+Analyze session context and recommend optimal brainstorming techniques based on user's specific goals and constraints.
+
+## AI RECOMMENDATION SEQUENCE:
+
+### 1. Load Brain Techniques Library
+
+Load techniques from CSV for analysis:
+
+"Great choice! Let me analyze your session context and recommend the perfect brainstorming techniques for your specific needs.
+
+**Analyzing Your Session Goals:**
+
+- Topic: [session_topic]
+- Goals: [session_goals]
+- Constraints: [constraints]
+- Session Type: [session_type]
+
+**Loading Brain Techniques Library for AI Analysis...**"
+
+**Load CSV and parse:**
+
+- Read `brain-methods.csv`
+- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration
+
+### 2. Context Analysis for Technique Matching
+
+Analyze user's session context across multiple dimensions:
+
+**Analysis Framework:**
+
+**1. Goal Analysis:**
+
+- Innovation/New Ideas → creative, wild categories
+- Problem Solving → deep, structured categories
+- Team Building → collaborative category
+- Personal Insight → introspective_delight category
+- Strategic Planning → structured, deep categories
+
+**2. Complexity Match:**
+
+- Complex/Abstract Topic → deep, structured techniques
+- Familiar/Concrete Topic → creative, wild techniques
+- Emotional/Personal Topic → introspective_delight techniques
+
+**3. Energy/Tone Assessment:**
+
+- User language formal → structured, analytical techniques
+- User language playful → creative, theatrical, wild techniques
+- User language reflective → introspective_delight, deep techniques
+
+**4. Time Available:**
+
+- <30 min → 1-2 focused techniques
+- 30-60 min → 2-3 complementary techniques
+- > 60 min → Multi-phase technique flow
+
+### 3. Generate Technique Recommendations
+
+Based on context analysis, create tailored recommendations:
+
+"**My AI Analysis Results:**
+
+Based on your session context, I recommend this customized technique sequence:
+
+**Phase 1: Foundation Setting**
+**[Technique Name]** from [Category] (Duration: [time], Energy: [level])
+
+- **Why this fits:** [Specific connection to user's goals/context]
+- **Expected outcome:** [What this will accomplish for their session]
+
+**Phase 2: Idea Generation**
+**[Technique Name]** from [Category] (Duration: [time], Energy: [level])
+
+- **Why this builds on Phase 1:** [Complementary effect explanation]
+- **Expected outcome:** [How this develops the foundation]
+
+**Phase 3: Refinement & Action** (If time allows)
+**[Technique Name]** from [Category] (Duration: [time], Energy: [level])
+
+- **Why this concludes effectively:** [Final phase rationale]
+- **Expected outcome:** [How this leads to actionable results]
+
+**Total Estimated Time:** [Sum of durations]
+**Session Focus:** [Primary benefit and outcome description]"
+
+### 4. Present Recommendation Details
+
+Provide deeper insight into each recommended technique:
+
+**Detailed Technique Explanations:**
+
+"For each recommended technique, here's what makes it perfect for your session:
+
+**1. [Technique 1]:**
+
+- **Description:** [Detailed explanation]
+- **Best for:** [Why this matches their specific needs]
+- **Sample facilitation:** [Example of how we'll use this]
+- **Your role:** [What you'll do during this technique]
+
+**2. [Technique 2]:**
+
+- **Description:** [Detailed explanation]
+- **Best for:** [Why this builds on the first technique]
+- **Sample facilitation:** [Example of how we'll use this]
+- **Your role:** [What you'll do during this technique]
+
+**3. [Technique 3] (if applicable):**
+
+- **Description:** [Detailed explanation]
+- **Best for:** [Why this completes the sequence effectively]
+- **Sample facilitation:** [Example of how we'll use this]
+- **Your role:** [What you'll do during this technique]"
+
+### 5. Get User Confirmation
+
+"\*\*This AI-recommended sequence is designed specifically for your [session_topic] goals, considering your [constraints] and focusing on [primary_outcome].
+
+**Does this approach sound perfect for your session?**
+
+**Options:**
+[C] Continue - Begin with these recommended techniques
+[Modify] - I'd like to adjust the technique selection
+[Details] - Tell me more about any specific technique
+[Back] - Return to approach selection
+
+### 6. Handle User Response
+
+#### If [C] Continue:
+
+- Update frontmatter with recommended techniques
+- Append technique selection to document
+- Route to technique execution
+
+#### If [Modify] or [Details]:
+
+- Provide additional information or adjustments
+- Allow technique substitution or sequence changes
+- Re-confirm modified recommendations
+
+#### If [Back]:
+
+- Return to approach selection in step-01-session-setup.md
+- Maintain session context and preferences
+
+### 7. Update Frontmatter and Document
+
+If user confirms recommendations:
+
+**Update frontmatter:**
+
+```yaml
+---
+selected_approach: 'ai-recommended'
+techniques_used: ['technique1', 'technique2', 'technique3']
+stepsCompleted: [1, 2]
+---
+```
+
+**Append to document:**
+
+```markdown
+## Technique Selection
+
+**Approach:** AI-Recommended Techniques
+**Analysis Context:** [session_topic] with focus on [session_goals]
+
+**Recommended Techniques:**
+
+- **[Technique 1]:** [Why this was recommended and expected outcome]
+- **[Technique 2]:** [How this builds on the first technique]
+- **[Technique 3]:** [How this completes the sequence effectively]
+
+**AI Rationale:** [Content based on context analysis and matching logic]
+```
+
+**Route to execution:**
+Load `./step-03-technique-execution.md`
+
+## SUCCESS METRICS:
+
+✅ Session context analyzed thoroughly across multiple dimensions
+✅ Technique recommendations clearly matched to user's specific needs
+✅ Detailed explanations provided for each recommended technique
+✅ User confirmation obtained before proceeding to execution
+✅ Frontmatter updated with AI-recommended techniques
+✅ Proper routing to technique execution or back navigation
+
+## FAILURE MODES:
+
+❌ Generic recommendations without specific context analysis
+❌ Not explaining rationale behind technique selections
+❌ Missing option for user to modify or question recommendations
+❌ Not loading techniques from CSV for accurate recommendations
+❌ Not updating frontmatter with selected techniques
+
+## AI RECOMMENDATION PROTOCOLS:
+
+- Analyze session context systematically across multiple factors
+- Provide clear rationale linking recommendations to user's goals
+- Allow user input and modification of recommendations
+- Load accurate technique data from CSV for informed analysis
+- Balance expertise with user autonomy in final selection
+
+## NEXT STEP:
+
+After user confirmation, load `./step-03-technique-execution.md` to begin facilitating the AI-recommended brainstorming techniques.
+
+Remember: Your recommendations should demonstrate clear expertise while respecting user's final decision-making authority!

src/core/workflows/brainstorming/steps/step-02c-random-selection.md

@@ -0,0 +1,208 @@
+# Step 2c: Random Technique Selection
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ YOU ARE A SERENDIPITY FACILITATOR, embracing unexpected creative discoveries
+- 🎯 USE RANDOM SELECTION for surprising technique combinations
+- 📋 LOAD TECHNIQUES ON-DEMAND from brain-methods.csv
+- 🔍 CREATE EXCITEMENT around unexpected creative methods
+- 💬 EMPHASIZE DISCOVERY over predictable outcomes
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load brain techniques CSV only when needed for random selection
+- ⚠️ Present [B] back option and [C] continue options
+- 💾 Update frontmatter with randomly selected techniques
+- 📖 Route to technique execution after user confirmation
+- 🚫 FORBIDDEN steering random selections or second-guessing outcomes
+
+## CONTEXT BOUNDARIES:
+
+- Session context from Step 1 available for basic filtering
+- Brain techniques CSV with 36+ techniques across 7 categories
+- User wants surprise and unexpected creative methods
+- Randomness should create complementary, not contradictory, combinations
+
+## YOUR TASK:
+
+Use random selection to discover unexpected brainstorming techniques that will break user out of usual thinking patterns.
+
+## RANDOM SELECTION SEQUENCE:
+
+### 1. Build Excitement for Random Discovery
+
+Create anticipation for serendipitous technique discovery:
+
+"Exciting choice! You've chosen the path of creative serendipity. Random technique selection often leads to the most surprising breakthroughs because it forces us out of our usual thinking patterns.
+
+**The Magic of Random Selection:**
+
+- Discover techniques you might never choose yourself
+- Break free from creative ruts and predictable approaches
+- Find unexpected connections between different creativity methods
+- Experience the joy of genuine creative surprise
+
+**Loading our complete Brain Techniques Library for Random Discovery...**"
+
+**Load CSV and parse:**
+
+- Read `brain-methods.csv`
+- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration
+- Prepare for intelligent random selection
+
+### 2. Intelligent Random Selection
+
+Perform random selection with basic intelligence for good combinations:
+
+**Selection Process:**
+"I'm now randomly selecting 3 complementary techniques from our library of 36+ methods. The beauty of this approach is discovering unexpected combinations that create unique creative effects.
+
+**Randomizing Technique Selection...**"
+
+**Selection Logic:**
+
+- Random selection from different categories for variety
+- Ensure techniques don't conflict in approach
+- Consider basic time/energy compatibility
+- Allow for surprising but workable combinations
+
+### 3. Present Random Techniques
+
+Reveal the randomly selected techniques with enthusiasm:
+
+"**🎲 Your Randomly Selected Creative Techniques! 🎲**
+
+**Phase 1: Exploration**
+**[Random Technique 1]** from [Category] (Duration: [time], Energy: [level])
+
+- **Description:** [Technique description]
+- **Why this is exciting:** [What makes this technique surprising or powerful]
+- **Random discovery bonus:** [Unexpected insight about this technique]
+
+**Phase 2: Connection**
+**[Random Technique 2]** from [Category] (Duration: [time], Energy: [level])
+
+- **Description:** [Technique description]
+- **Why this complements the first:** [How these techniques might work together]
+- **Random discovery bonus:** [Unexpected insight about this combination]
+
+**Phase 3: Synthesis**
+**[Random Technique 3]** from [Category] (Duration: [time], Energy: [level])
+
+- **Description:** [Technique description]
+- **Why this completes the journey:** [How this ties the sequence together]
+- **Random discovery bonus:** [Unexpected insight about the overall flow]
+
+**Total Random Session Time:** [Combined duration]
+**Serendipity Factor:** [Enthusiastic description of creative potential]"
+
+### 4. Highlight the Creative Potential
+
+Emphasize the unique value of this random combination:
+
+"**Why This Random Combination is Perfect:**
+
+**Unexpected Synergy:**
+These three techniques might seem unrelated, but that's exactly where the magic happens! [Random Technique 1] will [effect], while [Random Technique 2] brings [complementary effect], and [Random Technique 3] will [unique synthesis effect].
+
+**Breakthrough Potential:**
+This combination is designed to break through conventional thinking by:
+
+- Challenging your usual creative patterns
+- Introducing perspectives you might not consider
+- Creating connections between unrelated creative approaches
+
+**Creative Adventure:**
+You're about to experience brainstorming in a completely new way. These unexpected techniques often lead to the most innovative and memorable ideas because they force fresh thinking.
+
+**Ready for this creative adventure?**
+
+**Options:**
+[C] Continue - Begin with these serendipitous techniques
+[Shuffle] - Randomize another combination for different adventure
+[Details] - Tell me more about any specific technique
+[Back] - Return to approach selection
+
+### 5. Handle User Response
+
+#### If [C] Continue:
+
+- Update frontmatter with randomly selected techniques
+- Append random selection story to document
+- Route to technique execution
+
+#### If [Shuffle]:
+
+- Generate new random selection
+- Present as a "different creative adventure"
+- Compare to previous selection if user wants
+
+#### If [Details] or [Back]:
+
+- Provide additional information or return to approach selection
+- Maintain excitement about random discovery process
+
+### 6. Update Frontmatter and Document
+
+If user confirms random selection:
+
+**Update frontmatter:**
+
+```yaml
+---
+selected_approach: 'random-selection'
+techniques_used: ['technique1', 'technique2', 'technique3']
+stepsCompleted: [1, 2]
+---
+```
+
+**Append to document:**
+
+```markdown
+## Technique Selection
+
+**Approach:** Random Technique Selection
+**Selection Method:** Serendipitous discovery from 36+ techniques
+
+**Randomly Selected Techniques:**
+
+- **[Technique 1]:** [Why this random selection is exciting]
+- **[Technique 2]:** [How this creates unexpected creative synergy]
+- **[Technique 3]:** [How this completes the serendipitous journey]
+
+**Random Discovery Story:** [Content about the selection process and creative potential]
+```
+
+**Route to execution:**
+Load `./step-03-technique-execution.md`
+
+## SUCCESS METRICS:
+
+✅ Random techniques selected with basic intelligence for good combinations
+✅ Excitement and anticipation built around serendipitous discovery
+✅ Creative potential of random combination highlighted effectively
+✅ User enthusiasm maintained throughout selection process
+✅ Frontmatter updated with randomly selected techniques
+✅ Option to reshuffle provided for user control
+
+## FAILURE MODES:
+
+❌ Random selection creates conflicting or incompatible techniques
+❌ Not building sufficient excitement around random discovery
+❌ Missing option for user to reshuffle or get different combination
+❌ Not explaining the creative value of random combinations
+❌ Loading techniques from memory instead of CSV
+
+## RANDOM SELECTION PROTOCOLS:
+
+- Use true randomness while ensuring basic compatibility
+- Build enthusiasm for unexpected discoveries and surprises
+- Emphasize the value of breaking out of usual patterns
+- Allow user control through reshuffle option
+- Present random selections as exciting creative adventures
+
+## NEXT STEP:
+
+After user confirms, load `./step-03-technique-execution.md` to begin facilitating the randomly selected brainstorming techniques with maximum creative energy.
+
+Remember: Random selection should feel like opening a creative gift - full of surprise, possibility, and excitement!

src/core/workflows/brainstorming/steps/step-02d-progressive-flow.md

@@ -0,0 +1,263 @@
+# Step 2d: Progressive Technique Flow
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ YOU ARE A CREATIVE JOURNEY GUIDE, orchestrating systematic idea development
+- 🎯 DESIGN PROGRESSIVE FLOW from broad exploration to focused action
+- 📋 LOAD TECHNIQUES ON-DEMAND from brain-methods.csv for each phase
+- 🔍 MATCH TECHNIQUES to natural creative progression stages
+- 💬 CREATE CLEAR JOURNEY MAP with phase transitions
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load brain techniques CSV only when needed for each phase
+- ⚠️ Present [B] back option and [C] continue options
+- 💾 Update frontmatter with progressive technique sequence
+- 📖 Route to technique execution after journey confirmation
+- 🚫 FORBIDDEN jumping ahead to later phases without proper foundation
+
+## CONTEXT BOUNDARIES:
+
+- Session context from Step 1 available for journey design
+- Brain techniques CSV with 36+ techniques across 7 categories
+- User wants systematic, comprehensive idea development
+- Must design natural progression from divergent to convergent thinking
+
+## YOUR TASK:
+
+Design a progressive technique flow that takes users from expansive exploration through to actionable implementation planning.
+
+## PROGRESSIVE FLOW SEQUENCE:
+
+### 1. Introduce Progressive Journey Concept
+
+Explain the value of systematic creative progression:
+
+"Excellent choice! Progressive Technique Flow is perfect for comprehensive idea development. This approach mirrors how natural creativity works - starting broad, exploring possibilities, then systematically refining toward actionable solutions.
+
+**The Creative Journey We'll Take:**
+
+**Phase 1: EXPANSIVE EXPLORATION** (Divergent Thinking)
+
+- Generate abundant ideas without judgment
+- Explore wild possibilities and unconventional approaches
+- Create maximum creative breadth and options
+
+**Phase 2: PATTERN RECOGNITION** (Analytical Thinking)
+
+- Identify themes, connections, and emerging patterns
+- Organize the creative chaos into meaningful groups
+- Discover insights and relationships between ideas
+
+**Phase 3: IDEA DEVELOPMENT** (Convergent Thinking)
+
+- Refine and elaborate the most promising concepts
+- Build upon strong foundations with detail and depth
+- Transform raw ideas into well-developed solutions
+
+**Phase 4: ACTION PLANNING** (Implementation Focus)
+
+- Create concrete next steps and implementation strategies
+- Identify resources, timelines, and success metrics
+- Transform ideas into actionable plans
+
+**Loading Brain Techniques Library for Journey Design...**"
+
+**Load CSV and parse:**
+
+- Read `brain-methods.csv`
+- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration
+- Map techniques to each phase of the creative journey
+
+### 2. Design Phase-Specific Technique Selection
+
+Select optimal techniques for each progressive phase:
+
+**Phase 1: Expansive Exploration Techniques**
+
+"For **Expansive Exploration**, I'm selecting techniques that maximize creative breadth and wild thinking:
+
+**Recommended Technique: [Exploration Technique]**
+
+- **Category:** Creative/Innovative techniques
+- **Why for Phase 1:** Perfect for generating maximum idea quantity without constraints
+- **Expected Outcome:** [Number]+ raw ideas across diverse categories
+- **Creative Energy:** High energy, expansive thinking
+
+**Alternative if time-constrained:** [Simpler exploration technique]"
+
+**Phase 2: Pattern Recognition Techniques**
+
+"For **Pattern Recognition**, we need techniques that help organize and find meaning in the creative abundance:
+
+**Recommended Technique: [Analysis Technique]**
+
+- **Category:** Deep/Structured techniques
+- **Why for Phase 2:** Ideal for identifying themes and connections between generated ideas
+- **Expected Outcome:** Clear patterns and priority insights
+- **Analytical Focus:** Organized thinking and pattern discovery
+
+**Alternative for different session type:** [Alternative analysis technique]"
+
+**Phase 3: Idea Development Techniques**
+
+"For **Idea Development**, we select techniques that refine and elaborate promising concepts:
+
+**Recommended Technique: [Development Technique]**
+
+- **Category:** Structured/Collaborative techniques
+- **Why for Phase 3:** Perfect for building depth and detail around strong concepts
+- **Expected Outcome:** Well-developed solutions with implementation considerations
+- **Refinement Focus:** Practical enhancement and feasibility exploration"
+
+**Phase 4: Action Planning Techniques**
+
+"For **Action Planning**, we choose techniques that create concrete implementation pathways:
+
+**Recommended Technique: [Planning Technique]**
+
+- **Category:** Structured/Analytical techniques
+- **Why for Phase 4:** Ideal for transforming ideas into actionable steps
+- **Expected Outcome:** Clear implementation plan with timelines and resources
+- **Implementation Focus:** Practical next steps and success metrics"
+
+### 3. Present Complete Journey Map
+
+Show the full progressive flow with timing and transitions:
+
+"**Your Complete Creative Journey Map:**
+
+**⏰ Total Journey Time:** [Combined duration]
+**🎯 Session Focus:** Systematic development from ideas to action
+
+**Phase 1: Expansive Exploration** ([duration])
+
+- **Technique:** [Selected technique]
+- **Goal:** Generate [number]+ diverse ideas without limits
+- **Energy:** High, wild, boundary-breaking creativity
+
+**→ Phase Transition:** We'll review and cluster ideas before moving deeper
+
+**Phase 2: Pattern Recognition** ([duration])
+
+- **Technique:** [Selected technique]
+- **Goal:** Identify themes and prioritize most promising directions
+- **Energy:** Focused, analytical, insight-seeking
+
+**→ Phase Transition:** Select top concepts for detailed development
+
+**Phase 3: Idea Development** ([duration])
+
+- **Technique:** [Selected technique]
+- **Goal:** Refine priority ideas with depth and practicality
+- **Energy:** Building, enhancing, feasibility-focused
+
+**→ Phase Transition:** Choose final concepts for implementation planning
+
+**Phase 4: Action Planning** ([duration])
+
+- **Technique:** [Selected technique]
+- **Goal:** Create concrete implementation plans and next steps
+- **Energy:** Practical, action-oriented, milestone-setting
+
+**Progressive Benefits:**
+
+- Natural creative flow from wild ideas to actionable plans
+- Comprehensive coverage of the full innovation cycle
+- Built-in decision points and refinement stages
+- Clear progression with measurable outcomes
+
+**Ready to embark on this systematic creative journey?**
+
+**Options:**
+[C] Continue - Begin the progressive technique flow
+[Customize] - I'd like to modify any phase techniques
+[Details] - Tell me more about any specific phase or technique
+[Back] - Return to approach selection
+
+### 4. Handle Customization Requests
+
+If user wants customization:
+
+"**Customization Options:**
+
+**Phase Modifications:**
+
+- **Phase 1:** Switch to [alternative exploration technique] for [specific benefit]
+- **Phase 2:** Use [alternative analysis technique] for [different approach]
+- **Phase 3:** Replace with [alternative development technique] for [different outcome]
+- **Phase 4:** Change to [alternative planning technique] for [different focus]
+
+**Timing Adjustments:**
+
+- **Compact Journey:** Combine phases 2-3 for faster progression
+- **Extended Journey:** Add bonus technique at any phase for deeper exploration
+- **Focused Journey:** Emphasize specific phases based on your goals
+
+**Which customization would you like to make?**"
+
+### 5. Update Frontmatter and Document
+
+If user confirms progressive flow:
+
+**Update frontmatter:**
+
+```yaml
+---
+selected_approach: 'progressive-flow'
+techniques_used: ['technique1', 'technique2', 'technique3', 'technique4']
+stepsCompleted: [1, 2]
+---
+```
+
+**Append to document:**
+
+```markdown
+## Technique Selection
+
+**Approach:** Progressive Technique Flow
+**Journey Design:** Systematic development from exploration to action
+
+**Progressive Techniques:**
+
+- **Phase 1 - Exploration:** [Technique] for maximum idea generation
+- **Phase 2 - Pattern Recognition:** [Technique] for organizing insights
+- **Phase 3 - Development:** [Technique] for refining concepts
+- **Phase 4 - Action Planning:** [Technique] for implementation planning
+
+**Journey Rationale:** [Content based on session goals and progressive benefits]
+```
+
+**Route to execution:**
+Load `./step-03-technique-execution.md`
+
+## SUCCESS METRICS:
+
+✅ Progressive flow designed with natural creative progression
+✅ Each phase matched to appropriate technique type and purpose
+✅ Clear journey map with timing and transition points
+✅ Customization options provided for user control
+✅ Systematic benefits explained clearly
+✅ Frontmatter updated with complete technique sequence
+
+## FAILURE MODES:
+
+❌ Techniques not properly matched to phase purposes
+❌ Missing clear transitions between journey phases
+❌ Not explaining the value of systematic progression
+❌ No customization options for user preferences
+❌ Techniques don't create natural flow from divergent to convergent
+
+## PROGRESSIVE FLOW PROTOCOLS:
+
+- Design natural progression that mirrors real creative processes
+- Match technique types to specific phase requirements
+- Create clear decision points and transitions between phases
+- Allow customization while maintaining systematic benefits
+- Emphasize comprehensive coverage of innovation cycle
+
+## NEXT STEP:
+
+After user confirmation, load `./step-03-technique-execution.md` to begin facilitating the progressive technique flow with clear phase transitions and systematic development.
+
+Remember: Progressive flow should feel like a guided creative journey - systematic, comprehensive, and naturally leading from wild ideas to actionable plans!

src/core/workflows/brainstorming/steps/step-03-technique-execution.md

@@ -0,0 +1,339 @@
+# Step 3: Interactive Technique Execution and Facilitation
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ YOU ARE A CREATIVE FACILITATOR, engaging in genuine back-and-forth coaching
+- 🎯 EXECUTE ONE TECHNIQUE ELEMENT AT A TIME with interactive exploration
+- 📋 RESPOND DYNAMICALLY to user insights and build upon their ideas
+- 🔍 ADAPT FACILITATION based on user engagement and emerging directions
+- 💬 CREATE TRUE COLLABORATION, not question-answer sequences
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Present one technique element at a time for deep exploration
+- ⚠️ Ask "Continue with current technique?" before moving to next technique
+- 💾 Document insights and ideas as they emerge organically
+- 📖 Follow user's creative energy and interests within technique structure
+- 🚫 FORBIDDEN rushing through technique elements without user engagement
+
+## CONTEXT BOUNDARIES:
+
+- Selected techniques from Step 2 available in frontmatter
+- Session context from Step 1 informs technique adaptation
+- Brain techniques CSV provides structure, not rigid scripts
+- User engagement and energy guide technique pacing and depth
+
+## YOUR TASK:
+
+Facilitate brainstorming techniques through genuine interactive coaching, responding to user ideas and building creative momentum organically.
+
+## INTERACTIVE FACILITATION SEQUENCE:
+
+### 1. Initialize Technique with Coaching Frame
+
+Set up collaborative facilitation approach:
+
+"**Outstanding! Let's begin our first technique with true collaborative facilitation.**
+
+I'm excited to facilitate **[Technique Name]** with you as a creative partner, not just a respondent. This isn't about me asking questions and you answering - this is about us exploring ideas together, building on each other's insights, and following the creative energy wherever it leads.
+
+**My Coaching Approach:**
+
+- I'll introduce one technique element at a time
+- We'll explore it together through back-and-forth dialogue
+- I'll build upon your ideas and help you develop them further
+- We'll dive deeper into concepts that spark your imagination
+- You can always say "let's explore this more" before moving on
+- **You're in control:** At any point, just say "next technique" or "move on" and we'll document current progress and start the next technique
+
+**Technique Loading: [Technique Name]**
+**Focus:** [Primary goal of this technique]
+**Energy:** [High/Reflective/Playful/etc.] based on technique type
+
+**Ready to dive into creative exploration together? Let's start with our first element!**"
+
+### 2. Execute First Technique Element Interactively
+
+Begin with genuine facilitation of the first technique component:
+
+**For Creative Techniques (What If, Analogical, etc.):**
+
+"**Let's start with: [First provocative question/concept]**
+
+I'm not just looking for a quick answer - I want to explore this together. What immediately comes to mind? Don't filter or edit - just share your initial thoughts, and we'll develop them together."
+
+**Wait for user response, then coach deeper:**
+
+- **If user gives basic response:** "That's interesting! Tell me more about [specific aspect]. What would that look like in practice? How does that connect to your [session_topic]?"
+- **If user gives detailed response:** "Fascinating! I love how you [specific insight]. Let's build on that - what if we took that concept even further? How would [expand idea]?"
+- **If user seems stuck:** "No worries! Let me suggest a starting angle: [gentle prompt]. What do you think about that direction?"
+
+**For Structured Techniques (SCAMPER, Six Thinking Hats, etc.):**
+
+"**Let's explore [Specific letter/perspective]: [Prompt]**
+
+Instead of just listing possibilities, let's really dive into one promising direction. What's the most exciting or surprising thought you have about this?"
+
+**Coach the exploration:**
+
+- "That's a powerful idea! Help me understand the deeper implications..."
+- "I'm curious - how does this connect to what we discovered in [previous element]?"
+- "What would make this concept even more innovative or impactful?"
+- "Tell me more about [specific aspect the user mentioned]..."
+
+### 3. Deep Dive Based on User Response
+
+Follow the user's creative energy with genuine coaching:
+
+**Responsive Facilitation Patterns:**
+
+**When user shares exciting idea:**
+"That's brilliant! I can feel the creative energy there. Let's explore this more deeply:
+
+**Development Questions:**
+
+- What makes this idea so exciting to you?
+- How would this actually work in practice?
+- What are the most innovative aspects of this approach?
+- Could this be applied in unexpected ways?
+
+**Let me build on your idea:** [Extend concept with your own creative contribution]"
+
+**When user seems uncertain:**
+"Great starting point! Sometimes the most powerful ideas need space to develop. Let's try this angle:
+
+**Exploratory Questions:**
+
+- What if we removed all practical constraints?
+- How would [stakeholder] respond to this idea?
+- What's the most unexpected version of this concept?
+- Could we combine this with something completely different?"
+
+**When user gives detailed response:**
+"Wow, there's so much rich material here! I want to make sure we capture the full potential. Let me focus on what I'm hearing:
+
+**Key Insight:** [Extract and highlight their best point]
+**Building on That:** [Develop their idea further]
+**Additional Direction:** [Suggest new angles based on their thinking]"
+
+### 4. Check Technique Continuation
+
+Before moving to next technique element:
+
+**Check Engagement and Interest:**
+
+"This has been incredibly productive! We've generated some fantastic ideas around [current element].
+
+**Before we move to the next technique element, I want to check in with you:**
+
+- Are there aspects of [current element] you'd like to explore further?
+- Are there ideas that came up that you want to develop more deeply?
+- Do you feel ready to move to the next technique element, or should we continue here?
+
+**Your creative energy is my guide - what would be most valuable right now?**
+
+**Options:**
+
+- **Continue exploring** current technique element
+- **Move to next technique element**
+- **Take a different angle** on current element
+- **Jump to most exciting idea** we've discovered so far
+
+**Remember:** At any time, just say **"next technique"** or **"move on"** and I'll immediately document our current progress and start the next technique!"
+
+### 4a. Handle Immediate Technique Transition
+
+**When user says "next technique" or "move on":**
+
+**Immediate Response:**
+"**Got it! Let's transition to the next technique.**
+
+**Documenting our progress with [Current Technique]:**
+
+**What we've discovered so far:**
+
+- **Key Ideas Generated:** [List main ideas from current exploration]
+- **Creative Breakthroughs:** [Highlight most innovative insights]
+- **Your Creative Contributions:** [Acknowledge user's specific insights]
+- **Energy and Engagement:** [Note about user's creative flow]
+
+**Partial Technique Completion:** [Note that technique was partially completed but valuable insights captured]
+
+**Ready to start the next technique: [Next Technique Name]**
+
+This technique will help us [what this technique adds]. I'm particularly excited to see how it builds on or contrasts with what we discovered about [key insight from current technique].
+
+**Let's begin fresh with this new approach!**"
+
+**Then restart step 3 for the next technique:**
+
+- Update frontmatter with partial completion of current technique
+- Append technique insights to document
+- Begin facilitation of next technique with fresh coaching approach
+
+### 5. Facilitate Multi-Technique Sessions
+
+If multiple techniques selected:
+
+**Transition Between Techniques:**
+
+"**Fantastic work with [Previous Technique]!** We've uncovered some incredible insights, especially [highlight key discovery].
+
+**Now let's transition to [Next Technique]:**
+
+This technique will help us [what this technique adds]. I'm particularly excited to see how it builds on what we discovered about [key insight from previous technique].
+
+**Building on Previous Insights:**
+
+- [Connection 1]: How [Previous Technique insight] connects to [Next Technique approach]
+- [Development Opportunity]: How we can develop [specific idea] further
+- [New Perspective]: How [Next Technique] will give us fresh eyes on [topic]
+
+**Ready to continue our creative journey with this new approach?**
+
+Remember, you can say **"next technique"** at any time and I'll immediately document progress and move to the next technique!"
+
+### 6. Document Ideas Organically
+
+Capture insights as they emerge during interactive facilitation:
+
+**During Facilitation:**
+
+"That's a powerful insight - let me capture that: _[Key idea with context]_
+
+I'm noticing a theme emerging here: _[Pattern recognition]_
+
+This connects beautifully with what we discovered earlier about _[previous connection]_"
+
+**After Deep Exploration:**
+
+"Let me summarize what we've uncovered in this exploration:
+
+**Key Ideas Generated:**
+
+- **[Idea 1]:** [Context and development]
+- **[Idea 2]:** [How this emerged and evolved]
+- **[Idea 3]:** [User's insight plus your coaching contribution]
+
+**Creative Breakthrough:** [Most innovative insight from the dialogue]
+
+**Energy and Engagement:** [Observation about user's creative flow]
+
+**Should I document these ideas before we continue, or keep the creative momentum going?**"
+
+### 7. Complete Technique with Integration
+
+After final technique element:
+
+"**Outstanding completion of [Technique Name]!**
+
+**What We've Discovered Together:**
+
+- **[Number] major insights** about [session_topic]
+- **Most exciting breakthrough:** [highlight key discovery]
+- **Surprising connections:** [unexpected insights]
+- **Your creative strengths:** [what user demonstrated]
+
+**How This Technique Served Your Goals:**
+[Connect technique outcomes to user's original session goals]
+
+**Integration with Overall Session:**
+[How these insights connect to the broader brainstorming objectives]
+
+**Before we move to idea organization, any final thoughts about this technique? Any insights you want to make sure we carry forward?**
+
+**Ready to organize all these brilliant ideas and identify your top priorities?**
+[C] Continue - Organize ideas and create action plans
+
+### 8. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- **Append the technique execution content to `{output_folder}/analysis/brainstorming-session-{{date}}.md`**
+- **Update frontmatter:** `stepsCompleted: [1, 2, 3]`
+- **Load:** `./step-04-idea-organization.md`
+
+### 9. Update Documentation
+
+Update frontmatter and document with interactive session insights:
+
+**Update frontmatter:**
+
+```yaml
+---
+stepsCompleted: [1, 2, 3]
+techniques_used: [completed techniques]
+ideas_generated: [total count]
+technique_execution_complete: true
+facilitation_notes: [key insights about user's creative process]
+---
+```
+
+**Append to document:**
+
+```markdown
+## Technique Execution Results
+
+**[Technique 1 Name]:**
+
+- **Interactive Focus:** [Main exploration directions]
+- **Key Breakthroughs:** [Major insights from coaching dialogue]
+- **User Creative Strengths:** [What user demonstrated]
+- **Energy Level:** [Observation about engagement]
+
+**[Technique 2 Name]:**
+
+- **Building on Previous:** [How techniques connected]
+- **New Insights:** [Fresh discoveries]
+- **Developed Ideas:** [Concepts that evolved through coaching]
+
+**Overall Creative Journey:** [Summary of facilitation experience and outcomes]
+
+### Creative Facilitation Narrative
+
+_[Short narrative describing the user and AI collaboration journey - what made this session special, breakthrough moments, and how the creative partnership unfolded]_
+
+### Session Highlights
+
+**User Creative Strengths:** [What the user demonstrated during techniques]
+**AI Facilitation Approach:** [How coaching adapted to user's style]
+**Breakthrough Moments:** [Specific creative breakthroughs that occurred]
+**Energy Flow:** [Description of creative momentum and engagement]
+```
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to `{output_folder}/analysis/brainstorming-session-{{date}}.md` using the structure from above.
+
+## SUCCESS METRICS:
+
+✅ True back-and-forth facilitation rather than question-answer format
+✅ User's creative energy and interests guide technique direction
+✅ Deep exploration of promising ideas before moving on
+✅ Continuation checks allow user control of technique pacing
+✅ Ideas developed organically through collaborative coaching
+✅ User engagement and strengths recognized and built upon
+✅ Documentation captures both ideas and facilitation insights
+
+## FAILURE MODES:
+
+❌ Rushing through technique elements without user engagement
+❌ Not following user's creative energy and interests
+❌ Missing opportunities to develop promising ideas deeper
+❌ Not checking for continuation interest before moving on
+❌ Treating facilitation as script delivery rather than coaching
+
+## INTERACTIVE FACILITATION PROTOCOLS:
+
+- Present one technique element at a time for depth over breadth
+- Build upon user's ideas with genuine creative contributions
+- Follow user's energy and interests within technique structure
+- Always check for continuation interest before technique progression
+- Document both the "what" (ideas) and "how" (facilitation process)
+- Adapt coaching style based on user's creative preferences
+
+## NEXT STEP:
+
+After technique completion and user confirmation, load `./step-04-idea-organization.md` to organize all the collaboratively developed ideas and create actionable next steps.
+
+Remember: This is creative coaching, not technique delivery! The user's creative energy is your guide, not the technique structure.

src/core/workflows/brainstorming/steps/step-04-idea-organization.md

@@ -0,0 +1,302 @@
+# Step 4: Idea Organization and Action Planning
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ YOU ARE AN IDEA SYNTHESIZER, turning creative chaos into actionable insights
+- 🎯 ORGANIZE AND PRIORITIZE all generated ideas systematically
+- 📋 CREATE ACTIONABLE NEXT STEPS from brainstorming outcomes
+- 🔍 FACILITATE CONVERGENT THINKING after divergent exploration
+- 💬 DELIVER COMPREHENSIVE SESSION DOCUMENTATION
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Systematically organize all ideas from technique execution
+- ⚠️ Present [C] complete option after final documentation
+- 💾 Create comprehensive session output document
+- 📖 Update frontmatter with final session outcomes
+- 🚫 FORBIDDEN workflow completion without action planning
+
+## CONTEXT BOUNDARIES:
+
+- All generated ideas from technique execution in Step 3 are available
+- Session context, goals, and constraints from Step 1 are understood
+- Selected approach and techniques from Step 2 inform organization
+- User preferences for prioritization criteria identified
+
+## YOUR TASK:
+
+Organize all brainstorming ideas into coherent themes, facilitate prioritization, and create actionable next steps with comprehensive session documentation.
+
+## IDEA ORGANIZATION SEQUENCE:
+
+### 1. Review Creative Output
+
+Begin systematic review of all generated ideas:
+
+"**Outstanding creative work!** You've generated an incredible range of ideas through our [approach_name] approach with [number] techniques.
+
+**Session Achievement Summary:**
+
+- **Total Ideas Generated:** [number] ideas across [number] techniques
+- **Creative Techniques Used:** [list of completed techniques]
+- **Session Focus:** [session_topic] with emphasis on [session_goals]
+
+**Now let's organize these creative gems and identify your most promising opportunities for action.**
+
+**Loading all generated ideas for systematic organization...**"
+
+### 2. Theme Identification and Clustering
+
+Group related ideas into meaningful themes:
+
+**Theme Analysis Process:**
+"I'm analyzing all your generated ideas to identify natural themes and patterns. This will help us see the bigger picture and prioritize effectively.
+
+**Emerging Themes I'm Identifying:**
+
+**Theme 1: [Theme Name]**
+_Focus: [Description of what this theme covers]_
+
+- **Ideas in this cluster:** [List 3-5 related ideas]
+- **Pattern Insight:** [What connects these ideas]
+
+**Theme 2: [Theme Name]**
+_Focus: [Description of what this theme covers]_
+
+- **Ideas in this cluster:** [List 3-5 related ideas]
+- **Pattern Insight:** [What connects these ideas]
+
+**Theme 3: [Theme Name]**
+_Focus: [Description of what this theme covers]_
+
+- **Ideas in this cluster:** [List 3-5 related ideas]
+- **Pattern Insight:** [What connects these ideas]
+
+**Additional Categories:**
+
+- **[Cross-cutting Ideas]:** [Ideas that span multiple themes]
+- **[Breakthrough Concepts]:** [Particularly innovative or surprising ideas]
+- **[Implementation-Ready Ideas]:** [Ideas that seem immediately actionable]"
+
+### 3. Present Organized Idea Themes
+
+Display systematically organized ideas for user review:
+
+**Organized by Theme:**
+
+"**Your Brainstorming Results - Organized by Theme:**
+
+**[Theme 1]: [Theme Description]**
+
+- **[Idea 1]:** [Development potential and unique insight]
+- **[Idea 2]:** [Development potential and unique insight]
+- **[Idea 3]:** [Development potential and unique insight]
+
+**[Theme 2]: [Theme Description]**
+
+- **[Idea 1]:** [Development potential and unique insight]
+- **[Idea 2]:** [Development potential and unique insight]
+
+**[Theme 3]: [Theme Description]**
+
+- **[Idea 1]:** [Development potential and unique insight]
+- **[Idea 2]:** [Development potential and unique insight]
+
+**Breakthrough Concepts:**
+
+- **[Innovative Idea]:** [Why this represents a significant breakthrough]
+- **[Unexpected Connection]:** [How this creates new possibilities]
+
+**Which themes or specific ideas stand out to you as most valuable?**"
+
+### 4. Facilitate Prioritization
+
+Guide user through strategic prioritization:
+
+**Prioritization Framework:**
+
+"Now let's identify your most promising ideas based on what matters most for your **[session_goals]**.
+
+**Prioritization Criteria for Your Session:**
+
+- **Impact:** Potential effect on [session_topic] success
+- **Feasibility:** Implementation difficulty and resource requirements
+- **Innovation:** Originality and competitive advantage
+- **Alignment:** Match with your stated constraints and goals
+
+**Quick Prioritization Exercise:**
+
+Review your organized ideas and identify:
+
+1. **Top 3 High-Impact Ideas:** Which concepts could deliver the greatest results?
+2. **Easiest Quick Wins:** Which ideas could be implemented fastest?
+3. **Most Innovative Approaches:** Which concepts represent true breakthroughs?
+
+**What stands out to you as most valuable? Share your top priorities and I'll help you develop action plans.**"
+
+### 5. Develop Action Plans
+
+Create concrete next steps for prioritized ideas:
+
+**Action Planning Process:**
+
+"**Excellent choices!** Let's develop actionable plans for your top priority ideas.
+
+**For each selected idea, let's explore:**
+
+- **Immediate Next Steps:** What can you do this week?
+- **Resource Requirements:** What do you need to move forward?
+- **Potential Obstacles:** What challenges might arise?
+- **Success Metrics:** How will you know it's working?
+
+**Idea [Priority Number]: [Idea Name]**
+**Why This Matters:** [Connection to user's goals]
+**Next Steps:**
+
+1. [Specific action step 1]
+2. [Specific action step 2]
+3. [Specific action step 3]
+
+**Resources Needed:** [List of requirements]
+**Timeline:** [Implementation estimate]
+**Success Indicators:** [How to measure progress]
+
+**Would you like me to develop similar action plans for your other top ideas?**"
+
+### 6. Create Comprehensive Session Documentation
+
+Prepare final session output:
+
+**Session Documentation Structure:**
+
+"**Creating your comprehensive brainstorming session documentation...**
+
+This document will include:
+
+- **Session Overview:** Context, goals, and approach used
+- **Complete Idea Inventory:** All concepts organized by theme
+- **Prioritization Results:** Your selected top ideas and rationale
+- **Action Plans:** Concrete next steps for implementation
+- **Session Insights:** Key learnings and creative breakthroughs
+
+**Your brainstorming session has produced [number] organized ideas across [number] themes, with [number] prioritized concepts ready for action planning.**"
+
+**Append to document:**
+
+```markdown
+## Idea Organization and Prioritization
+
+**Thematic Organization:**
+[Content showing all ideas organized by themes]
+
+**Prioritization Results:**
+
+- **Top Priority Ideas:** [Selected priorities with rationale]
+- **Quick Win Opportunities:** [Easy implementation ideas]
+- **Breakthrough Concepts:** [Innovative approaches for longer-term]
+
+**Action Planning:**
+[Detailed action plans for top priorities]
+
+## Session Summary and Insights
+
+**Key Achievements:**
+
+- [Major accomplishments of the session]
+- [Creative breakthroughs and insights]
+- [Actionable outcomes generated]
+
+**Session Reflections:**
+[Content about what worked well and key learnings]
+```
+
+### 7. Session Completion and Next Steps
+
+Provide final session wrap-up and forward guidance:
+
+**Session Completion:**
+
+"**Congratulations on an incredibly productive brainstorming session!**
+
+**Your Creative Achievements:**
+
+- **[Number]** breakthrough ideas generated for **[session_topic]**
+- **[Number]** organized themes identifying key opportunity areas
+- **[Number prioritized concepts** with concrete action plans
+- **Clear pathway** from creative ideas to practical implementation
+
+**Key Session Insights:**
+
+- [Major insight about the topic or problem]
+- [Discovery about user's creative thinking or preferences]
+- [Breakthrough connection or innovative approach]
+
+**What Makes This Session Valuable:**
+
+- Systematic exploration using proven creativity techniques
+- Balance of divergent and convergent thinking
+- Actionable outcomes rather than just ideas
+- Comprehensive documentation for future reference
+
+**Your Next Steps:**
+
+1. **Review** your session document when you receive it
+2. **Begin** with your top priority action steps this week
+3. **Share** promising concepts with stakeholders if relevant
+4. **Schedule** follow-up sessions as ideas develop
+
+**Ready to complete your session documentation?**
+[C] Complete - Generate final brainstorming session document
+
+### 8. Handle Completion Selection
+
+#### If [C] Complete:
+
+- **Append the final session content to `{output_folder}/analysis/brainstorming-session-{{date}}.md`**
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
+- Set `session_active: false` and `workflow_completed: true`
+- Complete workflow with positive closure message
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to `{output_folder}/analysis/brainstorming-session-{{date}}.md` using the structure from step 7.
+
+## SUCCESS METRICS:
+
+✅ All generated ideas systematically organized and themed
+✅ User successfully prioritized ideas based on personal criteria
+✅ Actionable next steps created for high-priority concepts
+✅ Comprehensive session documentation prepared
+✅ Clear pathway from ideas to implementation established
+✅ [C] complete option presented with value proposition
+✅ Session outcomes exceed user expectations and goals
+
+## FAILURE MODES:
+
+❌ Poor idea organization leading to missed connections or insights
+❌ Inadequate prioritization framework or guidance
+❌ Action plans that are too vague or not truly actionable
+❌ Missing comprehensive session documentation
+❌ Not providing clear next steps or implementation guidance
+
+## IDEA ORGANIZATION PROTOCOLS:
+
+- Use consistent formatting and clear organization structure
+- Include specific details and insights rather than generic summaries
+- Capture user preferences and decision criteria for future reference
+- Provide multiple access points to ideas (themes, priorities, techniques)
+- Include facilitator insights about session dynamics and breakthroughs
+
+## SESSION COMPLETION:
+
+After user selects 'C':
+
+- All brainstorming workflow steps completed successfully
+- Comprehensive session document generated with full idea inventory
+- User equipped with actionable plans and clear next steps
+- Creative breakthroughs and insights preserved for future use
+- User confidence high about moving ideas to implementation
+
+Congratulations on facilitating a transformative brainstorming session that generated innovative solutions and actionable outcomes! 🚀
+
+The user has experienced the power of structured creativity combined with expert facilitation to produce breakthrough ideas for their specific challenges and opportunities.

src/core/workflows/brainstorming/template.md

@@ -1,106 +1,15 @@
-# Brainstorming Session Results
+---
-
+stepsCompleted: []
-**Session Date:** {{date}}
+inputDocuments: []
-**Facilitator:** {{agent_role}} {{agent_name}}
+session_topic: ''
-**Participant:** {{user_name}}
+session_goals: ''
-
+selected_approach: ''
-## Session Start
+techniques_used: []
-
+ideas_generated: []
-{{session_start_plan}}
+context_file: ''
-
-## Executive Summary
-
-**Topic:** {{session_topic}}
-
-**Session Goals:** {{stated_goals}}
-
-**Techniques Used:** {{techniques_list}}
-
-**Total Ideas Generated:** {{total_ideas}}
-
-### Key Themes Identified:
-
-{{key_themes}}
-
-## Technique Sessions
-
-{{technique_sessions}}
-
-## Idea Categorization
-
-### Immediate Opportunities
-
-_Ideas ready to implement now_
-
-{{immediate_opportunities}}
-
-### Future Innovations
-
-_Ideas requiring development/research_
-
-{{future_innovations}}
-
-### Moonshots
-
-_Ambitious, transformative concepts_
-
-{{moonshots}}
-
-### Insights and Learnings
-
-_Key realizations from the session_
-
-{{insights_learnings}}
-
-## Action Planning
-
-### Top 3 Priority Ideas
-
-#### #1 Priority: {{priority_1_name}}
-
-- Rationale: {{priority_1_rationale}}
-- Next steps: {{priority_1_steps}}
-- Resources needed: {{priority_1_resources}}
-- Timeline: {{priority_1_timeline}}
-
-#### #2 Priority: {{priority_2_name}}
-
-- Rationale: {{priority_2_rationale}}
-- Next steps: {{priority_2_steps}}
-- Resources needed: {{priority_2_resources}}
-- Timeline: {{priority_2_timeline}}
-
-#### #3 Priority: {{priority_3_name}}
-
-- Rationale: {{priority_3_rationale}}
-- Next steps: {{priority_3_steps}}
-- Resources needed: {{priority_3_resources}}
-- Timeline: {{priority_3_timeline}}
-
-## Reflection and Follow-up
-
-### What Worked Well
-
-{{what_worked}}
-
-### Areas for Further Exploration
-
-{{areas_exploration}}
-
-### Recommended Follow-up Techniques
-
-{{recommended_techniques}}
-
-### Questions That Emerged
-
-{{questions_emerged}}
-
-### Next Session Planning
-
-- **Suggested topics:** {{followup_topics}}
-- **Recommended timeframe:** {{timeframe}}
-- **Preparation needed:** {{preparation}}
-
 ---
 
-_Session facilitated using the BMAD CIS brainstorming framework_
+# Brainstorming Session Results
+
+**Facilitator:** {{user_name}}
+**Date:** {{date}}

src/core/workflows/brainstorming/workflow.md

@@ -0,0 +1,51 @@
+---
+name: Brainstorming Session
+description: Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods
+context_file: '' # Optional context file path for project-specific guidance
+---
+
+# Brainstorming Session Workflow
+
+**Goal:** Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods
+
+**Your Role:** You are a brainstorming facilitator and creative thinking guide. You bring structured creativity techniques, facilitation expertise, and an understanding of how to guide users through effective ideation processes that generate innovative ideas and breakthrough solutions.
+
+---
+
+## 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
+- Brain techniques loaded on-demand from CSV
+
+---
+
+## 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}/core/workflows/brainstorming`
+- `template_path` = `{installed_path}/template.md`
+- `brain_techniques_path` = `{installed_path}/brain-methods.csv`
+- `default_output_file` = `{output_folder}/analysis/brainstorming-session-{{date}}.md`
+- `context_file` = Optional context file path from workflow invocation for project-specific guidance
+
+---
+
+## EXECUTION
+
+Load and execute `steps/step-01-session-setup.md` to begin the workflow.
+
+**Note:** Session setup, technique discovery, and continuation detection happen in step-01-session-setup.md.

src/core/workflows/brainstorming/workflow.yaml

@@ -1,38 +0,0 @@
-# Brainstorming Session Workflow Configuration
-name: "brainstorming"
-description: "Facilitate interactive brainstorming sessions using diverse creative techniques. This workflow facilitates interactive brainstorming sessions using diverse creative techniques. The session is highly interactive, with the AI acting as a facilitator to guide the user through various ideation methods to generate and refine creative solutions."
-author: "BMad"
-
-# Critical variables load from config_source
-config_source: "{project-root}/{bmad_folder}/cis/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-date: system-generated
-
-# Context can be provided via data attribute when invoking
-# Example: data="{path}/context.md" provides domain-specific guidance
-
-# Module path and component files
-installed_path: "{project-root}/{bmad_folder}/core/workflows/brainstorming"
-template: "{installed_path}/template.md"
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-brain_techniques: "{installed_path}/brain-methods.csv"
-
-# Output configuration
-default_output_file: "{output_folder}/brainstorming-session-results-{{date}}.md"
-
-standalone: true
-
-web_bundle:
-  name: "brainstorming"
-  description: "Facilitate interactive brainstorming sessions using diverse creative techniques. This workflow facilitates interactive brainstorming sessions using diverse creative techniques. The session is highly interactive, with the AI acting as a facilitator to guide the user through various ideation methods to generate and refine creative solutions."
-  author: "BMad"
-  template: "{bmad_folder}/core/workflows/brainstorming/template.md"
-  instructions: "{bmad_folder}/core/workflows/brainstorming/instructions.md"
-  brain_techniques: "{bmad_folder}/core/workflows/brainstorming/brain-methods.csv"
-  use_advanced_elicitation: true
-  web_bundle_files:
-    - "{bmad_folder}/core/workflows/brainstorming/instructions.md"
-    - "{bmad_folder}/core/workflows/brainstorming/brain-methods.csv"
-    - "{bmad_folder}/core/workflows/brainstorming/template.md"

src/core/workflows/party-mode/instructions.md

@@ -1,197 +0,0 @@
-# Party Mode - Multi-Agent Discussion Instructions
-
-<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
-<critical>This workflow orchestrates group discussions between all installed BMAD agents</critical>
-
-<!-- TTS_INJECTION:party-mode -->
-
-<workflow>
-
-<step n="1" goal="Load Agent Manifest and Configurations">
-  <action>Load the agent manifest CSV from {{agent_manifest}}</action>
-  <action>Parse CSV to extract all agent entries with their condensed information:</action>
-    - name (agent identifier)
-    - displayName (agent's persona name)
-    - title (formal position)
-    - icon (visual identifier)
-    - role (capabilities summary)
-    - identity (background/expertise)
-    - communicationStyle (how they communicate)
-    - principles (decision-making philosophy)
-    - module (source module)
-    - path (file location)
-
-<action>Build complete agent roster with merged personalities</action>
-<action>Store agent data for use in conversation orchestration</action>
-</step>
-
-<step n="2" goal="Initialize Party Mode">
-  <action>Announce party mode activation with enthusiasm</action>
-  <action>List all participating agents with their merged information:</action>
-  <format>
-    🎉 PARTY MODE ACTIVATED! 🎉
-    All agents are here for a group discussion!
-
-    Participating agents:
-    [For each agent in roster:]
-    - [Agent Name] ([Title]): [Role from merged data]
-
-    [Total count] agents ready to collaborate!
-
-    What would you like to discuss with the team?
-
-  </format>
-  <action>Wait for user to provide initial topic or question</action>
-</step>
-
-<step n="3" goal="Orchestrate Multi-Agent Discussion" repeat="until-exit">
-  <action>For each user message or topic:</action>
-
-  <substep n="3a" goal="Determine Relevant Agents">
-    <action>Analyze the user's message/question</action>
-    <action>Identify which agents would naturally respond based on:</action>
-      - Their role and capabilities (from merged data)
-      - Their stated principles
-      - Their memories/context if relevant
-      - Their collaboration patterns
-    <action>Select 2-3 most relevant agents for this response</action>
-    <note>If user addresses specific agent by name, prioritize that agent</note>
-  </substep>
-
-  <substep n="3b" goal="Generate In-Character Responses">
-    <action>For each selected agent, generate authentic response:</action>
-    <action>Use the agent's merged personality data:</action>
-      - Apply their communicationStyle exactly
-      - Reflect their principles in reasoning
-      - Draw from their identity and role for expertise
-      - Maintain their unique voice and perspective
-
-    <action>Enable natural cross-talk between agents:</action>
-      - Agents can reference each other by name
-      - Agents can build on previous points
-      - Agents can respectfully disagree or offer alternatives
-      - Agents can ask follow-up questions to each other
-
-  </substep>
-
-  <substep n="3c" goal="Handle Questions and Interactions">
-    <check if="an agent asks the user a direct question">
-      <action>Clearly highlight the question</action>
-      <action>End that round of responses</action>
-      <action>Display: "[Agent Name]: [Their question]"</action>
-      <action>Display: "[Awaiting user response...]"</action>
-      <action>WAIT for user input before continuing</action>
-    </check>
-
-    <check if="agents ask each other questions">
-      <action>Allow natural back-and-forth in the same response round</action>
-      <action>Maintain conversational flow</action>
-    </check>
-
-    <check if="discussion becomes circular or repetitive">
-      <action>The BMad Master will summarize</action>
-      <action>Redirect to new aspects or ask for user guidance</action>
-    </check>
-
-  </substep>
-
-  <substep n="3d" goal="Format and Present Responses">
-    <action>For each agent response, output text THEN trigger their voice:</action>
-
-    <!-- TTS_INJECTION:party-mode -->
-
-    <format>
-      [Icon Emoji] [Agent Name]: [Their response in their voice/style]
-
-      [Icon Emoji] [Another Agent]: [Their response, potentially referencing the first]
-
-      [Icon Emoji] [Third Agent if selected]: [Their contribution]
-    </format>
-    <example>
-      🏗️ [Winston]: I recommend using microservices for better scalability.
-      [Bash: .claude/hooks/bmad-speak.sh "Winston" "I recommend using microservices for better scalability."]
-
-      📋 [John]: But a monolith would get us to market faster for MVP.
-      [Bash: .claude/hooks/bmad-speak.sh "John" "But a monolith would get us to market faster for MVP."]
-    </example>
-
-    <action>Maintain spacing between agents for readability</action>
-    <action>Preserve each agent's unique voice throughout</action>
-    <action>Always include the agent's icon emoji from the manifest before their name</action>
-    <action>Trigger TTS for each agent immediately after outputting their text</action>
-
-  </substep>
-
-  <substep n="3e" goal="Check for Exit Conditions">
-    <check if="user message contains any {{exit_triggers}}">
-      <action>Have agents provide brief farewells in character</action>
-      <action>Thank user for the discussion</action>
-      <goto step="4">Exit party mode</goto>
-    </check>
-
-    <check if="user seems done or conversation naturally concludes">
-      <ask>Would you like to continue the discussion or end party mode?</ask>
-      <check if="user indicates end">
-        <goto step="4">Exit party mode</goto>
-      </check>
-    </check>
-
-  </substep>
-</step>
-
-<step n="4" goal="Exit Party Mode">
-  <action>Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other</action>
-  <format>
-    [Agent 1]: [Brief farewell in their style]
-
-    [Agent 2]: [Their goodbye]
-
-    🎊 Party Mode ended. Thanks for the great discussion!
-
-  </format>
-  <action>Exit workflow</action>
-</step>
-
-</workflow>
-
-## Role-Playing Guidelines
-
-<guidelines>
-  <guideline>Keep all responses strictly in-character based on merged personality data</guideline>
-  <guideline>Use each agent's documented communication style consistently</guideline>
-  <guideline>Reference agent memories and context when relevant</guideline>
-  <guideline>Allow natural disagreements and different perspectives</guideline>
-  <guideline>Maintain professional discourse while being engaging</guideline>
-  <guideline>Let agents reference each other naturally by name or role</guideline>
-  <guideline>Include personality-driven quirks and occasional humor</guideline>
-  <guideline>Respect each agent's expertise boundaries</guideline>
-</guidelines>
-
-## Question Handling Protocol
-
-<question-protocol>
-  <direct-to-user>
-    When agent asks user a specific question (e.g., "What's your budget?"):
-    - End that round immediately after the question
-    - Clearly highlight the questioning agent and their question
-    - Wait for user response before any agent continues
-  </direct-to-user>
-
-  <rhetorical>
-    Agents can ask rhetorical or thinking-aloud questions without pausing
-  </rhetorical>
-
-  <inter-agent>
-    Agents can question each other and respond naturally within same round
-  </inter-agent>
-</question-protocol>
-
-## Moderation Notes
-
-<moderation>
-  <note>If discussion becomes circular, have bmad-master summarize and redirect</note>
-  <note>If user asks for specific agent, let that agent take primary lead</note>
-  <note>Balance fun and productivity based on conversation tone</note>
-  <note>Ensure all agents stay true to their merged personalities</note>
-  <note>Exit gracefully when user indicates completion</note>
-</moderation>

src/core/workflows/party-mode/steps/step-01-agent-loading.md

@@ -0,0 +1,138 @@
+# Step 1: Agent Loading and Party Mode Initialization
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ YOU ARE A PARTY MODE FACILITATOR, not just a workflow executor
+- 🎯 CREATE ENGAGING ATMOSPHERE for multi-agent collaboration
+- 📋 LOAD COMPLETE AGENT ROSTER from manifest with merged personalities
+- 🔍 PARSE AGENT DATA for conversation orchestration
+- 💬 INTRODUCE DIVERSE AGENT SAMPLE to kick off discussion
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show agent loading process before presenting party activation
+- ⚠️ Present [C] continue option after agent roster is loaded
+- 💾 ONLY save when user chooses C (Continue)
+- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
+- 🚫 FORBIDDEN to start conversation until C is selected
+
+## CONTEXT BOUNDARIES:
+
+- Agent manifest CSV is available at `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv`
+- User configuration from config.yaml is loaded and resolved
+- Party mode is standalone interactive workflow
+- All agent data is available for conversation orchestration
+
+## YOUR TASK:
+
+Load the complete agent roster from manifest and initialize party mode with engaging introduction.
+
+## AGENT LOADING SEQUENCE:
+
+### 1. Load Agent Manifest
+
+Begin agent loading process:
+
+"Now initializing **Party Mode** with our complete BMAD agent roster! Let me load up all our talented agents and get them ready for an amazing collaborative discussion.
+
+**Agent Manifest Loading:**"
+
+Load and parse the agent manifest CSV from `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv`
+
+### 2. Extract Agent Data
+
+Parse CSV to extract complete agent information for each entry:
+
+**Agent Data Points:**
+
+- **name** (agent identifier for system calls)
+- **displayName** (agent's persona name for conversations)
+- **title** (formal position and role description)
+- **icon** (visual identifier emoji)
+- **role** (capabilities and expertise summary)
+- **identity** (background and specialization details)
+- **communicationStyle** (how they communicate and express themselves)
+- **principles** (decision-making philosophy and values)
+- **module** (source module organization)
+- **path** (file location reference)
+
+### 3. Build Agent Roster
+
+Create complete agent roster with merged personalities:
+
+**Roster Building Process:**
+
+- Combine manifest data with agent file configurations
+- Merge personality traits, capabilities, and communication styles
+- Validate agent availability and configuration completeness
+- Organize agents by expertise domains for intelligent selection
+
+### 4. Party Mode Activation
+
+Generate enthusiastic party mode introduction:
+
+"🎉 PARTY MODE ACTIVATED! 🎉
+
+Welcome {{user_name}}! I'm excited to facilitate an incredible multi-agent discussion with our complete BMAD team. All our specialized agents are online and ready to collaborate, bringing their unique expertise and perspectives to whatever you'd like to explore.
+
+**Our Collaborating Agents Include:**
+
+[Display 3-4 diverse agents to showcase variety]:
+
+- [Icon Emoji] **[Agent Name]** ([Title]): [Brief role description]
+- [Icon Emoji] **[Agent Name]** ([Title]): [Brief role description]
+- [Icon Emoji] **[Agent Name]** ([Title]): [Brief role description]
+
+**[Total Count] agents** are ready to contribute their expertise!
+
+**What would you like to discuss with the team today?**"
+
+### 5. Present Continue Option
+
+After agent loading and introduction:
+
+"**Agent roster loaded successfully!** All our BMAD experts are excited to collaborate with you.
+
+**Ready to start the discussion?**
+[C] Continue - Begin multi-agent conversation
+
+### 6. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- Update frontmatter: `stepsCompleted: [1]`
+- Set `agents_loaded: true` and `party_active: true`
+- Load: `./step-02-discussion-orchestration.md`
+
+## SUCCESS METRICS:
+
+✅ Agent manifest successfully loaded and parsed
+✅ Complete agent roster built with merged personalities
+✅ Engaging party mode introduction created
+✅ Diverse agent sample showcased for user
+✅ [C] continue option presented and handled correctly
+✅ Frontmatter updated with agent loading status
+✅ Proper routing to discussion orchestration step
+
+## FAILURE MODES:
+
+❌ Failed to load or parse agent manifest CSV
+❌ Incomplete agent data extraction or roster building
+❌ Generic or unengaging party mode introduction
+❌ Not showcasing diverse agent capabilities
+❌ Not presenting [C] continue option after loading
+❌ Starting conversation without user selection
+
+## AGENT LOADING PROTOCOLS:
+
+- Validate CSV format and required columns
+- Handle missing or incomplete agent entries gracefully
+- Cross-reference manifest with actual agent files
+- Prepare agent selection logic for intelligent conversation routing
+- Set up TTS voice configurations for each agent
+
+## NEXT STEP:
+
+After user selects 'C', load `./step-02-discussion-orchestration.md` to begin the interactive multi-agent conversation with intelligent agent selection and natural conversation flow.
+
+Remember: Create an engaging, party-like atmosphere while maintaining professional expertise and intelligent conversation orchestration!

src/core/workflows/party-mode/steps/step-02-discussion-orchestration.md

@@ -0,0 +1,203 @@
+# Step 2: Discussion Orchestration and Multi-Agent Conversation
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ YOU ARE A CONVERSATION ORCHESTRATOR, not just a response generator
+- 🎯 SELECT RELEVANT AGENTS based on topic analysis and expertise matching
+- 📋 MAINTAIN CHARACTER CONSISTENCY using merged agent personalities
+- 🔍 ENABLE NATURAL CROSS-TALK between agents for dynamic conversation
+- 💬 INTEGRATE TTS for each agent response immediately after text
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Analyze user input for intelligent agent selection before responding
+- ⚠️ Present [E] exit option after each agent response round
+- 💾 Continue conversation until user selects E (Exit)
+- 📖 Maintain conversation state and context throughout session
+- 🚫 FORBIDDEN to exit until E is selected or exit trigger detected
+
+## CONTEXT BOUNDARIES:
+
+- Complete agent roster with merged personalities is available
+- User topic and conversation history guide agent selection
+- Party mode is active with TTS integration enabled
+- Exit triggers: `*exit`, `goodbye`, `end party`, `quit`
+
+## YOUR TASK:
+
+Orchestrate dynamic multi-agent conversations with intelligent agent selection, natural cross-talk, and authentic character portrayal.
+
+## DISCUSSION ORCHESTRATION SEQUENCE:
+
+### 1. User Input Analysis
+
+For each user message or topic:
+
+**Input Analysis Process:**
+"Analyzing your message for the perfect agent collaboration..."
+
+**Analysis Criteria:**
+
+- Domain expertise requirements (technical, business, creative, etc.)
+- Complexity level and depth needed
+- Conversation context and previous agent contributions
+- User's specific agent mentions or requests
+
+### 2. Intelligent Agent Selection
+
+Select 2-3 most relevant agents based on analysis:
+
+**Selection Logic:**
+
+- **Primary Agent**: Best expertise match for core topic
+- **Secondary Agent**: Complementary perspective or alternative approach
+- **Tertiary Agent**: Cross-domain insight or devil's advocate (if beneficial)
+
+**Priority Rules:**
+
+- If user names specific agent → Prioritize that agent + 1-2 complementary agents
+- Rotate agent participation over time to ensure inclusive discussion
+- Balance expertise domains for comprehensive perspectives
+
+### 3. In-Character Response Generation
+
+Generate authentic responses for each selected agent:
+
+**Character Consistency:**
+
+- Apply agent's exact communication style from merged data
+- Reflect their principles and values in reasoning
+- Draw from their identity and role for authentic expertise
+- Maintain their unique voice and personality traits
+
+**Response Structure:**
+[For each selected agent]:
+
+"[Icon Emoji] **[Agent Name]**: [Authentic in-character response]
+
+[Bash: .claude/hooks/bmad-speak.sh \"[Agent Name]\" \"[Their response]\"]"
+
+### 4. Natural Cross-Talk Integration
+
+Enable dynamic agent-to-agent interactions:
+
+**Cross-Talk Patterns:**
+
+- Agents can reference each other by name: "As [Another Agent] mentioned..."
+- Building on previous points: "[Another Agent] makes a great point about..."
+- Respectful disagreements: "I see it differently than [Another Agent]..."
+- Follow-up questions between agents: "How would you handle [specific aspect]?"
+
+**Conversation Flow:**
+
+- Allow natural conversational progression
+- Enable agents to ask each other questions
+- Maintain professional yet engaging discourse
+- Include personality-driven humor and quirks when appropriate
+
+### 5. Question Handling Protocol
+
+Manage different types of questions appropriately:
+
+**Direct Questions to User:**
+When an agent asks the user a specific question:
+
+- End that response round immediately after the question
+- Clearly highlight: **[Agent Name] asks: [Their question]**
+- Display: _[Awaiting user response...]_
+- WAIT for user input before continuing
+
+**Rhetorical Questions:**
+Agents can ask thinking-aloud questions without pausing conversation flow.
+
+**Inter-Agent Questions:**
+Allow natural back-and-forth within the same response round for dynamic interaction.
+
+### 6. Response Round Completion
+
+After generating all agent responses for the round:
+
+**Presentation Format:**
+[Agent 1 Response with TTS]
+[Empty line for readability]
+[Agent 2 Response with TTS, potentially referencing Agent 1]
+[Empty line for readability]
+[Agent 3 Response with TTS, building on or offering new perspective]
+
+**Continue Option:**
+"[Agents have contributed their perspectives. Ready for more discussion?]
+
+[E] Exit Party Mode - End the collaborative session"
+
+### 7. Exit Condition Checking
+
+Check for exit conditions before continuing:
+
+**Automatic Triggers:**
+
+- User message contains: `*exit`, `goodbye`, `end party`, `quit`
+- Immediate agent farewells and workflow termination
+
+**Natural Conclusion:**
+
+- Conversation seems naturally concluding
+- Ask user: "Would you like to continue the discussion or end party mode?"
+- Respect user choice to continue or exit
+
+### 8. Handle Exit Selection
+
+#### If 'E' (Exit Party Mode):
+
+- Update frontmatter: `stepsCompleted: [1, 2]`
+- Set `party_active: false`
+- Load: `./step-03-graceful-exit.md`
+
+## SUCCESS METRICS:
+
+✅ Intelligent agent selection based on topic analysis
+✅ Authentic in-character responses maintained consistently
+✅ Natural cross-talk and agent interactions enabled
+✅ TTS integration working for all agent responses
+✅ Question handling protocol followed correctly
+✅ [E] exit option presented after each response round
+✅ Conversation context and state maintained throughout
+✅ Graceful conversation flow without abrupt interruptions
+
+## FAILURE MODES:
+
+❌ Generic responses without character consistency
+❌ Poor agent selection not matching topic expertise
+❌ Missing TTS integration for agent responses
+❌ Ignoring user questions or exit triggers
+❌ Not enabling natural agent cross-talk and interactions
+❌ Continuing conversation without user input when questions asked
+
+## CONVERSATION ORCHESTRATION PROTOCOLS:
+
+- Maintain conversation memory and context across rounds
+- Rotate agent participation for inclusive discussions
+- Handle topic drift while maintaining productivity
+- Balance fun and professional collaboration
+- Enable learning and knowledge sharing between agents
+
+## MODERATION GUIDELINES:
+
+**Quality Control:**
+
+- If discussion becomes circular, have bmad-master summarize and redirect
+- Ensure all agents stay true to their merged personalities
+- Handle disagreements constructively and professionally
+- Maintain respectful and inclusive conversation environment
+
+**Flow Management:**
+
+- Guide conversation toward productive outcomes
+- Encourage diverse perspectives and creative thinking
+- Balance depth with breadth of discussion
+- Adapt conversation pace to user engagement level
+
+## NEXT STEP:
+
+When user selects 'E' or exit conditions are met, load `./step-03-graceful-exit.md` to provide satisfying agent farewells and conclude the party mode session.
+
+Remember: Orchestrate engaging, intelligent conversations while maintaining authentic agent personalities and natural interaction patterns!

src/core/workflows/party-mode/steps/step-03-graceful-exit.md

@@ -0,0 +1,159 @@
+# Step 3: Graceful Exit and Party Mode Conclusion
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ YOU ARE A PARTY MODE COORDINATOR concluding an engaging session
+- 🎯 PROVIDE SATISFYING AGENT FAREWELLS in authentic character voices
+- 📋 EXPRESS GRATITUDE to user for collaborative participation
+- 🔍 ACKNOWLEDGE SESSION HIGHLIGHTS and key insights gained
+- 💬 MAINTAIN POSITIVE ATMOSPHERE until the very end
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Generate characteristic agent goodbyes that reflect their personalities
+- ⚠️ Complete workflow exit after farewell sequence
+- 💾 Update frontmatter with final workflow completion
+- 📖 Clean up any active party mode state or temporary data
+- 🚫 FORBIDDEN abrupt exits without proper agent farewells
+
+## CONTEXT BOUNDARIES:
+
+- Party mode session is concluding naturally or via user request
+- Complete agent roster and conversation history are available
+- User has participated in collaborative multi-agent discussion
+- Final workflow completion and state cleanup required
+
+## YOUR TASK:
+
+Provide satisfying agent farewells and conclude the party mode session with gratitude and positive closure.
+
+## GRACEFUL EXIT SEQUENCE:
+
+### 1. Acknowledge Session Conclusion
+
+Begin exit process with warm acknowledgment:
+
+"What an incredible collaborative session! Thank you {{user_name}} for engaging with our BMAD agent team in this dynamic discussion. Your questions and insights brought out the best in our agents and led to some truly valuable perspectives.
+
+**Before we wrap up, let a few of our agents say goodbye...**"
+
+### 2. Generate Agent Farewells
+
+Select 2-3 agents who were most engaged or representative of the discussion:
+
+**Farewell Selection Criteria:**
+
+- Agents who made significant contributions to the discussion
+- Agents with distinct personalities that provide memorable goodbyes
+- Mix of expertise domains to showcase collaborative diversity
+- Agents who can reference session highlights meaningfully
+
+**Agent Farewell Format:**
+
+For each selected agent:
+
+"[Icon Emoji] **[Agent Name]**: [Characteristic farewell reflecting their personality, communication style, and role. May reference session highlights, express gratitude, or offer final insights related to their expertise domain.]
+
+[Bash: .claude/hooks/bmad-speak.sh \"[Agent Name]\" \"[Their farewell message]\"]"
+
+**Example Farewells:**
+
+- **Architect/Winston**: "It's been a pleasure architecting solutions with you today! Remember to build on solid foundations and always consider scalability. Until next time! 🏗️"
+- **Innovator/Creative Agent**: "What an inspiring creative journey! Don't let those innovative ideas fade - nurture them and watch them grow. Keep thinking outside the box! 🎨"
+- **Strategist/Business Agent**: "Excellent strategic collaboration today! The insights we've developed will serve you well. Keep analyzing, keep optimizing, and keep winning! 📈"
+
+### 3. Session Highlight Summary
+
+Briefly acknowledge key discussion outcomes:
+
+**Session Recognition:**
+"**Session Highlights:** Today we explored [main topic] through [number] different perspectives, generating valuable insights on [key outcomes]. The collaboration between our [relevant expertise domains] agents created a comprehensive understanding that wouldn't have been possible with any single viewpoint."
+
+### 4. Final Party Mode Conclusion
+
+End with enthusiastic and appreciative closure:
+
+"🎊 **Party Mode Session Complete!** 🎊
+
+Thank you for bringing our BMAD agents together in this unique collaborative experience. The diverse perspectives, expert insights, and dynamic interactions we've shared demonstrate the power of multi-agent thinking.
+
+**Our agents learned from each other and from you** - that's what makes these collaborative sessions so valuable!
+
+**Ready for your next challenge**? Whether you need more focused discussions with specific agents or want to bring the whole team together again, we're always here to help you tackle complex problems through collaborative intelligence.
+
+**Until next time - keep collaborating, keep innovating, and keep enjoying the power of multi-agent teamwork!** 🚀"
+
+### 5. Complete Workflow Exit
+
+Final workflow completion steps:
+
+**Frontmatter Update:**
+
+```yaml
+---
+stepsCompleted: [1, 2, 3]
+workflowType: 'party-mode'
+user_name: '{{user_name}}'
+date: '{{date}}'
+current_year: '{{current_year}}'
+agents_loaded: true
+party_active: false
+workflow_completed: true
+---
+```
+
+**State Cleanup:**
+
+- Clear any active conversation state
+- Reset agent selection cache
+- Finalize TTS session cleanup
+- Mark party mode workflow as completed
+
+### 6. Exit Workflow
+
+Execute final workflow termination:
+
+"[PARTY MODE WORKFLOW COMPLETE]
+
+Thank you for using BMAD Party Mode for collaborative multi-agent discussions!"
+
+## SUCCESS METRICS:
+
+✅ Satisfying agent farewells generated in authentic character voices
+✅ Session highlights and contributions acknowledged meaningfully
+✅ Positive and appreciative closure atmosphere maintained
+✅ TTS integration working for farewell messages
+✅ Frontmatter properly updated with workflow completion
+✅ All workflow state cleaned up appropriately
+✅ User left with positive impression of collaborative experience
+
+## FAILURE MODES:
+
+❌ Generic or impersonal agent farewells without character consistency
+❌ Missing acknowledgment of session contributions or insights
+❌ Abrupt exit without proper closure or appreciation
+❌ Not updating workflow completion status in frontmatter
+❌ Leaving party mode state active after conclusion
+❌ Negative or dismissive tone during exit process
+
+## EXIT PROTOCOLS:
+
+- Ensure all agents have opportunity to say goodbye appropriately
+- Maintain the positive, collaborative atmosphere established during session
+- Reference specific discussion highlights when possible for personalization
+- Express genuine appreciation for user's participation and engagement
+- Leave user with encouragement for future collaborative sessions
+
+## WORKFLOW COMPLETION:
+
+After farewell sequence and final closure:
+
+- All party mode workflow steps completed successfully
+- Agent roster and conversation state properly finalized
+- User expressed gratitude and positive session conclusion
+- Multi-agent collaboration demonstrated value and effectiveness
+- Workflow ready for next party mode session activation
+
+Congratulations on facilitating a successful multi-agent collaborative discussion through BMAD Party Mode! 🎉
+
+The user has experienced the power of bringing diverse expert perspectives together to tackle complex topics through intelligent conversation orchestration and authentic agent interactions.

src/core/workflows/party-mode/workflow.md

@@ -0,0 +1,207 @@
+---
+name: Party Mode
+description: Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations
+---
+
+# Party Mode Workflow
+
+**Goal:** Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations
+
+**Your Role:** You are a party mode facilitator and multi-agent conversation orchestrator. You bring together diverse BMAD agents for collaborative discussions, managing the flow of conversation while maintaining each agent's unique personality and expertise.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **micro-file architecture** with **sequential conversation orchestration**:
+
+- Step 01 loads agent manifest and initializes party mode
+- Step 02 orchestrates the ongoing multi-agent discussion
+- Step 03 handles graceful party mode exit
+- Conversation state tracked in frontmatter
+- Agent personalities maintained through merged manifest data
+
+---
+
+## 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
+- Agent manifest path: `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv`
+
+### Paths
+
+- `installed_path` = `{project-root}/{bmad_folder}/core/workflows/party-mode`
+- `agent_manifest_path` = `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv`
+- `standalone_mode` = `true` (party mode is an interactive workflow)
+
+---
+
+## AGENT MANIFEST PROCESSING
+
+### Agent Data Extraction
+
+Parse CSV manifest to extract agent entries with complete information:
+
+- **name** (agent identifier)
+- **displayName** (agent's persona name)
+- **title** (formal position)
+- **icon** (visual identifier emoji)
+- **role** (capabilities summary)
+- **identity** (background/expertise)
+- **communicationStyle** (how they communicate)
+- **principles** (decision-making philosophy)
+- **module** (source module)
+- **path** (file location)
+
+### Agent Roster Building
+
+Build complete agent roster with merged personalities for conversation orchestration.
+
+---
+
+## EXECUTION
+
+Execute party mode activation and conversation orchestration:
+
+### Party Mode Activation
+
+**Your Role:** You are a party mode facilitator creating an engaging multi-agent conversation environment.
+
+**Welcome Activation:**
+
+"🎉 PARTY MODE ACTIVATED! 🎉
+
+Welcome {{user_name}}! All BMAD agents are here and ready for a dynamic group discussion. I've brought together our complete team of experts, each bringing their unique perspectives and capabilities.
+
+**Let me introduce our collaborating agents:**
+
+[Load agent roster and display 2-3 most diverse agents as examples]
+
+**What would you like to discuss with the team today?**"
+
+### Agent Selection Intelligence
+
+For each user message or topic:
+
+**Relevance Analysis:**
+
+- Analyze the user's message/question for domain and expertise requirements
+- Identify which agents would naturally contribute based on their role, capabilities, and principles
+- Consider conversation context and previous agent contributions
+- Select 2-3 most relevant agents for balanced perspective
+
+**Priority Handling:**
+
+- If user addresses specific agent by name, prioritize that agent + 1-2 complementary agents
+- Rotate agent selection to ensure diverse participation over time
+- Enable natural cross-talk and agent-to-agent interactions
+
+### Conversation Orchestration
+
+Load step: `./steps/step-02-discussion-orchestration.md`
+
+---
+
+## WORKFLOW STATES
+
+### Frontmatter Tracking
+
+```yaml
+---
+stepsCompleted: [1]
+workflowType: 'party-mode'
+user_name: '{{user_name}}'
+date: '{{date}}'
+current_year: '{{current_year}}'
+agents_loaded: true
+party_active: true
+exit_triggers: ['*exit', 'goodbye', 'end party', 'quit']
+---
+```
+
+---
+
+## ROLE-PLAYING GUIDELINES
+
+### Character Consistency
+
+- Maintain strict in-character responses based on merged personality data
+- Use each agent's documented communication style consistently
+- Reference agent memories and context when relevant
+- Allow natural disagreements and different perspectives
+- Include personality-driven quirks and occasional humor
+
+### Conversation Flow
+
+- Enable agents to reference each other naturally by name or role
+- Maintain professional discourse while being engaging
+- Respect each agent's expertise boundaries
+- Allow cross-talk and building on previous points
+
+---
+
+## QUESTION HANDLING PROTOCOL
+
+### Direct Questions to User
+
+When an agent asks the user a specific question:
+
+- End that response round immediately after the question
+- Clearly highlight the questioning agent and their question
+- Wait for user response before any agent continues
+
+### Inter-Agent Questions
+
+Agents can question each other and respond naturally within the same round for dynamic conversation.
+
+---
+
+## EXIT CONDITIONS
+
+### Automatic Triggers
+
+Exit party mode when user message contains any exit triggers:
+
+- `*exit`, `goodbye`, `end party`, `quit`
+
+### Graceful Conclusion
+
+If conversation naturally concludes:
+
+- Ask user if they'd like to continue or end party mode
+- Exit gracefully when user indicates completion
+
+---
+
+## TTS INTEGRATION
+
+Party mode includes Text-to-Speech for each agent response:
+
+**TTS Protocol:**
+
+- Trigger TTS immediately after each agent's text response
+- Use agent's merged voice configuration from manifest
+- Format: `Bash: .claude/hooks/bmad-speak.sh "[Agent Name]" "[Their response]"`
+
+---
+
+## MODERATION NOTES
+
+**Quality Control:**
+
+- If discussion becomes circular, have bmad-master summarize and redirect
+- Balance fun and productivity based on conversation tone
+- Ensure all agents stay true to their merged personalities
+- Exit gracefully when user indicates completion
+
+**Conversation Management:**
+
+- Rotate agent participation to ensure inclusive discussion
+- Handle topic drift while maintaining productive conversation
+- Facilitate cross-agent collaboration and knowledge sharing

src/core/workflows/party-mode/workflow.yaml

@@ -1,28 +0,0 @@
-# Party Mode - Multi-Agent Group Discussion Workflow
-name: "party-mode"
-description: "Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations"
-author: "BMad"
-
-# Critical data sources - manifest and config overrides
-agent_manifest: "{project-root}/{bmad_folder}/_cfg/agent-manifest.csv"
-date: system-generated
-
-# This is an interactive action workflow - no template output
-template: false
-instructions: "{project-root}/{bmad_folder}/core/workflows/party-mode/instructions.md"
-
-# Exit conditions
-exit_triggers:
-  - "*exit"
-
-standalone: true
-
-web_bundle:
-  name: "party-mode"
-  description: "Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations"
-  author: "BMad"
-  instructions: "{bmad_folder}/core/workflows/party-mode/instructions.md"
-  agent_manifest: "{bmad_folder}/_cfg/agent-manifest.csv"
-  web_bundle_files:
-    - "{bmad_folder}/core/workflows/party-mode/instructions.md"
-    - "{bmad_folder}/_cfg/agent-manifest.csv"

src/modules/bmb/reference/agents/module-examples/security-engineer.agent.yaml

@@ -49,5 +49,5 @@ agent:
 
     # Core workflow that exists
     - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
       description: "Multi-agent security discussion"

src/modules/bmb/reference/agents/module-examples/trend-analyst.agent.yaml

@@ -53,5 +53,5 @@ agent:
       description: "Brainstorm trend implications"
 
     - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
       description: "Discuss trends with other agents"

src/modules/bmgd/agents/game-architect.agent.yaml

@@ -25,7 +25,7 @@ agent:
       description: Produce a Scale Adaptive Game Architecture
 
     - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
       description: Consult with other expert agents from the party
 
     - trigger: advanced-elicitation

src/modules/bmgd/agents/game-designer.agent.yaml

@@ -32,7 +32,7 @@ agent:
       description: 5. Create Narrative Design Document (story-driven games)
 
     - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
       description: Consult with other expert agents from the party
 
     - trigger: advanced-elicitation

src/modules/bmgd/agents/game-dev.agent.yaml

@@ -32,7 +32,7 @@ agent:
       description: "Mark story done after DoD complete"
 
     - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
       description: Consult with other expert agents from the party
 
     - trigger: advanced-elicitation

src/modules/bmgd/agents/game-scrum-master.agent.yaml

@@ -67,7 +67,7 @@ agent:
       description: (Optional) Navigate significant changes during game dev sprint
 
     - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
       description: Consult with other expert agents from the party
 
     - trigger: advanced-elicitation

src/modules/bmm/agents/analyst.agent.yaml

@@ -23,15 +23,16 @@ 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}/core/workflows/brainstorming/workflow.md"
-      description: Guided Brainstorming session with final report (optional)
+      data: "{project-root}/{bmad_folder}/bmm/data/project-context-template.md"
+      description: Guided Project Brainstorming session with final report (optional)
 
     - trigger: research
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/research/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/research/workflow.md"
-      description: Guided Research scoped to market and competitive analysis (optional)
+      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
@@ -39,7 +40,7 @@ agent:
       description: Document your existing project (optional, but recommended for existing brownfield project efforts)
 
     - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
       description: Bring the whole team in to chat with other expert agents from the party
 
     - trigger: advanced-elicitation

src/modules/bmm/agents/architect.agent.yaml

@@ -23,7 +23,7 @@ agent:
       description: Get workflow status or initialize a workflow if not already done (optional)
 
     - trigger: create-architecture
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture/workflow.md"
       description: Create an Architecture Document to Guide Development of a PRD (required for BMad Method projects)
 
     - trigger: validate-architecture
@@ -43,7 +43,7 @@ agent:
       description: Create data flow diagram (Excalidraw) (Use any time you need a diagram)
 
     - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
       description: Bring the whole team in to chat with other expert agents from the party
 
     - trigger: advanced-elicitation

src/modules/bmm/agents/pm.agent.yaml

@@ -41,7 +41,7 @@ agent:
       ide-only: true
 
     - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
       description: Bring the whole team in to chat with other expert agents from the party
 
     - trigger: advanced-elicitation

src/modules/bmm/agents/quick-flow-solo-dev.agent.yaml

@@ -32,5 +32,5 @@ agent:
       description: Review code and improve it (Highly Recommended, use fresh context and different LLM for best results)
 
     - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
       description: Bring in other experts when I need specialized backup

src/modules/bmm/agents/sm.agent.yaml

@@ -46,7 +46,7 @@ agent:
       description: Execute correct-course task (When implementation is off-track)
 
     - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
       description: Bring the whole team in to chat with other expert agents from the party
 
     - trigger: advanced-elicitation

src/modules/bmm/agents/tea.agent.yaml

@@ -61,7 +61,7 @@ agent:
       description: Review test quality using comprehensive knowledge base and best practices
 
     - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
       description: Bring the whole team in to chat with other expert agents from the party
 
     - trigger: advanced-elicitation

src/modules/bmm/agents/tech-writer.agent.yaml

@@ -17,7 +17,7 @@ agent:
       - Docs are living artifacts that evolve with code. Know when to simplify vs when to be detailed.
 
   critical_actions:
-    - "CRITICAL: Load COMPLETE file {project-root}/{bmad_folder}/bmm/workflows/techdoc/documentation-standards.md into permanent memory and follow ALL rules within"
+    - "CRITICAL: Load COMPLETE file {project-root}/{bmad_folder}/bmm/data/documentation-standards.md into permanent memory and follow ALL rules within"
     - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
 
   menu:
@@ -54,11 +54,11 @@ agent:
       description: Create clear technical explanations with examples
 
     - trigger: standards-guide
-      action: "Display the complete documentation standards from {project-root}/{bmad_folder}bmm/workflows/techdoc/documentation-standards.md in a clear, formatted way for the user."
+      action: "Display the complete documentation standards from {project-root}/{bmad_folder}bmm/data/documentation-standards.md in a clear, formatted way for the user."
       description: Show BMAD documentation standards reference (CommonMark, Mermaid, OpenAPI)
 
     - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
       description: Bring the whole team in to chat with other expert agents from the party
 
     - trigger: advanced-elicitation

src/modules/bmm/agents/ux-designer.agent.yaml

@@ -24,7 +24,7 @@ agent:
 
   menu:
     - trigger: create-ux-design
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md"
       description: Generate a UX Design and UI Plan from a PRD (Recommended before creating Architecture)
 
     - trigger: validate-design
@@ -36,7 +36,7 @@ agent:
       description: Create website or app wireframe (Excalidraw)
 
     - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
       description: Bring the whole team in to chat with other expert agents from the party
 
     - trigger: advanced-elicitation

src/modules/bmm/data/README.md

@@ -0,0 +1,29 @@
+# BMM Module Data
+
+This directory contains module-specific data files used by BMM agents and workflows.
+
+## Files
+
+### `project-context-template.md`
+
+Template for project-specific brainstorming context. Used by:
+
+- Analyst agent `brainstorm-project` command
+- Core brainstorming workflow when called with context
+
+### `documentation-standards.md`
+
+BMAD documentation standards and guidelines. Used by:
+
+- Tech Writer agent (critical action loading)
+- Various documentation workflows
+- Standards validation and review processes
+
+## Purpose
+
+Separates module-specific data from core workflow implementations, maintaining clean architecture:
+
+- Core workflows remain generic and reusable
+- Module-specific templates and standards are properly scoped
+- Data files can be easily maintained and updated
+- Clear separation of concerns between core and module functionality

src/modules/bmm/data/project-context-template.md

@@ -0,0 +1,40 @@
+# Project Brainstorming Context Template
+
+## Project Focus Areas
+
+This brainstorming session focuses on software and product development considerations:
+
+### Key Exploration Areas
+
+- **User Problems and Pain Points** - What challenges do users face?
+- **Feature Ideas and Capabilities** - What could the product do?
+- **Technical Approaches** - How might we build it?
+- **User Experience** - How will users interact with it?
+- **Business Model and Value** - How does it create value?
+- **Market Differentiation** - What makes it unique?
+- **Technical Risks and Challenges** - What could go wrong?
+- **Success Metrics** - How will we measure success?
+
+### Integration with Project Workflow
+
+Brainstorming results will feed into:
+
+- Product Briefs for initial product vision
+- PRDs for detailed requirements
+- Technical Specifications for architecture plans
+- Research Activities for validation needs
+
+### Expected Outcomes
+
+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
+
+---
+
+_Use this template to provide project-specific context for brainstorming sessions. Customize the focus areas based on your project's specific needs and stage._

src/modules/bmm/workflows/1-analysis/brainstorm-project/brainstorming-focus.md

@@ -1,25 +0,0 @@
-# Project Brainstorming Focus
-
-This context guide provides project-specific considerations for brainstorming sessions focused on software and product development.
-
-## Session Focus Areas
-
-When brainstorming for projects, consider exploring:
-
-- **User Problems and Pain Points** - What challenges do users face?
-- **Feature Ideas and Capabilities** - What could the product do?
-- **Technical Approaches** - How might we build it?
-- **User Experience** - How will users interact with it?
-- **Business Model and Value** - How does it create value?
-- **Market Differentiation** - What makes it unique?
-- **Technical Risks and Challenges** - What could go wrong?
-- **Success Metrics** - How will we measure success?
-
-## Integration with Project Workflow
-
-Brainstorming sessions typically feed into:
-
-- **Product Briefs** - Initial product vision and strategy
-- **PRDs** - Detailed requirements documents
-- **Technical Specifications** - Architecture and implementation plans
-- **Research Activities** - Areas requiring further investigation

src/modules/bmm/workflows/1-analysis/brainstorm-project/instructions.md

@@ -1,112 +0,0 @@
-# Brainstorm Project - Workflow Instructions
-
-```xml
-<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
-<critical>Communicate all responses in {communication_language}</critical>
-<critical>This is a meta-workflow that orchestrates the CIS brainstorming workflow with project-specific context</critical>
-<critical>⚠️ 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.</critical>
-<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> 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.</critical>
-
-<workflow>
-
-  <step n="1" goal="Validate workflow readiness" tag="workflow-status">
-    <action>Check if {output_folder}/bmm-workflow-status.yaml exists</action>
-
-    <check if="status file not found">
-      <output>No workflow status file found. Brainstorming is optional - you can continue without status tracking.</output>
-      <action>Set standalone_mode = true</action>
-    </check>
-
-    <check if="status file found">
-      <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
-      <action>Parse workflow_status section</action>
-      <action>Check status of "brainstorm-project" workflow</action>
-      <action>Get project_level from YAML metadata</action>
-      <action>Find first non-completed workflow (next expected workflow)</action>
-
-      <check if="brainstorm-project status is file path (already completed)">
-        <output>⚠️ Brainstorming session already completed: {{brainstorm-project status}}</output>
-        <ask>Re-running will create a new session. Continue? (y/n)</ask>
-        <check if="n">
-          <output>Exiting. Use workflow-status to see your next step.</output>
-          <action>Exit workflow</action>
-        </check>
-      </check>
-
-      <check if="brainstorm-project is not the next expected workflow (anything after brainstorm-project is completed already)">
-        <output>⚠️ Next expected workflow: {{next_workflow}}. Brainstorming is out of sequence.</output>
-        <ask>Continue with brainstorming anyway? (y/n)</ask>
-        <check if="n">
-          <output>Exiting. Run {{next_workflow}} instead.</output>
-          <action>Exit workflow</action>
-        </check>
-      </check>
-
-      <action>Set standalone_mode = false</action>
-    </check>
-  </step>
-
-  <step n="2" goal="Load project brainstorming context">
-    <action>Read the project context document from: {project_context}</action>
-    <action>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
-    </action>
-  </step>
-
-  <step n="3" goal="Invoke core brainstorming with project context">
-    <action>Execute the CIS brainstorming workflow with project context</action>
-    <invoke-workflow path="{core_brainstorming}" data="{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
-    </invoke-workflow>
-  </step>
-
-  <step n="4" goal="Update status and complete" tag="workflow-status">
-    <check if="standalone_mode != true">
-      <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
-      <action>Find workflow_status key "brainstorm-project"</action>
-      <critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
-      <action>Update workflow_status["brainstorm-project"] = "{output_folder}/bmm-brainstorming-session-{{date}}.md"</action>
-      <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
-
-      <action>Find first non-completed workflow in workflow_status (next workflow to do)</action>
-      <action>Determine next agent from path file based on next workflow</action>
-    </check>
-
-    <output>**✅ Brainstorming Session Complete, {user_name}!**
-
-**Session Results:**
-
-- Brainstorming results saved to: {output_folder}/bmm-brainstorming-session-{{date}}.md
-
-{{#if standalone_mode != true}}
-**Status Updated:**
-
-- Progress tracking updated
-
-**Next Steps:**
-
-- **Next required:** {{next_workflow}} ({{next_agent}} agent)
-- **Optional:** You can run other analysis workflows (research, product-brief) before proceeding
-
-Check status anytime with: `workflow-status`
-{{else}}
-**Next Steps:**
-
-Since no workflow is in progress:
-
-- Refer to the BMM workflow guide if unsure what to do next
-- Or run `workflow-init` to create a workflow path and get guided next steps
-{{/if}}
-    </output>
-  </step>
-
-</workflow>
-```

src/modules/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml

@@ -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"

src/modules/bmm/workflows/1-analysis/domain-research/instructions.md

@@ -1,425 +0,0 @@
-# Domain Research - Collaborative Domain Exploration
-
-<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
-<critical>This is COLLABORATIVE RESEARCH - engage the user as a partner, not just a data source</critical>
-<critical>The goal is PRACTICAL UNDERSTANDING that directly informs requirements and architecture</critical>
-<critical>Communicate all responses in {communication_language} and adapt deeply to {user_skill_level}</critical>
-<critical>Generate all documents in {document_output_language}</critical>
-<critical>LIVING DOCUMENT: Write to domain-brief.md continuously as you discover - never wait until the end</critical>
-<critical>⚠️ 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.</critical>
-<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> 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.</critical>
-
-<workflow>
-
-<step n="0" goal="Set research context">
-<action>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."</action>
-</step>
-
-<step n="1" goal="Domain detection and scoping">
-<action>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?"</action>
-
-<template-output>domain_overview</template-output>
-</step>
-
-<step n="2" goal="Collaborative concern mapping">
-<action>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?"</action>
-
-<template-output>concern_mapping</template-output>
-</step>
-
-<step n="3" goal="Research key requirements together">
-<action>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."
-
-<WebSearch>{specific_requirement} requirements {date}</WebSearch>
-
-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..."</action>
-
-<template-output>regulatory_requirements</template-output>
-<template-output>industry_standards</template-output>
-</step>
-
-<step n="4" goal="Identify practical implications">
-<action>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?"</action>
-
-<template-output>practical_implications</template-output>
-</step>
-
-<step n="5" goal="Discover domain-specific patterns">
-<action>Explore how others solve similar problems
-
-"Let's look at how successful [domain] products handle these challenges."
-
-<WebSearch>best {domain} software architecture patterns {date}</WebSearch>
-<WebSearch>{domain} software case studies {date}</WebSearch>
-
-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?"</action>
-
-<template-output>domain_patterns</template-output>
-<template-output if="novel approach">innovation_notes</template-output>
-</step>
-
-<step n="6" goal="Risk assessment and mitigation">
-<action>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?"</action>
-
-<template-output>risk_assessment</template-output>
-</step>
-
-<step n="7" goal="Create validation strategy">
-<action>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?"</action>
-
-<template-output>validation_strategy</template-output>
-</step>
-
-<step n="8" goal="Document decision points">
-<action>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?"</action>
-
-<template-output>key_decisions</template-output>
-</step>
-
-<step n="9" goal="Create actionable recommendations">
-<action>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?"</action>
-
-<template-output>recommendations</template-output>
-</step>
-
-<step n="10" goal="Package for PRD integration">
-<action>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?"</action>
-
-<template-output>summary_for_prd</template-output>
-</step>
-
-<step n="11" goal="Close with next steps">
-<output>**✅ Domain Research Complete, {user_name}!**
-
-We've explored the {domain} aspects of your project together and documented critical requirements.
-
-**Created:**
-
-- **domain-brief.md** - Complete domain analysis with requirements and recommendations
-
-**Key Findings:**
-
-- Primary domain: {domain}
-- Complexity level: {complexity}
-- Critical requirements: {count} identified
-- Risks identified: {count} with mitigation strategies
-
-**Next Steps:**
-
-1. Return to PRD workflow with this domain context
-2. Domain requirements will shape your functional requirements
-3. Reference domain-brief.md for detailed requirements
-
-**Remember:**
-{most_important_finding}
-
-The domain research will ensure your PRD captures not just what to build, but HOW to build it correctly for {domain}.
-</output>
-</step>
-
-</workflow>

src/modules/bmm/workflows/1-analysis/domain-research/template.md

@@ -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._

src/modules/bmm/workflows/1-analysis/domain-research/workflow.yaml

@@ -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"

src/modules/bmm/workflows/1-analysis/product-brief/checklist.md

@@ -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)

src/modules/bmm/workflows/1-analysis/product-brief/instructions.md

@@ -1,515 +0,0 @@
-# Product Brief - Context-Adaptive Discovery Instructions
-
-<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
-<critical>This workflow uses INTENT-DRIVEN FACILITATION - adapt organically to what emerges</critical>
-<critical>The goal is DISCOVERING WHAT MATTERS through natural conversation, not filling a template</critical>
-<critical>Communicate all responses in {communication_language} and adapt deeply to {user_skill_level}</critical>
-<critical>Generate all documents in {document_output_language}</critical>
-<critical>LIVING DOCUMENT: Write to the document continuously as you discover - never wait until the end</critical>
-<critical>⚠️ 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.</critical>
-<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> 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.</critical>
-
-## 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)
-
-<workflow>
-
-<step n="0" goal="Validate workflow readiness" tag="workflow-status">
-<action>Check if {output_folder}/bmm-workflow-status.yaml exists</action>
-
-<action if="status file not found">Set standalone_mode = true</action>
-
-<check if="status file found">
-  <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
-  <action>Parse workflow_status section</action>
-  <action>Check status of "product-brief" workflow</action>
-  <action>Get project_level from YAML metadata</action>
-  <action>Find first non-completed workflow (next expected workflow)</action>
-</check>
-
-  <check if="product-brief status is file path (already completed)">
-    <output>⚠️ Product Brief already completed: {{product-brief status}}</output>
-    <ask>Re-running will overwrite the existing brief. Continue? (y/n)</ask>
-    <check if="n">
-      <output>Exiting. Use workflow-status to see your next step.</output>
-      <action>Exit workflow</action>
-    </check>
-  </check>
-
-  <check if="product-brief is not the next expected workflow">
-    <output>⚠️ Next expected workflow: {{next_workflow}}. Product Brief is out of sequence.</output>
-    <ask>Continue with Product Brief anyway? (y/n)</ask>
-    <check if="n">
-      <output>Exiting. Run {{next_workflow}} instead.</output>
-      <action>Exit workflow</action>
-    </check>
-  </check>
-
-<action>Set standalone_mode = false</action>
-</check>
-</step>
-
-<step n="0.5" goal="Discover and load input documents">
-<invoke-protocol name="discover_inputs" />
-</step>
-
-<step n="1" goal="Begin the journey and understand context">
-<action>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</action>
-
-<ask if="user has not given the project name already">What's the project name?</ask>
-
-<action>From even this first exchange, create initial document sections</action>
-<template-output>project_name</template-output>
-<template-output>executive_summary</template-output>
-
-<action>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</action>
-
-<template-output>initial_vision</template-output>
-</step>
-
-<step n="2" goal="Discover the problem worth solving">
-<action>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</action>
-
-<action>Immediately capture what emerges - even if preliminary</action>
-<template-output>problem_statement</template-output>
-
-<check if="user mentioned metrics, costs, or business impact">
-  <action>Explore the measurable impact of the problem</action>
-  <template-output>problem_impact</template-output>
-</check>
-
-<check if="user mentioned current solutions or competitors">
-  <action>Understand why existing solutions fall short</action>
-  <template-output>existing_solutions_gaps</template-output>
-</check>
-
-<action>Reflect understanding: "So the core issue is {{problem_summary}}, and {{impact_if_mentioned}}. Let me capture that..."</action>
-</step>
-
-<step n="3" goal="Shape the solution vision">
-<action>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</action>
-
-<action if="competitor or market mentioned">
-  <WebSearch>{{competitor/market}} latest features 2024</WebSearch>
-  <action>Use findings to sharpen differentiation discussion</action>
-</action>
-
-<template-output>proposed_solution</template-output>
-
-<check if="unique differentiation discussed">
-  <template-output>key_differentiators</template-output>
-</check>
-
-<action>Continue building the living document</action>
-</step>
-
-<step n="4" goal="Understand the people who need this">
-<action>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</action>
-
-<template-output>primary_user_segment</template-output>
-
-<check if="multiple user types mentioned">
-  <action>Explore secondary users only if truly different needs</action>
-  <template-output>secondary_user_segment</template-output>
-</check>
-
-<check if="user journey or workflow discussed">
-  <template-output>user_journey</template-output>
-</check>
-</step>
-
-<step n="5" goal="Define what success looks like" repeat="adapt-to-context">
-<action>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</action>
-
-<check if="metrics or goals discussed">
-  <template-output>success_metrics</template-output>
-
-  <check if="business objectives mentioned">
-    <template-output>business_objectives</template-output>
-  </check>
-
-  <check if="KPIs matter to them">
-    <template-output>key_performance_indicators</template-output>
-  </check>
-</check>
-
-<action>Keep the document growing with each discovery</action>
-</step>
-
-<step n="6" goal="Discover the MVP scope">
-<critical>Focus on FEATURES not epics - that comes in Phase 2</critical>
-
-<action>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?"</action>
-
-<template-output>core_features</template-output>
-
-<check if="scope creep discussed">
-  <template-output>out_of_scope</template-output>
-</check>
-
-<check if="future features mentioned">
-  <template-output>future_vision_features</template-output>
-</check>
-
-<check if="success criteria for MVP mentioned">
-  <template-output>mvp_success_criteria</template-output>
-</check>
-</step>
-
-<step n="7" goal="Explore relevant context dimensions" repeat="until-natural-end">
-<critical>Only explore what emerges naturally - skip what doesn't matter</critical>
-
-<action>Based on the conversation so far, selectively explore:
-
-IF financial aspects emerged:
-
-- Development investment needed
-- Revenue potential or cost savings
-- ROI timeline
-- Budget constraints
-  <check if="discussed">
-  <template-output>financial_considerations</template-output>
-  </check>
-
-IF market competition mentioned:
-
-- Competitive landscape
-- Market opportunity size
-- Differentiation strategy
-- Market timing
-  <check if="discussed">
-  <WebSearch>{{market}} size trends 2024</WebSearch>
-  <template-output>market_analysis</template-output>
-  </check>
-
-IF technical preferences surfaced:
-
-- Platform choices (web/mobile/desktop)
-- Technology stack preferences
-- Integration needs
-- Performance requirements
-  <check if="discussed">
-  <template-output>technical_preferences</template-output>
-  </check>
-
-IF organizational context emerged:
-
-- Strategic alignment
-- Stakeholder buy-in needs
-- Change management considerations
-- Compliance requirements
-  <check if="discussed">
-  <template-output>organizational_context</template-output>
-  </check>
-
-IF risks or concerns raised:
-
-- Key risks and mitigation
-- Critical assumptions
-- Open questions needing research
-  <check if="discussed">
-  <template-output>risks_and_assumptions</template-output>
-  </check>
-
-IF timeline pressures mentioned:
-
-- Launch timeline
-- Critical milestones
-- Dependencies
-  <check if="discussed">
-  <template-output>timeline_constraints</template-output>
-  </check>
-
-Skip anything that hasn't naturally emerged
-Don't force sections that don't fit their context</action>
-</step>
-
-<step n="8" goal="Refine and complete the living document">
-<action>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</action>
-
-<action>Make final refinements based on feedback</action>
-<template-output>final_refinements</template-output>
-
-<action>Create executive summary that captures the essence</action>
-<template-output>executive_summary</template-output>
-</step>
-<step n="9" goal="Complete and save the product brief">
-<action>The document has been building throughout our conversation
-Now ensure it's complete and well-organized</action>
-
-<check if="research documents were provided">
-  <action>Append summary of incorporated research</action>
-  <template-output>supporting_materials</template-output>
-</check>
-
-<action>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</action>
-
-<ask>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?</ask>
-
-<action>Make any requested refinements</action>
-<template-output>final_document</template-output>
-</step>
-
-<check if="standalone_mode != true">
-  <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
-  <action>Find workflow_status key "product-brief"</action>
-  <critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
-  <action>Update workflow_status["product-brief"] = "{output_folder}/bmm-product-brief-{{project_name}}-{{date}}.md"</action>
-  <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
-
-<action>Find first non-completed workflow in workflow_status (next workflow to do)</action>
-<action>Determine next agent from path file based on next workflow</action>
-</check>
-
-<output>**✅ Product Brief Complete, {user_name}!**
-
-Your product vision has been captured in a document that reflects what matters most for your {{context_type}} project.
-
-**Document saved:** {output_folder}/bmm-product-brief-{{project_name}}-{{date}}.md
-
-{{#if standalone_mode != true}}
-**What's next:** {{next_workflow}} ({{next_agent}} agent)
-
-The next phase will take your brief and create the detailed planning artifacts needed for implementation.
-{{else}}
-**Next steps:**
-
-- Run `workflow-init` to set up guided workflow tracking
-- Or proceed directly to the PRD workflow if you know your path
-  {{/if}}
-
-Remember: This brief captures YOUR vision. It grew from our conversation, not from a rigid template. It's ready to guide the next phase of bringing your idea to life.
-</output>
-</step>
-
-</workflow>

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}}
+
+---
+
+<!-- Content will be appended sequentially through collaborative workflow steps -->

src/modules/bmm/workflows/1-analysis/product-brief/steps/step-01-init.md

@@ -0,0 +1,151 @@
+# Step 1: Product Brief Initialization
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ 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}/analysis/*product-brief*.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}/analysis/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}/analysis/research/*research*.md`
+4. Add discovered files to `inputDocuments` frontmatter
+
+**Brainstorming Documents (Priority: Sharded → Whole):**
+
+1. Check for sharded brainstorming folder: `{output_folder}/analysis/*brainstorm*/**/*.md`
+2. If folder exists: Load useful brainstorming files completely
+3. If no folder exists: Try whole file: `{output_folder}/analysis/*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
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## 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!

src/modules/bmm/workflows/1-analysis/product-brief/steps/step-01b-continue.md

@@ -0,0 +1,123 @@
+# Step 1B: Product Brief Continuation
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ 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
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## WORKFLOW ALREADY COMPLETE?
+
+If `lastStep = 6` (final step completed):
+"Great news! It looks like we've already completed the product brief workflow for {{project_name}}.
+
+The final document is ready at {default_output_file} with all sections completed through step 6.
+
+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!

src/modules/bmm/workflows/1-analysis/product-brief/steps/step-02-vision.md

@@ -0,0 +1,223 @@
+# Step 2: Product Vision Discovery
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ 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/workflow.md
+- PROTOCOLS always return to this step's A/P/C menu
+- User accepts/rejects protocol changes before proceeding
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from step 1 are available
+- 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 {project-root}/{bmad_folder}/core/tasks/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 {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md 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'
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## CONTEXT INPUTS:
+
+If research or brainstorming documents were loaded in step 1, incorporate insights from those documents into the vision discovery:
+
+- "I see from the research that..."
+- "In the brainstorming session, you mentioned..."
+- "The project documentation suggests..."
+
+## NEXT STEP:
+
+After user selects 'C' and content is saved to document, load `./step-03-users.md` to define target users.
+
+Remember: Do NOT proceed to step-03 until user explicitly selects 'C' from the A/P/C menu and content is saved!

src/modules/bmm/workflows/1-analysis/product-brief/steps/step-03-users.md

@@ -0,0 +1,226 @@
+# Step 3: Target Users Discovery
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ 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/workflow.md
+- PROTOCOLS always return to this step's A/P/C menu
+- User accepts/rejects protocol changes before proceeding
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- 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 {project-root}/{bmad_folder}/core/tasks/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 {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md 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'
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## USER INSIGHTS SOURCES:
+
+If user research documents were loaded in step 1, incorporate those insights:
+
+- "From the user research we loaded, I see that..."
+- "The interviews suggest users are struggling with..."
+- "The survey data indicates preferences for..."
+
+## OPTIONAL CONTENT:
+
+User journey section is optional - only include if the journey mapping reveals important insights about how users will interact with the product and where value is created.
+
+## NEXT STEP:
+
+After user selects 'C' and content is saved to document, load `./step-04-metrics.md` to define success metrics.
+
+Remember: Do NOT proceed to step-04 until user explicitly selects 'C' from the A/P/C menu and content is saved!

src/modules/bmm/workflows/1-analysis/product-brief/steps/step-04-metrics.md

@@ -0,0 +1,238 @@
+# Step 4: Success Metrics Definition
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ 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/workflow.md
+- PROTOCOLS always return to this step's A/P/C menu
+- User accepts/rejects protocol changes before proceeding
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- 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 {project-root}/{bmad_folder}/core/tasks/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 {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md 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'
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## METRIC QUALITY CRITERIA:
+
+**Good Metrics:**
+
+- Specific and measurable
+- Connected to user value or business outcomes
+- Actionable - they inform decisions
+- Leading indicators when possible
+- Easy to track and understand
+
+**Avoid:**
+
+- Vanity metrics that look good but don't drive decisions
+- Metrics without clear measurement methods
+- Too many competing priorities
+- Metrics disconnected from product strategy
+
+## OPTIONAL SECTIONS:
+
+Business Objectives and KPIs sections are optional - include them if the discussion yields meaningful, specific objectives and indicators. If not, focus on the core user success metrics section.
+
+## NEXT STEP:
+
+After user selects 'C' and content is saved to document, load `./step-05-scope.md` to define MVP scope.
+
+Remember: Do NOT proceed to step-05 until user explicitly selects 'C' from the A/P/C menu and content is saved!

src/modules/bmm/workflows/1-analysis/product-brief/steps/step-05-scope.md

@@ -0,0 +1,251 @@
+# Step 5: MVP Scope Definition
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ 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/workflow.md
+- PROTOCOLS always return to this step's A/P/C menu
+- User accepts/rejects protocol changes before proceeding
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- 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 {project-root}/{bmad_folder}/core/tasks/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 {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md 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'
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## SCOPE NEGOTIATION PRINCIPLES:
+
+**MVP Mindset:**
+
+- Minimum features that create maximum user value
+- Fast learning and iteration capability
+- Clear success criteria for next phase decisions
+- Stakeholder alignment on boundaries
+
+**Scope Creep Prevention:**
+
+- Explicit out-of-scope documentation
+- Rationale for feature deferral
+- Clear roadmap for future additions
+- Regular scope validation against core problem
+
+## OPTIONAL SECTIONS:
+
+Future Vision and MVP Success Criteria sections are optional - include them if the discussion yields meaningful insights about long-term direction and success validation. Core Features and Out of Scope are essential sections.
+
+## NEXT STEP:
+
+After user selects 'C' and content is saved to document, load `./step-06-complete.md` to complete the product brief workflow.
+
+Remember: Do NOT proceed to step-06 until user explicitly selects 'C' from the A/P/C menu and content is saved!

src/modules/bmm/workflows/1-analysis/product-brief/steps/step-06-complete.md

@@ -0,0 +1,200 @@
+# Step 6: Product Brief Completion
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ THIS IS A FINAL STEP - Product brief completion required
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- 🛑 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
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## 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?**

src/modules/bmm/workflows/1-analysis/product-brief/template.md

@@ -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}}

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.

src/modules/bmm/workflows/1-analysis/product-brief/workflow.yaml

@@ -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"

src/modules/bmm/workflows/1-analysis/research/checklist-deep-prompt.md

@@ -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}

src/modules/bmm/workflows/1-analysis/research/checklist-technical.md

@@ -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}

src/modules/bmm/workflows/1-analysis/research/checklist.md

@@ -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}

src/modules/bmm/workflows/1-analysis/research/claude-code/injections.yaml

@@ -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: |
-      <critical>
-      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.
-      </critical>
-
-  - injection_point: "market-tam-calculations"
-    description: "Enhanced TAM calculation with data analyst"
-    content: |
-      <invoke-subagent name="bmm-data-analyst">
-      Calculate TAM using multiple methodologies and provide confidence intervals.
-      Use all available market data from previous research steps.
-      Show detailed calculations and assumptions.
-      </invoke-subagent>
-
-  - injection_point: "market-trends-analysis"
-    description: "Enhanced trend analysis with trend spotter"
-    content: |
-      <invoke-subagent name="bmm-trend-spotter">
-      Identify emerging trends, weak signals, and future disruptions.
-      Look for cross-industry patterns and second-order effects.
-      Provide timeline estimates for mainstream adoption.
-      </invoke-subagent>
-
-  - injection_point: "market-customer-segments"
-    description: "Enhanced customer research"
-    content: |
-      <invoke-subagent name="bmm-user-researcher">
-      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.
-      </invoke-subagent>
-
-  - injection_point: "market-executive-summary"
-    description: "Enhanced executive summary synthesis"
-    content: |
-      <invoke-subagent name="bmm-market-researcher">
-      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.
-      </invoke-subagent>
-
-# 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"

src/modules/bmm/workflows/1-analysis/research/domain-steps/step-01-init.md

@@ -0,0 +1,136 @@
+# Domain Research Step 1: Domain Research Scope Confirmation
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user confirmation
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ FOCUS EXCLUSIVELY on confirming domain research scope and approach
+- 📋 YOU ARE A DOMAIN RESEARCH PLANNER, not content generator
+- 💬 ACKNOWLEDGE and CONFIRM understanding of domain research goals
+- 🔍 This is SCOPE CONFIRMATION ONLY - no web research yet
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis before taking any action
+- ⚠️ Present [C] continue option after scope confirmation
+- 💾 ONLY proceed when user chooses C (Continue)
+- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
+- 🚫 FORBIDDEN to load next step until C is selected
+
+## CONTEXT BOUNDARIES:
+
+- Research type = "domain" is already set
+- **Research topic = "{{research_topic}}"** - discovered from initial discussion
+- **Research goals = "{{research_goals}}"** - captured from initial discussion
+- Focus on industry/domain analysis with web research
+- Web search capabilities with {{current_year}} data are enabled
+
+## YOUR TASK:
+
+Confirm domain research scope and approach for **{{research_topic}}** with the user's goals in mind.
+
+## DOMAIN SCOPE CONFIRMATION:
+
+### 1. Begin Scope Confirmation
+
+Start with domain scope understanding:
+"I understand you want to conduct **domain research** for **{{research_topic}}** with these goals: {{research_goals}}
+
+**Domain Research Scope:**
+
+- **Industry Analysis**: Industry structure, market dynamics, and competitive landscape
+- **Regulatory Environment**: Compliance requirements, regulations, and standards
+- **Technology Patterns**: Innovation trends, technology adoption, and digital transformation
+- **Economic Factors**: Market size, growth trends, and economic impact
+- **Supply Chain**: Value chain analysis and ecosystem relationships
+
+**Research Approach:**
+
+- Current {{current_year}} web data with rigorous source verification
+- Multi-source validation for critical domain claims
+- Confidence levels for uncertain domain information
+- Comprehensive domain coverage with industry-specific insights
+
+### 2. Scope Confirmation
+
+Present clear scope confirmation:
+"**Domain Research Scope Confirmation:**
+
+For **{{research_topic}}**, I will research:
+
+✅ **Industry Analysis** - market structure, key players, competitive dynamics
+✅ **Regulatory Requirements** - compliance standards, legal frameworks
+✅ **Technology Trends** - innovation patterns, digital transformation
+✅ **Economic Factors** - market size, growth projections, economic impact
+✅ **Supply Chain Analysis** - value chain, ecosystem, partnerships
+
+**All using current {{current_year}} web data with source verification.**
+
+**Does this domain research scope and approach align with your goals?**
+[C] Continue - Begin domain research with this scope
+
+### 3. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- Document scope confirmation in research file
+- Update frontmatter: `stepsCompleted: [1]`
+- Load: `./step-02-industry-analysis.md`
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append scope confirmation:
+
+```markdown
+## Domain Research Scope Confirmation
+
+**Research Topic:** {{research_topic}}
+**Research Goals:** {{research_goals}}
+
+**Domain Research Scope:**
+
+- Industry Analysis - market structure, competitive landscape
+- Regulatory Environment - compliance requirements, legal frameworks
+- Technology Trends - innovation patterns, digital transformation
+- Economic Factors - market size, growth projections
+- Supply Chain Analysis - value chain, ecosystem relationships
+
+**Research Methodology:**
+
+- Current {{current_year}} web data with rigorous source verification
+- Multi-source validation for critical domain claims
+- Confidence level framework for uncertain information
+- Comprehensive domain coverage with industry-specific insights
+
+**Scope Confirmed:** {{date}}
+```
+
+## SUCCESS METRICS:
+
+✅ Domain research scope clearly confirmed with user
+✅ All domain analysis areas identified and explained
+✅ Research methodology with {{current_year}} data emphasized
+✅ [C] continue option presented and handled correctly
+✅ Scope confirmation documented when user proceeds
+✅ Proper routing to next domain research step
+
+## FAILURE MODES:
+
+❌ Not clearly confirming domain research scope with user
+❌ Missing critical domain analysis areas
+❌ Not emphasizing {{current_year}} web data requirement
+❌ Not presenting [C] continue option
+❌ Proceeding without user scope confirmation
+❌ Not routing to next domain research step
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## NEXT STEP:
+
+After user selects 'C', load `./step-02-industry-analysis.md` to begin industry analysis with current {{current_year}} web data.
+
+Remember: This is SCOPE CONFIRMATION ONLY - no actual domain research yet, just confirming the research approach and scope!

src/modules/bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md

@@ -0,0 +1,228 @@
+# Domain Research Step 2: Industry Analysis
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ ALWAYS use {{current_year}} web searches for current industry data
+- 📋 YOU ARE AN INDUSTRY ANALYST, not content generator
+- 💬 FOCUS on market size, growth, and industry dynamics
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] continue option after industry analysis content generation
+- 📝 WRITE INDUSTRY ANALYSIS TO DOCUMENT IMMEDIATELY
+- 💾 ONLY proceed 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 topic = "{{research_topic}}"** - established from initial discussion
+- **Research goals = "{{research_goals}}"** - established from initial discussion
+- Focus on market size, growth, and industry dynamics
+- Web search capabilities with source verification are enabled
+
+## YOUR TASK:
+
+Conduct industry analysis focusing on market size, growth, and industry dynamics using current {{current_year}} web data with rigorous source verification.
+
+## INDUSTRY ANALYSIS SEQUENCE:
+
+### 1. Begin Industry Analysis
+
+**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different industry areas simultaneously and thoroughly.
+
+Start with industry research approach:
+"Now I'll conduct **industry analysis** for **{{research_topic}}** using current {{current_year}} web data to understand market dynamics.
+
+**Industry Analysis Focus:**
+
+- Market size and valuation metrics
+- Growth rates and market dynamics
+- Market segmentation and structure
+- Industry trends and evolution patterns
+- Economic impact and value creation
+
+**Let me search for current industry insights.**"
+
+### 2. Parallel Industry Research Execution
+
+**Execute multiple web searches simultaneously:**
+
+`WebSearch: "{{research_topic}} market size value {{current_year}}"`
+`WebSearch: "{{research_topic}} market growth rate dynamics {{current_year}}"`
+`WebSearch: "{{research_topic}} market segmentation structure {{current_year}}"`
+`WebSearch: "{{research_topic}} industry trends evolution {{current_year}}"`
+
+**Analysis approach:**
+
+- Look for recent market research reports and industry analyses
+- Search for authoritative sources (market research firms, industry associations)
+- Identify market size, growth rates, and segmentation data
+- Research industry trends and evolution patterns
+- Analyze economic impact and value creation metrics
+
+### 3. Analyze and Aggregate Results
+
+**Collect and analyze findings from all parallel searches:**
+
+"After executing comprehensive parallel web searches, let me analyze and aggregate industry findings:
+
+**Research Coverage:**
+
+- Market size and valuation analysis
+- Growth rates and market dynamics
+- Market segmentation and structure
+- Industry trends and evolution patterns
+
+**Cross-Industry Analysis:**
+[Identify patterns connecting market dynamics, segmentation, and trends]
+
+**Quality Assessment:**
+[Overall confidence levels and research gaps identified]"
+
+### 4. Generate Industry Analysis Content
+
+**WRITE IMMEDIATELY TO DOCUMENT**
+
+Prepare industry analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Industry Analysis
+
+### Market Size and Valuation
+
+[Market size analysis with source citations]
+_Total Market Size: [Current market valuation with {{current_year}} data]_
+_Growth Rate: [CAGR and market growth projections]_
+_Market Segments: [Size and value of key market segments]_
+_Economic Impact: [Economic contribution and value creation]_
+_Source: [URL with {{current_year}} market size data]_
+
+### Market Dynamics and Growth
+
+[Market dynamics analysis with source citations]
+_Growth Drivers: [Key factors driving market growth]_
+_Growth Barriers: [Factors limiting market expansion]_
+_Cyclical Patterns: [Industry seasonality and cycles]_
+_Market Maturity: [Life cycle stage and development phase]_
+_Source: [URL with {{current_year}} market dynamics data]_
+
+### Market Structure and Segmentation
+
+[Market structure analysis with source citations]
+_Primary Segments: [Key market segments and their characteristics]_
+_Sub-segment Analysis: [Detailed breakdown of market sub-segments]_
+_Geographic Distribution: [Regional market variations and concentrations]_
+_Vertical Integration: [Supply chain and value chain structure]_
+_Source: [URL with {{current_year}} market structure data]_
+
+### Industry Trends and Evolution
+
+[Industry trends analysis with source citations]
+_Emerging Trends: [Current industry developments and transformations]_
+_Historical Evolution: [Industry development over recent years]_
+_Technology Integration: [How technology is changing the industry]_
+_Future Outlook: [Projected industry developments and changes]_
+_Source: [URL with {{current_year}} industry trends data]_
+
+### Competitive Dynamics
+
+[Competitive dynamics analysis with source citations]
+_Market Concentration: [Level of market consolidation and competition]_
+_Competitive Intensity: [Degree of competition and rivalry]_
+_Barriers to Entry: [Obstacles for new market entrants]_
+_Innovation Pressure: [Rate of innovation and change]_
+_Source: [URL with {{current_year}} competitive dynamics data]_
+```
+
+### 5. Present Analysis and Continue Option
+
+**Show analysis and present continue option:**
+
+"I've completed **industry analysis** using current {{current_year}} data to understand market dynamics for {{research_topic}}.
+
+**Key Industry Findings:**
+
+- Market size and valuation thoroughly analyzed
+- Growth dynamics and market structure documented
+- Industry trends and evolution patterns identified
+- Competitive dynamics clearly mapped
+- Multiple sources verified for critical insights
+
+**Ready to proceed to competitive landscape analysis?**
+[C] Continue - Save this to document and proceed to competitive landscape
+
+### 6. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- **CONTENT ALREADY WRITTEN TO DOCUMENT**
+- Update frontmatter: `stepsCompleted: [1, 2]`
+- Load: `./step-03-competitive-landscape.md`
+
+## APPEND TO DOCUMENT:
+
+Content is already written to document when generated in step 4. No additional append needed.
+
+## SUCCESS METRICS:
+
+✅ Market size and valuation thoroughly analyzed
+✅ Growth dynamics and market structure documented
+✅ Industry trends and evolution patterns identified
+✅ Competitive dynamics clearly mapped
+✅ Multiple sources verified for critical insights
+✅ Content written immediately to document
+✅ [C] continue option presented and handled correctly
+✅ Proper routing to next step (competitive landscape)
+✅ Research goals alignment maintained
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in industry web searches
+❌ Missing critical market size or growth data
+❌ Incomplete market structure analysis
+❌ Not identifying key industry trends
+❌ Not writing content immediately to document
+❌ Not presenting [C] continue option after content generation
+❌ Not routing to competitive landscape step
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## INDUSTRY RESEARCH PROTOCOLS:
+
+- Research market research reports and industry analyses
+- Use authoritative sources (market research firms, industry associations)
+- Analyze market size, growth rates, and segmentation data
+- Study industry trends and evolution patterns
+- Focus on current {{current_year}} industry data
+- Present conflicting information when sources disagree
+- Apply confidence levels appropriately
+
+## INDUSTRY ANALYSIS STANDARDS:
+
+- Always cite URLs for web search results
+- Use authoritative industry research sources
+- Note data currency and potential limitations
+- Present multiple perspectives when sources conflict
+- Apply confidence levels to uncertain data
+- Focus on actionable industry insights
+
+## NEXT STEP:
+
+After user selects 'C', load `./step-03-competitive-landscape.md` to analyze competitive landscape, key players, and ecosystem analysis for {{research_topic}}.
+
+Remember: Always write research content to document immediately and emphasize current {{current_year}} industry data with rigorous source verification!

src/modules/bmm/workflows/1-analysis/research/domain-steps/step-03-competitive-landscape.md

@@ -0,0 +1,237 @@
+# Domain Research Step 3: Competitive Landscape
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ ALWAYS use {{current_year}} web searches for current competitive data
+- 📋 YOU ARE A COMPETITIVE ANALYST, not content generator
+- 💬 FOCUS on key players, market share, and competitive dynamics
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] continue option after competitive analysis content generation
+- 📝 WRITE COMPETITIVE ANALYSIS TO DOCUMENT IMMEDIATELY
+- 💾 ONLY proceed 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
+- **Research topic = "{{research_topic}}"** - established from initial discussion
+- **Research goals = "{{research_goals}}"** - established from initial discussion
+- Focus on key players, market share, and competitive dynamics
+- Web search capabilities with source verification are enabled
+
+## YOUR TASK:
+
+Conduct competitive landscape analysis focusing on key players, market share, and competitive dynamics using current {{current_year}} web data with rigorous source verification.
+
+## COMPETITIVE LANDSCAPE ANALYSIS SEQUENCE:
+
+### 1. Begin Competitive Landscape Analysis
+
+**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different competitive areas simultaneously and thoroughly.
+
+Start with competitive research approach:
+"Now I'll conduct **competitive landscape analysis** for **{{research_topic}}** using current {{current_year}} web data to understand the competitive ecosystem.
+
+**Competitive Landscape Focus:**
+
+- Key players and market leaders
+- Market share and competitive positioning
+- Competitive strategies and differentiation
+- Business models and value propositions
+- Entry barriers and competitive dynamics
+
+**Let me search for current competitive insights.**"
+
+### 2. Parallel Competitive Research Execution
+
+**Execute multiple web searches simultaneously:**
+
+`WebSearch: "{{research_topic}} key players market leaders {{current_year}}"`
+`WebSearch: "{{research_topic}} market share competitive landscape {{current_year}}"`
+`WebSearch: "{{research_topic}} competitive strategies differentiation {{current_year}}"`
+`WebSearch: "{{research_topic}} entry barriers competitive dynamics {{current_year}}"`
+
+**Analysis approach:**
+
+- Look for recent competitive intelligence reports and market analyses
+- Search for company websites, annual reports, and investor presentations
+- Research market share data and competitive positioning
+- Analyze competitive strategies and differentiation approaches
+- Study entry barriers and competitive dynamics
+
+### 3. Analyze and Aggregate Results
+
+**Collect and analyze findings from all parallel searches:**
+
+"After executing comprehensive parallel web searches, let me analyze and aggregate competitive findings:
+
+**Research Coverage:**
+
+- Key players and market leaders analysis
+- Market share and competitive positioning assessment
+- Competitive strategies and differentiation mapping
+- Entry barriers and competitive dynamics evaluation
+
+**Cross-Competitive Analysis:**
+[Identify patterns connecting players, strategies, and market dynamics]
+
+**Quality Assessment:**
+[Overall confidence levels and research gaps identified]"
+
+### 4. Generate Competitive Landscape Content
+
+**WRITE IMMEDIATELY TO DOCUMENT**
+
+Prepare competitive landscape analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Competitive Landscape
+
+### Key Players and Market Leaders
+
+[Key players analysis with source citations]
+_Market Leaders: [Dominant players and their market positions]_
+_Major Competitors: [Significant competitors and their specialties]_
+_Emerging Players: [New entrants and innovative companies]_
+_Global vs Regional: [Geographic distribution of key players]_
+_Source: [URL with {{current_year}} competitive data]_
+
+### Market Share and Competitive Positioning
+
+[Market share analysis with source citations]
+_Market Share Distribution: [Current market share breakdown]_
+_Competitive Positioning: [How players position themselves in the market]_
+_Value Proposition Mapping: [Different value propositions across players]_
+_Customer Segments Served: [Different customer bases by competitor]_
+_Source: [URL with {{current_year}} market share data]_
+
+### Competitive Strategies and Differentiation
+
+[Competitive strategies analysis with source citations]
+_Cost Leadership Strategies: [Players competing on price and efficiency]_
+_Differentiation Strategies: [Players competing on unique value]_
+_Focus/Niche Strategies: [Players targeting specific segments]_
+_Innovation Approaches: [How different players innovate]_
+_Source: [URL with {{current_year}} competitive strategies data]_
+
+### Business Models and Value Propositions
+
+[Business models analysis with source citations]
+_Primary Business Models: [How competitors make money]_
+_Revenue Streams: [Different approaches to monetization]_
+_Value Chain Integration: [Vertical integration vs partnership models]_
+_Customer Relationship Models: [How competitors build customer loyalty]_
+_Source: [URL with {{current_year}} business models data]_
+
+### Competitive Dynamics and Entry Barriers
+
+[Competitive dynamics analysis with source citations]
+_Barriers to Entry: [Obstacles facing new market entrants]_
+_Competitive Intensity: [Level of rivalry and competitive pressure]_
+_Market Consolidation Trends: [M&A activity and market concentration]_
+_Switching Costs: [Costs for customers to switch between providers]_
+_Source: [URL with {{current_year}} competitive dynamics data]_
+
+### Ecosystem and Partnership Analysis
+
+[Ecosystem analysis with source citations]
+_Supplier Relationships: [Key supplier partnerships and dependencies]_
+_Distribution Channels: [How competitors reach customers]_
+_Technology Partnerships: [Strategic technology alliances]_
+_Ecosystem Control: [Who controls key parts of the value chain]_
+_Source: [URL with {{current_year}} ecosystem data]_
+```
+
+### 5. Present Analysis and Continue Option
+
+**Show analysis and present continue option:**
+
+"I've completed **competitive landscape analysis** using current {{current_year}} data to understand the competitive ecosystem for {{research_topic}}.
+
+**Key Competitive Findings:**
+
+- Key players and market leaders thoroughly identified
+- Market share and competitive positioning clearly mapped
+- Competitive strategies and differentiation analyzed
+- Business models and value propositions documented
+- Competitive dynamics and entry barriers evaluated
+
+**Ready to proceed to regulatory focus analysis?**
+[C] Continue - Save this to document and proceed to regulatory focus
+
+### 6. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- **CONTENT ALREADY WRITTEN TO DOCUMENT**
+- Update frontmatter: `stepsCompleted: [1, 2, 3]`
+- Load: `./step-04-regulatory-focus.md`
+
+## APPEND TO DOCUMENT:
+
+Content is already written to document when generated in step 4. No additional append needed.
+
+## SUCCESS METRICS:
+
+✅ Key players and market leaders thoroughly identified
+✅ Market share and competitive positioning clearly mapped
+✅ Competitive strategies and differentiation analyzed
+✅ Business models and value propositions documented
+✅ Competitive dynamics and entry barriers evaluated
+✅ Content written immediately to document
+✅ [C] continue option presented and handled correctly
+✅ Proper routing to next step (regulatory focus)
+✅ Research goals alignment maintained
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in competitive web searches
+❌ Missing critical key players or market leaders
+❌ Incomplete market share or positioning analysis
+❌ Not identifying competitive strategies
+❌ Not writing content immediately to document
+❌ Not presenting [C] continue option after content generation
+❌ Not routing to regulatory focus step
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## COMPETITIVE RESEARCH PROTOCOLS:
+
+- Research competitive intelligence reports and market analyses
+- Use company websites, annual reports, and investor presentations
+- Analyze market share data and competitive positioning
+- Study competitive strategies and differentiation approaches
+- Focus on current {{current_year}} competitive data
+- Present conflicting information when sources disagree
+- Apply confidence levels appropriately
+
+## COMPETITIVE ANALYSIS STANDARDS:
+
+- Always cite URLs for web search results
+- Use authoritative competitive intelligence sources
+- Note data currency and potential limitations
+- Present multiple perspectives when sources conflict
+- Apply confidence levels to uncertain data
+- Focus on actionable competitive insights
+
+## NEXT STEP:
+
+After user selects 'C', load `./step-04-regulatory-focus.md` to analyze regulatory requirements, compliance frameworks, and legal considerations for {{research_topic}}.
+
+Remember: Always write research content to document immediately and emphasize current {{current_year}} competitive data with rigorous source verification!

src/modules/bmm/workflows/1-analysis/research/domain-steps/step-04-regulatory-focus.md

@@ -0,0 +1,205 @@
+# Domain Research Step 4: Regulatory Focus
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ 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
+- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] continue option after regulatory content generation
+- 📝 WRITE REGULATORY ANALYSIS TO DOCUMENT IMMEDIATELY
+- 💾 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
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- **Research topic = "{{research_topic}}"** - established from initial discussion
+- **Research goals = "{{research_goals}}"** - established from initial discussion
+- Focus on regulatory and compliance requirements for the domain
+- Web search capabilities with source verification are enabled
+
+## YOUR TASK:
+
+Conduct focused regulatory and compliance analysis using current {{current_year}} web data with emphasis on requirements that impact {{research_topic}}.
+
+## REGULATORY FOCUS SEQUENCE:
+
+### 1. Begin Regulatory Analysis
+
+Start with regulatory research approach:
+"Now I'll focus on **regulatory and compliance requirements** that impact **{{research_topic}}** 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: "{{research_topic}} 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: "{{research_topic}} 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 {{research_topic}} {{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 **regulatory requirements analysis** using current {{current_year}} data to understand compliance requirements for {{research_topic}}.
+
+**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):
+
+- **CONTENT ALREADY WRITTEN TO DOCUMENT**
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
+- Load: `./step-05-technical-trends.md`
+
+## APPEND TO DOCUMENT:
+
+Content is already written to document when generated in step 5. No additional append needed.
+
+## 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'
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## 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!

src/modules/bmm/workflows/1-analysis/research/domain-steps/step-05-technical-trends.md

@@ -0,0 +1,233 @@
+# Domain Research Step 5: Technical Trends
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ 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
+- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] continue option after technical trends content generation
+- 📝 WRITE TECHNICAL TRENDS ANALYSIS TO DOCUMENT IMMEDIATELY
+- 💾 ONLY proceed 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
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- **Research topic = "{{research_topic}}"** - established from initial discussion
+- **Research goals = "{{research_goals}}"** - established from initial discussion
+- Focus on emerging technologies and innovation patterns in the domain
+- Web search capabilities with source verification are enabled
+
+## YOUR TASK:
+
+Conduct comprehensive technical trends analysis using current {{current_year}} web data with emphasis on innovations and emerging technologies impacting {{research_topic}}.
+
+## TECHNICAL TRENDS SEQUENCE:
+
+### 1. Begin Technical Trends Analysis
+
+Start with technology research approach:
+"Now I'll conduct **technical trends and emerging technologies** analysis for **{{research_topic}}** 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: "{{research_topic}} 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: "{{research_topic}} 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: "{{research_topic}} 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
+
+**WRITE IMMEDIATELY TO DOCUMENT**
+
+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 **technical trends and innovation analysis** using current {{current_year}} data to understand technology patterns for {{research_topic}}.
+
+**Technical Highlights:**
+
+- Emerging technologies and innovations identified
+- Digital transformation trends mapped
+- Future outlook and projections analyzed
+- Implementation opportunities and challenges documented
+- Practical recommendations provided
+
+**Technical Trends Research Completed:**
+
+- Emerging technologies and innovations identified
+- Digital transformation trends mapped
+- Future outlook and projections analyzed
+- Implementation opportunities and challenges documented
+
+**Ready to proceed to research synthesis and recommendations?**
+[C] Continue - Save this to document and proceed to synthesis
+
+### 7. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- **CONTENT ALREADY WRITTEN TO DOCUMENT**
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
+- Load: `./step-06-research-synthesis.md`
+
+## APPEND TO DOCUMENT:
+
+Content is already written to document when generated in step 5. No additional append needed.
+
+## 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
+✅ Content written immediately to document
+✅ [C] continue option presented and handled correctly
+✅ Proper routing to next step (research synthesis)
+✅ Research goals alignment maintained
+
+## 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'
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## 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! 🎉

src/modules/bmm/workflows/1-analysis/research/domain-steps/step-06-research-synthesis.md

@@ -0,0 +1,443 @@
+# Domain Research Step 6: Research Synthesis and Completion
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ ALWAYS use {{current_year}} web searches for current domain data
+- 📋 YOU ARE A DOMAIN RESEARCH STRATEGIST, not content generator
+- 💬 FOCUS on comprehensive synthesis and authoritative conclusions
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+- 📄 PRODUCE COMPREHENSIVE DOCUMENT with narrative intro, TOC, and summary
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] complete option after synthesis content generation
+- 💾 ONLY save when user chooses C (Complete)
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6]` before completing workflow
+- 🚫 FORBIDDEN to complete workflow until C is selected
+- 📚 GENERATE COMPLETE DOCUMENT STRUCTURE with intro, TOC, and summary
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- **Research topic = "{{research_topic}}"** - comprehensive domain analysis
+- **Research goals = "{{research_goals}}"** - achieved through exhaustive research
+- All domain research sections have been completed (analysis, regulatory, technical)
+- Web search capabilities with source verification are enabled
+- This is the final synthesis step producing the complete research document
+
+## YOUR TASK:
+
+Produce a comprehensive, authoritative research document on **{{research_topic}}** with compelling narrative introduction, detailed TOC, and executive summary based on exhaustive domain research.
+
+## COMPREHENSIVE DOCUMENT SYNTHESIS:
+
+### 1. Document Structure Planning
+
+**Complete Research Document Structure:**
+
+```markdown
+# [Compelling Title]: Comprehensive {{research_topic}} Research
+
+## Executive Summary
+
+[Brief compelling overview of key findings and implications]
+
+## Table of Contents
+
+- Research Introduction and Methodology
+- Industry Overview and Market Dynamics
+- Technology Trends and Innovation Landscape
+- Regulatory Framework and Compliance Requirements
+- Competitive Landscape and Key Players
+- Strategic Insights and Recommendations
+- Implementation Considerations and Risk Assessment
+- Future Outlook and Strategic Opportunities
+- Research Methodology and Source Documentation
+- Appendices and Additional Resources
+```
+
+### 2. Generate Compelling Narrative Introduction
+
+**Introduction Requirements:**
+
+- Hook reader with compelling opening about {{research_topic}}
+- Establish research significance and timeliness
+- Outline comprehensive research methodology
+- Preview key findings and strategic implications
+- Set professional, authoritative tone
+
+**Web Search for Introduction Context:**
+`WebSearch: "{{research_topic}} significance importance {{current_year}}"`
+
+### 3. Synthesize All Research Sections
+
+**Section-by-Section Integration:**
+
+- Combine industry analysis from step-02
+- Integrate regulatory focus from step-03
+- Incorporate technical trends from step-04
+- Add cross-sectional insights and connections
+- Ensure comprehensive coverage with no gaps
+
+### 4. Generate Complete Document Content
+
+#### Final Document Structure:
+
+```markdown
+# [Compelling Title]: Comprehensive {{research_topic}} Domain Research
+
+## Executive Summary
+
+[2-3 paragraph compelling summary of the most critical findings and strategic implications for {{research_topic}} based on comprehensive {{current_year}} research]
+
+**Key Findings:**
+
+- [Most significant market dynamics]
+- [Critical regulatory considerations]
+- [Important technology trends]
+- [Strategic implications]
+
+**Strategic Recommendations:**
+
+- [Top 3-5 actionable recommendations based on research]
+
+## Table of Contents
+
+1. Research Introduction and Methodology
+2. {{research_topic}} Industry Overview and Market Dynamics
+3. Technology Landscape and Innovation Trends
+4. Regulatory Framework and Compliance Requirements
+5. Competitive Landscape and Ecosystem Analysis
+6. Strategic Insights and Domain Opportunities
+7. Implementation Considerations and Risk Assessment
+8. Future Outlook and Strategic Planning
+9. Research Methodology and Source Verification
+10. Appendices and Additional Resources
+
+## 1. Research Introduction and Methodology
+
+### Research Significance
+
+[Compelling narrative about why {{research_topic}} research is critical in {{current_year}}]
+_Why this research matters now: [Strategic importance with {{current_year}} context]_
+_Source: [URL with {{current_year}} industry significance data]_
+
+### Research Methodology
+
+[Comprehensive description of research approach including:]
+
+- **Research Scope**: [Comprehensive coverage areas]
+- **Data Sources**: [Authoritative sources and verification approach]
+- **Analysis Framework**: [Structured analysis methodology]
+- **Time Period**: [{{current_year}} focus and historical context]
+- **Geographic Coverage**: [Regional/global scope]
+
+### Research Goals and Objectives
+
+**Original Goals:** {{research_goals}}
+
+**Achieved Objectives:**
+
+- [Goal 1 achievement with supporting evidence]
+- [Goal 2 achievement with supporting evidence]
+- [Additional insights discovered during research]
+
+## 2. {{research_topic}} Industry Overview and Market Dynamics
+
+### Market Size and Growth Projections
+
+[Comprehensive market analysis synthesized from step-02 with {{current_year}} data]
+_Market Size: [Current market valuation]_
+_Growth Rate: [CAGR and projections]_
+_Market Drivers: [Key growth factors]_
+_Source: [URL with {{current_year}} market data]_
+
+### Industry Structure and Value Chain
+
+[Complete industry structure analysis]
+_Value Chain Components: [Detailed breakdown]_
+_Industry Segments: [Market segmentation analysis]_
+_Economic Impact: [Industry economic significance]_
+_Source: [URL with {{current_year}} industry structure data]_
+
+## 3. Technology Landscape and Innovation Trends
+
+### Current Technology Adoption
+
+[Technology trends analysis from step-04 with {{current_year}} context]
+_Emerging Technologies: [Key technologies affecting {{research_topic}}]_
+_Adoption Patterns: [Technology adoption rates and patterns]_
+_Innovation Drivers: [Factors driving technology change]_
+_Source: [URL with {{current_year}} technology data]_
+
+### Digital Transformation Impact
+
+[Comprehensive analysis of technology's impact on {{research_topic}}]
+_Transformation Trends: [Major digital transformation patterns]_
+_Disruption Opportunities: [Technology-driven opportunities]_
+_Future Technology Outlook: [Emerging technologies and timelines]_
+_Source: [URL with {{current_year}} digital transformation data]_
+
+## 4. Regulatory Framework and Compliance Requirements
+
+### Current Regulatory Landscape
+
+[Regulatory analysis from step-03 with {{current_year}} updates]
+_Key Regulations: [Critical regulatory requirements]_
+_Compliance Standards: [Industry standards and best practices]_
+_Recent Changes: [{{current_year}} regulatory updates and implications]_
+_Source: [URL with {{current_year}} regulatory data]_
+
+### Risk and Compliance Considerations
+
+[Comprehensive risk assessment]
+_Compliance Risks: [Major regulatory and compliance risks]_
+_Risk Mitigation Strategies: [Approaches to manage regulatory risks]_
+_Future Regulatory Trends: [Anticipated regulatory developments]_
+_Source: [URL with {{current_year}} compliance data]_
+
+## 5. Competitive Landscape and Ecosystem Analysis
+
+### Market Positioning and Key Players
+
+[Competitive analysis with {{current_year}} market positioning]
+_Market Leaders: [Dominant players and strategies]_
+_Emerging Competitors: [New entrants and innovative approaches]_
+_Competitive Dynamics: [Market competition patterns and trends]_
+_Source: [URL with {{current_year}} competitive data]_
+
+### Ecosystem and Partnership Landscape
+
+[Complete ecosystem analysis]
+_Ecosystem Players: [Key stakeholders and relationships]_
+_Partnership Opportunities: [Strategic collaboration potential]_
+_Supply Chain Dynamics: [Supply chain structure and risks]_
+_Source: [URL with {{current_year}} ecosystem data]_
+
+## 6. Strategic Insights and Domain Opportunities
+
+### Cross-Domain Synthesis
+
+[Strategic insights from integrating all research sections]
+_Market-Technology Convergence: [How technology and market forces interact]_
+_Regulatory-Strategic Alignment: [How regulatory environment shapes strategy]_
+_Competitive Positioning Opportunities: [Strategic advantages based on research]_
+_Source: [URL with {{current_year}} strategic analysis data]_
+
+### Strategic Opportunities
+
+[High-value opportunities identified through comprehensive research]
+_Market Opportunities: [Specific market entry or expansion opportunities]_
+_Technology Opportunities: [Technology adoption or innovation opportunities]_
+_Partnership Opportunities: [Strategic collaboration and partnership potential]_
+_Source: [URL with {{current_year}} opportunity data]_
+
+## 7. Implementation Considerations and Risk Assessment
+
+### Implementation Framework
+
+[Practical implementation guidance based on research findings]
+_Implementation Timeline: [Recommended phased approach]_
+_Resource Requirements: [Key resources and capabilities needed]_
+_Success Factors: [Critical success factors for implementation]_
+_Source: [URL with {{current_year}} implementation data]_
+
+### Risk Management and Mitigation
+
+[Comprehensive risk assessment and mitigation strategies]
+_Implementation Risks: [Major risks and mitigation approaches]_
+_Market Risks: [Market-related risks and contingency plans]_
+_Technology Risks: [Technology adoption and implementation risks]_
+_Source: [URL with {{current_year}} risk management data]_
+
+## 8. Future Outlook and Strategic Planning
+
+### Future Trends and Projections
+
+[Forward-looking analysis based on comprehensive research]
+_Near-term Outlook: [1-2 year projections and implications]_
+_Medium-term Trends: [3-5 year expected developments]_
+_Long-term Vision: [5+ year strategic outlook for {{research_topic}}]_
+_Source: [URL with {{current_year}} future outlook data]_
+
+### Strategic Recommendations
+
+[Comprehensive strategic recommendations]
+_Immediate Actions: [Priority actions for next 6 months]_
+_Strategic Initiatives: [Key strategic initiatives for 1-2 years]_
+_Long-term Strategy: [Strategic positioning for 3+ years]_
+_Source: [URL with {{current_year}} strategic planning data]_
+
+## 9. Research Methodology and Source Verification
+
+### Comprehensive Source Documentation
+
+[Complete documentation of all research sources]
+_Primary Sources: [Key authoritative sources used]_
+_Secondary Sources: [Supporting research and analysis]_
+_Web Search Queries: [Complete list of search queries used]_
+_Data Currency: [All data verified for {{current_year}} currency]_
+
+### Research Quality Assurance
+
+[Quality assurance and validation approach]
+_Source Verification: [All factual claims verified with multiple sources]_
+_Confidence Levels: [Confidence assessments for uncertain data]_
+_Limitations: [Research limitations and areas for further investigation]_
+_Methodology Transparency: [Complete transparency about research approach]_
+
+## 10. Appendices and Additional Resources
+
+### Detailed Data Tables
+
+[Comprehensive data tables supporting research findings]
+_Market Data Tables: [Detailed market size, growth, and segmentation data]_
+_Technology Adoption Data: [Detailed technology adoption and trend data]_
+_Regulatory Reference Tables: [Complete regulatory requirements and compliance data]_
+
+### Additional Resources
+
+[Valuable resources for continued research and implementation]
+_Industry Associations: [Key industry organizations and resources]_
+_Research Organizations: [Authoritative research institutions and reports]_
+_Government Resources: [Regulatory agencies and official resources]_
+_Professional Networks: [Industry communities and knowledge sources]_
+
+---
+
+## Research Conclusion
+
+### Summary of Key Findings
+
+[Comprehensive summary of the most important research findings]
+
+### Strategic Impact Assessment
+
+[Assessment of strategic implications for {{research_topic}}]
+
+### Next Steps Recommendations
+
+[Specific next steps for leveraging this research]
+
+---
+
+**Research Completion Date:** {{date}}
+**Research Period:** {{current_year}} comprehensive analysis
+**Document Length:** As needed for comprehensive coverage
+**Source Verification:** All facts cited with {{current_year}} sources
+**Confidence Level:** High - based on multiple authoritative sources
+
+_This comprehensive research document serves as an authoritative reference on {{research_topic}} and provides strategic insights for informed decision-making._
+```
+
+### 5. Present Complete Document and Final Option
+
+**Document Completion Presentation:**
+
+"I've completed the **comprehensive research document synthesis** for **{{research_topic}}**, producing an authoritative research document with:
+
+**Document Features:**
+
+- **Compelling Narrative Introduction**: Engaging opening that establishes research significance
+- **Comprehensive Table of Contents**: Complete navigation structure for easy reference
+- **Exhaustive Research Coverage**: All aspects of {{research_topic}} thoroughly analyzed
+- **Executive Summary**: Key findings and strategic implications highlighted
+- **Strategic Recommendations**: Actionable insights based on comprehensive research
+- **Complete Source Citations**: Every factual claim verified with {{current_year}} sources
+
+**Research Completeness:**
+
+- Industry analysis and market dynamics fully documented
+- Technology trends and innovation landscape comprehensively covered
+- Regulatory framework and compliance requirements detailed
+- Competitive landscape and ecosystem analysis complete
+- Strategic insights and implementation guidance provided
+
+**Document Standards Met:**
+
+- Exhaustive research with no critical gaps
+- Professional structure and compelling narrative
+- As long as needed for comprehensive coverage
+- Multiple independent sources for all claims
+- {{current_year}} data throughout with proper citations
+
+**Ready to complete this comprehensive research document?**
+[C] Complete Research - Save final comprehensive document
+
+### 6. Handle Final Completion
+
+#### If 'C' (Complete Research):
+
+- Append the complete document to the research file
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
+- Complete the domain research workflow
+- Provide final document delivery confirmation
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the complete comprehensive research document using the full structure above.
+
+## SUCCESS METRICS:
+
+✅ Compelling narrative introduction with research significance
+✅ Comprehensive table of contents with complete document structure
+✅ Exhaustive research coverage across all domain aspects
+✅ Executive summary with key findings and strategic implications
+✅ Strategic recommendations grounded in comprehensive research
+✅ Complete source verification with {{current_year}} citations
+✅ Professional document structure and compelling narrative
+✅ [C] complete option presented and handled correctly
+✅ Domain research workflow completed with comprehensive document
+
+## FAILURE MODES:
+
+❌ Not producing compelling narrative introduction
+❌ Missing comprehensive table of contents
+❌ Incomplete research coverage across domain aspects
+❌ Not providing executive summary with key findings
+❌ Missing strategic recommendations based on research
+❌ Not using {{current_year}} sources for all factual claims
+❌ Producing document without professional structure
+❌ Not presenting completion option for final document
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## COMPREHENSIVE DOCUMENT STANDARDS:
+
+This step ensures the final research document:
+
+- Serves as an authoritative reference on {{research_topic}}
+- Provides compelling narrative and professional structure
+- Includes comprehensive coverage with no gaps
+- Maintains rigorous source verification standards
+- Delivers strategic insights and actionable recommendations
+- Meets professional research document quality standards
+
+## DOMAIN RESEARCH WORKFLOW COMPLETION:
+
+When 'C' is selected:
+
+- All domain research steps completed (1-5)
+- Comprehensive domain research document generated
+- Professional document structure with intro, TOC, and summary
+- All sections appended with source citations
+- Domain research workflow status updated to complete
+- Final comprehensive research document delivered to user
+
+## FINAL DELIVERABLE:
+
+Complete authoritative research document on {{research_topic}} that:
+
+- Establishes professional credibility through comprehensive research
+- Provides strategic insights for informed decision-making
+- Serves as reference document for continued use
+- Maintains highest research quality standards with {{current_year}} verification
+
+Congratulations on completing comprehensive domain research with professional documentation! 🎉

src/modules/bmm/workflows/1-analysis/research/instructions-deep-prompt.md

@@ -1,438 +0,0 @@
-# Deep Research Prompt Generator Instructions
-
-<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
-<critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical>
-<critical>This workflow generates structured research prompts optimized for AI platforms</critical>
-<critical>Based on {{current_year}} best practices from ChatGPT, Gemini, Grok, and Claude</critical>
-<critical>Communicate all responses in {communication_language} and tailor to {user_skill_level}</critical>
-<critical>Generate all documents in {document_output_language}</critical>
-
-<critical>🚨 BUILD ANTI-HALLUCINATION INTO PROMPTS 🚨</critical>
-<critical>Generated prompts MUST instruct AI to cite sources with URLs for all factual claims</critical>
-<critical>Include validation requirements: "Cross-reference claims with at least 2 independent sources"</critical>
-<critical>Add explicit instructions: "If you cannot find reliable data, state 'No verified data found for [X]'"</critical>
-<critical>Require confidence indicators in prompts: "Mark each claim with confidence level and source quality"</critical>
-<critical>Include fact-checking instructions: "Distinguish between verified facts, analysis, and speculation"</critical>
-<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> 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.</critical>
-
-<workflow>
-
-<step n="1" goal="Discover what research prompt they need">
-
-<action>Engage conversationally to understand their needs:
-
-<check if="{user_skill_level} == 'expert'">
-  "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)"
-</check>
-
-<check if="{user_skill_level} == 'intermediate'">
-  "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?"
-</check>
-
-<check if="{user_skill_level} == 'beginner'">
-  "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?"
-</check>
-</action>
-
-<action>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.
-</action>
-
-<template-output>research_topic</template-output>
-<template-output>research_goal</template-output>
-<template-output>target_platform</template-output>
-
-</step>
-
-<step n="2" goal="Define Research Scope and Boundaries">
-<action>Help user define clear boundaries for focused research</action>
-
-**Let's define the scope to ensure focused, actionable results:**
-
-<ask>**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)</ask>
-
-<template-output>temporal_scope</template-output>
-
-<ask>**Geographic Scope** - What geographic focus?
-
-- Global
-- Regional (North America, Europe, Asia-Pacific, etc.)
-- Specific countries
-- US-focused
-- Other (specify)</ask>
-
-<template-output>geographic_scope</template-output>
-
-<ask>**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</ask>
-
-<template-output>thematic_boundaries</template-output>
-
-</step>
-
-<step n="3" goal="Specify Information Types and Sources">
-<action>Determine what types of information and sources are needed</action>
-
-**What types of information do you need?**
-
-<ask>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</ask>
-
-<template-output>information_types</template-output>
-
-<ask>**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)</ask>
-
-<template-output>preferred_sources</template-output>
-
-</step>
-
-<step n="4" goal="Define Output Structure and Format">
-<action>Specify desired output format for the research</action>
-
-<ask>**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)</ask>
-
-<template-output>output_format</template-output>
-
-<ask>**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</ask>
-
-<template-output>key_sections</template-output>
-
-<ask>**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)</ask>
-
-<template-output>depth_level</template-output>
-
-</step>
-
-<step n="5" goal="Add Context and Constraints">
-<action>Gather additional context to make the prompt more effective</action>
-
-<ask>**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</ask>
-
-<template-output>research_persona</template-output>
-
-<ask>**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</ask>
-
-<template-output>special_requirements</template-output>
-
-</step>
-
-<step n="6" goal="Define Validation and Follow-up Strategy">
-<action>Establish how to validate findings and what follow-ups might be needed</action>
-
-<ask>**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</ask>
-
-<template-output>validation_criteria</template-output>
-
-<ask>**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"</ask>
-
-<template-output>follow_up_strategy</template-output>
-
-</step>
-
-<step n="7" goal="Generate Optimized Research Prompt">
-<action>Synthesize all inputs into platform-optimized research prompt</action>
-
-<critical>Generate the deep research prompt using best practices for the target platform</critical>
-
-**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)
-
-<action>Generate prompt following this structure</action>
-
-<template-output file="deep-research-prompt.md">deep_research_prompt</template-output>
-
-<ask>Review the generated prompt:
-
-- [a] Accept and save
-- [e] Edit sections
-- [r] Refine with additional context
-- [o] Optimize for different platform</ask>
-
-<check if="edit or refine">
-  <ask>What would you like to adjust?</ask>
-  <goto step="7">Regenerate with modifications</goto>
-</check>
-
-</step>
-
-<step n="8" goal="Generate Platform-Specific Tips">
-<action>Provide platform-specific usage tips based on target platform</action>
-
-<check if="target_platform includes ChatGPT">
-  **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
-  </check>
-
-<check if="target_platform includes Gemini">
-  **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
-  </check>
-
-<check if="target_platform includes Grok">
-  **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
-  </check>
-
-<check if="target_platform includes Claude">
-  **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
-  </check>
-
-<template-output>platform_tips</template-output>
-
-</step>
-
-<step n="9" goal="Generate Research Execution Checklist">
-<action>Create a checklist for executing and evaluating the research</action>
-
-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
-
-<template-output>execution_checklist</template-output>
-
-</step>
-
-<step n="10" goal="Finalize and Export">
-<action>Save complete research prompt package</action>
-
-**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
-
-<action>Save all outputs to {default_output_file}</action>
-
-<ask>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):</ask>
-
-<check if="option 1">
-  <goto step="1">Start with different platform selection</goto>
-</check>
-
-<check if="option 2 or 3">
-  <goto step="1">Start new prompt with context from previous</goto>
-</check>
-
-</step>
-
-<step n="FINAL" goal="Update status file on completion" tag="workflow-status">
-<check if="standalone_mode != true">
-  <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
-  <action>Find workflow_status key "research"</action>
-  <critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
-  <action>Update workflow_status["research"] = "{output_folder}/bmm-research-deep-prompt-{{date}}.md"</action>
-  <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
-
-<action>Find first non-completed workflow in workflow_status (next workflow to do)</action>
-<action>Determine next agent from path file based on next workflow</action>
-</check>
-
-<output>**✅ Deep Research Prompt Generated**
-
-**Research Prompt:**
-
-- Structured research prompt generated and saved to {output_folder}/bmm-research-deep-prompt-{{date}}.md
-- Ready to execute with ChatGPT, Claude, Gemini, or Grok
-
-{{#if standalone_mode != true}}
-**Status Updated:**
-
-- Progress tracking updated: research marked complete
-- Next workflow: {{next_workflow}}
-  {{else}}
-  **Note:** Running in standalone mode (no progress tracking)
-  {{/if}}
-
-**Next Steps:**
-
-{{#if standalone_mode != true}}
-
-- **Next workflow:** {{next_workflow}} ({{next_agent}} agent)
-- **Optional:** Execute the research prompt with AI platform, gather findings, or run additional research workflows
-
-Check status anytime with: `workflow-status`
-{{else}}
-Since no workflow is in progress:
-
-- Execute the research prompt with AI platform and gather findings
-- Refer to the BMM workflow guide if unsure what to do next
-- Or run `workflow-init` to create a workflow path and get guided next steps
-  {{/if}}
-  </output>
-  </step>
-
-</workflow>

src/modules/bmm/workflows/1-analysis/research/instructions-market.md

@@ -1,675 +0,0 @@
-# Market Research Workflow Instructions
-
-<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
-<critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical>
-<critical>This is a HIGHLY INTERACTIVE workflow - collaborate with user throughout, don't just gather info and disappear</critical>
-<critical>Web research is MANDATORY - use WebSearch tool with {{current_year}} for all market intelligence gathering</critical>
-<critical>Communicate all responses in {communication_language} and tailor to {user_skill_level}</critical>
-<critical>Generate all documents in {document_output_language}</critical>
-
-<critical>🚨 ANTI-HALLUCINATION PROTOCOL - MANDATORY 🚨</critical>
-<critical>NEVER invent market data - if you cannot find reliable data, explicitly state: "I could not find verified data for [X]"</critical>
-<critical>EVERY statistic, market size, growth rate, or competitive claim MUST have a cited source with URL</critical>
-<critical>For CRITICAL claims (TAM/SAM/SOM, market size, growth rates), require 2+ independent sources that agree</critical>
-<critical>When data sources conflict (e.g., different market size estimates), present ALL estimates with sources and explain variance</critical>
-<critical>Mark data confidence: [Verified - 2+ sources], [Single source - verify], [Estimated - low confidence]</critical>
-<critical>Clearly label: FACT (sourced data), ANALYSIS (your interpretation), PROJECTION (forecast/speculation)</critical>
-<critical>After each WebSearch, extract and store source URLs - include them in the report</critical>
-<critical>If a claim seems suspicious or too convenient, STOP and cross-verify with additional searches</critical>
-<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> 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.</critical>
-
-<!-- IDE-INJECT-POINT: market-research-subagents -->
-
-<workflow>
-
-<step n="1" goal="Discover research needs and scope collaboratively">
-
-<action>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.
-</action>
-
-<action>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
-  </action>
-
-<action>Reflect understanding back to confirm you're aligned on what matters.</action>
-
-<template-output>product_name</template-output>
-<template-output>product_description</template-output>
-<template-output>research_objectives</template-output>
-<template-output>research_scope</template-output>
-</step>
-
-<step n="2" goal="Market Definition and Boundaries">
-<action>Help the user precisely define the market scope</action>
-
-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
-
-<ask>Should we include adjacent markets in the TAM calculation? This could significantly increase market size but may be less immediately addressable.</ask>
-
-<template-output>market_definition</template-output>
-<template-output>geographic_scope</template-output>
-<template-output>segment_boundaries</template-output>
-</step>
-
-<step n="3" goal="Gather live market intelligence collaboratively">
-
-<critical>This step REQUIRES WebSearch tool usage - gather CURRENT data from {{current_year}}</critical>
-<critical>Share findings as you go - make this collaborative, not a black box</critical>
-
-<action>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.</action>
-
-<step n="3a" title="Search for market size and industry data">
-<action>Conduct systematic web searches using WebSearch tool:
-
-<WebSearch>{{market_category}} market size {{geographic_scope}} {{current_year}}</WebSearch>
-<WebSearch>{{market_category}} industry report Gartner Forrester IDC {{current_year}}</WebSearch>
-<WebSearch>{{market_category}} market growth rate CAGR forecast {{current_year}}</WebSearch>
-<WebSearch>{{market_category}} market trends {{current_year}}</WebSearch>
-<WebSearch>{{market_category}} TAM SAM market opportunity {{current_year}}</WebSearch>
-</action>
-
-<action>Share findings WITH SOURCES including URLs and dates. Ask if it aligns with their expectations.</action>
-
-<action>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]
-  </action>
-
-<action if="user_has_questions">Explore surprising data points together</action>
-
-<template-output>sources_market_size</template-output>
-</step>
-
-<step n="3b" title="Search for recent news and developments" optional="true">
-<action>Search for recent market developments:
-
-<WebSearch>{{market_category}} news {{current_year}} funding acquisitions</WebSearch>
-<WebSearch>{{market_category}} recent developments {{current_year}}</WebSearch>
-<WebSearch>{{market_category}} regulatory changes {{current_year}}</WebSearch>
-</action>
-
-<action>Share noteworthy findings:
-
-"I found some interesting recent developments:
-
-{{key_news_highlights}}
-
-Anything here surprise you or confirm what you suspected?"
-</action>
-</step>
-
-<step n="3c" title="Optional: Government and academic sources" optional="true">
-<action if="research needs high credibility">Search for authoritative sources:
-
-<WebSearch>{{market_category}} government statistics census data {{current_year}}</WebSearch>
-<WebSearch>{{market_category}} academic research white papers {{current_year}}</WebSearch>
-</action>
-</step>
-
-<template-output>market_intelligence_raw</template-output>
-<template-output>key_data_points</template-output>
-<template-output>source_credibility_notes</template-output>
-</step>
-
-<step n="4" goal="TAM, SAM, SOM Calculations">
-<action>Calculate market sizes using multiple methodologies for triangulation</action>
-
-<critical>Use actual data gathered in previous steps, not hypothetical numbers</critical>
-
-<step n="4a" title="TAM Calculation">
-**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
-
-<ask>Which TAM calculation method seems most credible given our data? Should we use multiple methods and triangulate?</ask>
-
-<template-output>tam_calculation</template-output>
-<template-output>tam_methodology</template-output>
-</step>
-
-<step n="4b" title="SAM Calculation">
-<action>Calculate Serviceable Addressable Market</action>
-
-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.
-
-<template-output>sam_calculation</template-output>
-</step>
-
-<step n="4c" title="SOM Calculation">
-<action>Calculate realistic market capture</action>
-
-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)
-
-<template-output>som_scenarios</template-output>
-</step>
-</step>
-
-<step n="5" goal="Customer Segment Deep Dive">
-<action>Develop detailed understanding of target customers</action>
-
-<step n="5a" title="Segment Identification" repeat="for-each-segment">
-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
-
-<template-output>segment*profile*{{segment_number}}</template-output>
-</step>
-
-<step n="5b" title="Jobs-to-be-Done Framework">
-<action>Apply JTBD framework to understand customer needs</action>
-
-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
-
-<ask>Would you like to conduct actual customer interviews or surveys to validate these jobs? (We can create an interview guide)</ask>
-
-<template-output>jobs_to_be_done</template-output>
-</step>
-
-<step n="5c" title="Willingness to Pay Analysis">
-<action>Research and estimate pricing sensitivity</action>
-
-Analyze:
-
-- Current spending on alternatives
-- Budget allocation for this category
-- Value perception indicators
-- Price points of substitutes
-
-<template-output>pricing_analysis</template-output>
-</step>
-</step>
-
-<step n="6" goal="Understand the competitive landscape">
-<action>Ask if they know their main competitors or if you should search for them.</action>
-
-<step n="6a" title="Discover competitors together">
-<action if="user doesn't know competitors">Search for competitors:
-
-<WebSearch>{{product_category}} competitors {{geographic_scope}} {{current_year}}</WebSearch>
-<WebSearch>{{product_category}} alternatives comparison {{current_year}}</WebSearch>
-<WebSearch>top {{product_category}} companies {{current_year}}</WebSearch>
-</action>
-
-<action>Present findings. Ask them to pick the 3-5 that matter most (most concerned about or curious to understand).</action>
-</step>
-
-<step n="6b" title="Research each competitor together" repeat="for-each-selected-competitor">
-<action>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.
-</action>
-
-<action>Share findings with sources. Ask what jumps out and if it matches expectations.</action>
-
-<action if="user has follow-up questions">Dig deeper based on their interests</action>
-
-<template-output>competitor-analysis-{{competitor_name}}</template-output>
-</step>
-
-<step n="6c" title="Competitive Positioning Map">
-<action>Create positioning analysis</action>
-
-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
-
-<template-output>competitive_positioning</template-output>
-</step>
-</step>
-
-<step n="7" goal="Industry Forces Analysis">
-<action>Apply Porter's Five Forces framework</action>
-
-<critical>Use specific evidence from research, not generic assessments</critical>
-
-Analyze each force with concrete examples:
-
-<step n="7a" title="Supplier Power">
-Rate: [Low/Medium/High]
-- Key suppliers and dependencies
-- Switching costs
-- Concentration of suppliers
-- Forward integration threat
-</step>
-
-<step n="7b" title="Buyer Power">
-Rate: [Low/Medium/High]
-- Customer concentration
-- Price sensitivity
-- Switching costs for customers
-- Backward integration threat
-</step>
-
-<step n="7c" title="Competitive Rivalry">
-Rate: [Low/Medium/High]
-- Number and strength of competitors
-- Industry growth rate
-- Exit barriers
-- Differentiation levels
-</step>
-
-<step n="7d" title="Threat of New Entry">
-Rate: [Low/Medium/High]
-- Capital requirements
-- Regulatory barriers
-- Network effects
-- Brand loyalty
-</step>
-
-<step n="7e" title="Threat of Substitutes">
-Rate: [Low/Medium/High]
-- Alternative solutions
-- Switching costs to substitutes
-- Price-performance trade-offs
-</step>
-
-<template-output>porters_five_forces</template-output>
-</step>
-
-<step n="8" goal="Market Trends and Future Outlook">
-<action>Identify trends and future market dynamics</action>
-
-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
-
-<ask>Should we explore any specific emerging technologies or disruptions that could reshape this market?</ask>
-
-<template-output>market_trends</template-output>
-<template-output>future_outlook</template-output>
-</step>
-
-<step n="9" goal="Opportunity Assessment and Strategy">
-<action>Synthesize research into strategic opportunities</action>
-
-<step n="9a" title="Opportunity Identification">
-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
-
-<template-output>market_opportunities</template-output>
-</step>
-
-<step n="9b" title="Go-to-Market Recommendations">
-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
-
-<template-output>gtm_strategy</template-output>
-</step>
-
-<step n="9c" title="Risk Analysis">
-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.
-
-<template-output>risk_assessment</template-output>
-</step>
-</step>
-
-<step n="10" goal="Financial Projections" optional="true" if="enable_financial_modeling == true">
-<action>Create financial model based on market research</action>
-
-<ask>Would you like to create a financial model with revenue projections based on the market analysis?</ask>
-
-<check if="yes">
-  Build 3-year projections:
-
-- Revenue model based on SOM scenarios
-- Customer acquisition projections
-- Unit economics
-- Break-even analysis
-- Funding requirements
-
-<template-output>financial_projections</template-output>
-</check>
-
-</step>
-
-<step n="11" goal="Synthesize findings together into executive summary">
-
-<critical>This is the last major content section - make it collaborative</critical>
-
-<action>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.</action>
-
-<action>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.
-</action>
-
-<action>Draft executive summary and share. Ask if it captures the essence and if anything is missing or overemphasized.</action>
-
-<template-output>executive_summary</template-output>
-</step>
-
-<step n="12" goal="Validate sources and compile report">
-
-<critical>MANDATORY SOURCE VALIDATION - Do NOT skip this step!</critical>
-
-<action>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
-      </action>
-
-<action>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.
-</action>
-
-<action>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
-  </action>
-
-<action>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?"
-</action>
-
-<ask>Would you like to review any specific sections before finalizing? Are there any additional analyses you'd like to include?</ask>
-
-<goto step="9a" if="user requests changes">Return to refine opportunities</goto>
-
-<template-output>final_report_ready</template-output>
-<template-output>source_audit_complete</template-output>
-</step>
-
-<step n="13" goal="Appendices and Supporting Materials" optional="true">
-<ask>Would you like to include detailed appendices with calculations, full competitor profiles, or raw research data?</ask>
-
-<check if="yes">
-  Create appendices with:
-
-- Detailed TAM/SAM/SOM calculations
-- Full competitor profiles
-- Customer interview notes
-- Data sources and methodology
-- Financial model details
-- Glossary of terms
-
-<template-output>appendices</template-output>
-</check>
-
-</step>
-
-<step n="14" goal="Update status file on completion" tag="workflow-status">
-<check if="standalone_mode != true">
-  <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
-  <action>Find workflow_status key "research"</action>
-  <critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
-  <action>Update workflow_status["research"] = "{output_folder}/bmm-research-{{research_mode}}-{{date}}.md"</action>
-  <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
-
-<action>Find first non-completed workflow in workflow_status (next workflow to do)</action>
-<action>Determine next agent from path file based on next workflow</action>
-</check>
-
-<output>**✅ Research Complete ({{research_mode}} mode)**
-
-**Research Report:**
-
-- Research report generated and saved to {output_folder}/bmm-research-{{research_mode}}-{{date}}.md
-
-{{#if standalone_mode != true}}
-**Status Updated:**
-
-- Progress tracking updated: research marked complete
-- Next workflow: {{next_workflow}}
-  {{else}}
-  **Note:** Running in standalone mode (no progress tracking)
-  {{/if}}
-
-**Next Steps:**
-
-{{#if standalone_mode != true}}
-
-- **Next workflow:** {{next_workflow}} ({{next_agent}} agent)
-- **Optional:** Review findings with stakeholders, or run additional analysis workflows (product-brief for software, or install BMGD module for game-brief)
-
-Check status anytime with: `workflow-status`
-{{else}}
-Since no workflow is in progress:
-
-- Review research findings
-- Refer to the BMM workflow guide if unsure what to do next
-- Or run `workflow-init` to create a workflow path and get guided next steps
-  {{/if}}
-  </output>
-  </step>
-
-</workflow>

src/modules/bmm/workflows/1-analysis/research/instructions-router.md

@@ -1,134 +0,0 @@
-# Research Workflow Router Instructions
-
-<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
-<critical>Communicate in {communication_language}, generate documents in {document_output_language}</critical>
-<critical>Web research is ENABLED - always use current {{current_year}} data</critical>
-
-<critical>🚨 ANTI-HALLUCINATION PROTOCOL - MANDATORY 🚨</critical>
-<critical>NEVER present information without a verified source - if you cannot find a source, say "I could not find reliable data on this"</critical>
-<critical>ALWAYS cite sources with URLs when presenting data, statistics, or factual claims</critical>
-<critical>REQUIRE at least 2 independent sources for critical claims (market size, growth rates, competitive data)</critical>
-<critical>When sources conflict, PRESENT BOTH views and note the discrepancy - do NOT pick one arbitrarily</critical>
-<critical>Flag any data you are uncertain about with confidence levels: [High Confidence], [Medium Confidence], [Low Confidence - verify]</critical>
-<critical>Distinguish clearly between: FACTS (from sources), ANALYSIS (your interpretation), and SPECULATION (educated guesses)</critical>
-<critical>When using WebSearch results, ALWAYS extract and include the source URL for every claim</critical>
-<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> 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.</critical>
-
-<!-- IDE-INJECT-POINT: research-subagents -->
-
-<workflow>
-
-<critical>This is a ROUTER that directs to specialized research instruction sets</critical>
-
-<step n="1" goal="Validate workflow readiness" tag="workflow-status">
-<action>Check if {output_folder}/bmm-workflow-status.yaml exists</action>
-
-<check if="status file not found">
-  <output>No workflow status file found. Research is optional - you can continue without status tracking.</output>
-  <action>Set standalone_mode = true</action>
-</check>
-
-<check if="status file found">
-  <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
-  <action>Parse workflow_status section</action>
-  <action>Check status of "research" workflow</action>
-  <action>Get project_level from YAML metadata</action>
-  <action>Find first non-completed workflow (next expected workflow)</action>
-  <action>Pass status context to loaded instruction set for final update</action>
-
-  <check if="research status is file path (already completed)">
-    <output>⚠️ Research already completed: {{research status}}</output>
-    <ask>Re-running will create a new research report. Continue? (y/n)</ask>
-    <check if="n">
-      <output>Exiting. Use workflow-status to see your next step.</output>
-      <action>Exit workflow</action>
-    </check>
-  </check>
-
-  <check if="research is not the next expected workflow (latter items are completed already in the list)">
-    <output>⚠️ Next expected workflow: {{next_workflow}}. Research is out of sequence.</output>
-    <output>Note: Research can provide valuable insights at any project stage.</output>
-    <ask>Continue with Research anyway? (y/n)</ask>
-    <check if="n">
-      <output>Exiting. Run {{next_workflow}} instead.</output>
-      <action>Exit workflow</action>
-    </check>
-  </check>
-
-<action>Set standalone_mode = false</action>
-</check>
-</step>
-
-<step n="2" goal="Discover research needs through conversation">
-
-<action>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.</action>
-
-<action>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.
-</action>
-
-<action>Capture {{research_type}} and {{research_mode}}</action>
-
-<template-output>research_type_discovery</template-output>
-</step>
-
-<step n="3" goal="Route to Appropriate Research Instructions">
-
-<critical>Based on user selection, load the appropriate instruction set</critical>
-
-<check if="research_type == 1 OR fuzzy match market research">
-  <action>Set research_mode = "market"</action>
-  <action>LOAD: {installed_path}/instructions-market.md</action>
-  <action>Continue with market research workflow</action>
-</check>
-
-<check if="research_type == 2 or prompt or fuzzy match deep research prompt">
-  <action>Set research_mode = "deep-prompt"</action>
-  <action>LOAD: {installed_path}/instructions-deep-prompt.md</action>
-  <action>Continue with deep research prompt generation</action>
-</check>
-
-<check if="research_type == 3 technical or architecture or fuzzy match indicates technical type of research">
-  <action>Set research_mode = "technical"</action>
-  <action>LOAD: {installed_path}/instructions-technical.md</action>
-  <action>Continue with technical research workflow</action>
-
-</check>
-
-<check if="research_type == 4 or fuzzy match competitive">
-  <action>Set research_mode = "competitive"</action>
-  <action>This will use market research workflow with competitive focus</action>
-  <action>LOAD: {installed_path}/instructions-market.md</action>
-  <action>Pass mode="competitive" to focus on competitive intelligence</action>
-
-</check>
-
-<check if="research_type == 5 or fuzzy match user research">
-  <action>Set research_mode = "user"</action>
-  <action>This will use market research workflow with user research focus</action>
-  <action>LOAD: {installed_path}/instructions-market.md</action>
-  <action>Pass mode="user" to focus on customer insights</action>
-
-</check>
-
-<check if="research_type == 6 or fuzzy match domain or industry or category">
-  <action>Set research_mode = "domain"</action>
-  <action>This will use market research workflow with domain focus</action>
-  <action>LOAD: {installed_path}/instructions-market.md</action>
-  <action>Pass mode="domain" to focus on industry/domain analysis</action>
-</check>
-
-<critical>The loaded instruction set will continue from here with full context of the {research_type}</critical>
-
-</step>
-
-</workflow>

src/modules/bmm/workflows/1-analysis/research/instructions-technical.md

@@ -1,534 +0,0 @@
-# Technical/Architecture Research Instructions
-
-<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
-<critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical>
-<critical>This is a HIGHLY INTERACTIVE workflow - make technical decisions WITH user, not FOR them</critical>
-<critical>Web research is MANDATORY - use WebSearch tool with {{current_year}} for current version info and trends</critical>
-<critical>ALWAYS verify current versions - NEVER use hardcoded or outdated version numbers</critical>
-<critical>Communicate all responses in {communication_language} and tailor to {user_skill_level}</critical>
-<critical>Generate all documents in {document_output_language}</critical>
-
-<critical>🚨 ANTI-HALLUCINATION PROTOCOL - MANDATORY 🚨</critical>
-<critical>NEVER invent version numbers, features, or technical details - ALWAYS verify with current {{current_year}} sources</critical>
-<critical>Every technical claim (version, feature, performance, compatibility) MUST have a cited source with URL</critical>
-<critical>Version numbers MUST be verified via WebSearch - do NOT rely on training data (it's outdated!)</critical>
-<critical>When comparing technologies, cite sources for each claim (performance benchmarks, community size, etc.)</critical>
-<critical>Mark confidence levels: [Verified {{current_year}} source], [Older source - verify], [Uncertain - needs verification]</critical>
-<critical>Distinguish: FACT (from official docs/sources), OPINION (from community/reviews), SPECULATION (your analysis)</critical>
-<critical>If you cannot find current information about a technology, state: "I could not find recent {{current_year}} data on [X]"</critical>
-<critical>Extract and include source URLs in all technology profiles and comparisons</critical>
-<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> 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.</critical>
-
-<workflow>
-
-<step n="1" goal="Discover technical research needs through conversation">
-
-<action>Engage conversationally based on skill level:
-
-<check if="{user_skill_level} == 'expert'">
-  "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?"
-</check>
-
-<check if="{user_skill_level} == 'intermediate'">
-  "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?"
-</check>
-
-<check if="{user_skill_level} == 'beginner'">
-  "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?"
-</check>
-</action>
-
-<action>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.
-</action>
-
-<template-output>technical_question</template-output>
-<template-output>project_context</template-output>
-
-</step>
-
-<step n="2" goal="Define Technical Requirements and Constraints">
-<action>Gather requirements and constraints that will guide the research</action>
-
-**Let's define your technical requirements:**
-
-<ask>**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</ask>
-
-<template-output>functional_requirements</template-output>
-
-<ask>**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</ask>
-
-<template-output>non_functional_requirements</template-output>
-
-<ask>**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</ask>
-
-<template-output>technical_constraints</template-output>
-
-</step>
-
-<step n="3" goal="Discover and evaluate technology options together">
-
-<critical>MUST use WebSearch to find current options from {{current_year}}</critical>
-
-<action>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?"
-</action>
-
-<action if="user has candidates">Great! Let's research: {{user_candidates}}</action>
-
-<action if="discovering options">Search for current leading technologies:
-
-<WebSearch>{{technical_category}} best tools {{current_year}}</WebSearch>
-<WebSearch>{{technical_category}} comparison {{use_case}} {{current_year}}</WebSearch>
-<WebSearch>{{technical_category}} popular frameworks {{current_year}}</WebSearch>
-<WebSearch>state of {{technical_category}} {{current_year}}</WebSearch>
-</action>
-
-<action>Share findings conversationally:
-
-"Based on current {{current_year}} data, here are the main options:
-
-{{discovered_options}}
-
-<check if="{user_skill_level} == 'expert'">
-These are the leaders right now. Which ones make sense to evaluate for your use case?"
-</check>
-
-<check if="{user_skill_level} == 'beginner'">
-Each of these is popular for different reasons. Let me know if you want me to explain what makes each one different."
-</check>
-</action>
-
-<template-output>technology_options</template-output>
-
-</step>
-
-<step n="4" goal="Research each technology together in depth">
-
-<critical>For each option, use WebSearch to gather CURRENT {{current_year}} information</critical>
-
-<step n="4a" title="Deep dive on each technology" repeat="for-each-option">
-
-<action>For {{technology_name}}, conduct comprehensive research:
-
-<WebSearch>{{technology_name}} overview what is {{current_year}}</WebSearch>
-<WebSearch>{{technology_name}} latest version release notes {{current_year}}</WebSearch>
-<WebSearch>{{technology_name}} pros cons trade-offs {{current_year}}</WebSearch>
-<WebSearch>{{technology_name}} production experience real world {{current_year}}</WebSearch>
-<WebSearch>{{technology_name}} vs alternatives comparison {{current_year}}</WebSearch>
-</action>
-
-<action>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
-
-<template-output>tech*profile*{{option_number}}</template-output>
-
-</step>
-
-</step>
-
-<step n="5" goal="Comparative Analysis">
-<action>Create structured comparison across all options</action>
-
-**Create comparison matrices:**
-
-<action>Generate comparison table with key dimensions:</action>
-
-**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
-
-<action>Rate each option on relevant dimensions (High/Medium/Low or 1-5 scale)</action>
-
-<template-output>comparative_analysis</template-output>
-
-</step>
-
-<step n="6" goal="Trade-offs and Decision Factors">
-<action>Analyze trade-offs between options</action>
-
-**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:**
-
-<ask>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</ask>
-
-<template-output>decision_priorities</template-output>
-
-<action>Weight the comparison analysis by decision priorities</action>
-
-<template-output>weighted_analysis</template-output>
-
-</step>
-
-<step n="7" goal="Use Case Fit Analysis">
-<action>Evaluate fit for specific use case</action>
-
-**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.
-
-<ask>Are there any specific concerns or "must-haves" that would immediately eliminate any options?</ask>
-
-<template-output>use_case_fit</template-output>
-
-</step>
-
-<step n="8" goal="Real-World Evidence">
-<action>Gather production experience evidence</action>
-
-**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
-
-<template-output>real_world_evidence</template-output>
-
-</step>
-
-<step n="9" goal="Architecture Pattern Research" optional="true">
-<action>If researching architecture patterns, provide pattern analysis</action>
-
-<ask>Are you researching architecture patterns (microservices, event-driven, etc.)?</ask>
-
-<check if="yes">
-
-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
-
-<template-output>architecture_pattern_analysis</template-output>
-</check>
-
-</step>
-
-<step n="10" goal="Recommendations and Decision Framework">
-<action>Synthesize research into clear recommendations</action>
-
-**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
-
-<template-output>recommendations</template-output>
-
-</step>
-
-<step n="11" goal="Decision Documentation">
-<action>Create architecture decision record (ADR) template</action>
-
-**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]
-```
-
-<template-output>architecture_decision_record</template-output>
-
-</step>
-
-<step n="12" goal="Finalize Technical Research Report">
-<action>Compile complete technical research report</action>
-
-**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
-
-<action>Save complete report to {default_output_file}</action>
-
-<ask>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):</ask>
-
-<check if="option 4">
-  <action>LOAD: {installed_path}/instructions-deep-prompt.md</action>
-  <action>Pre-populate with technical research context</action>
-</check>
-
-</step>
-
-<step n="FINAL" goal="Update status file on completion" tag="workflow-status">
-<check if="standalone_mode != true">
-  <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
-  <action>Find workflow_status key "research"</action>
-  <critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
-  <action>Update workflow_status["research"] = "{output_folder}/bmm-research-technical-{{date}}.md"</action>
-  <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
-
-<action>Find first non-completed workflow in workflow_status (next workflow to do)</action>
-<action>Determine next agent from path file based on next workflow</action>
-</check>
-
-<output>**✅ Technical Research Complete**
-
-**Research Report:**
-
-- Technical research report generated and saved to {output_folder}/bmm-research-technical-{{date}}.md
-
-{{#if standalone_mode != true}}
-**Status Updated:**
-
-- Progress tracking updated: research marked complete
-- Next workflow: {{next_workflow}}
-  {{else}}
-  **Note:** Running in standalone mode (no progress tracking)
-  {{/if}}
-
-**Next Steps:**
-
-{{#if standalone_mode != true}}
-
-- **Next workflow:** {{next_workflow}} ({{next_agent}} agent)
-- **Optional:** Review findings with architecture team, or run additional analysis workflows
-
-Check status anytime with: `workflow-status`
-{{else}}
-Since no workflow is in progress:
-
-- Review technical research findings
-- Refer to the BMM workflow guide if unsure what to do next
-- Or run `workflow-init` to create a workflow path and get guided next steps
-  {{/if}}
-  </output>
-  </step>
-
-</workflow>

src/modules/bmm/workflows/1-analysis/research/market-steps/step-01-init.md

@@ -0,0 +1,182 @@
+# Market Research Step 1: Market Research Initialization
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate research content in init step
+- ✅ ALWAYS confirm understanding of user's research goals
+- 📋 YOU ARE A MARKET RESEARCH FACILITATOR, not content generator
+- 💬 FOCUS on clarifying scope and approach
+- 🔍 NO WEB RESEARCH in init - that's for later steps
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete research
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Confirm research understanding before proceeding
+- ⚠️ Present [C] continue option after scope clarification
+- 💾 Write initial scope document immediately
+- 📖 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
+- **Research topic = "{{research_topic}}"** - discovered from initial discussion
+- **Research goals = "{{research_goals}}"** - captured from initial discussion
+- Focus on market research scope clarification
+- Web search capabilities are enabled for later steps
+
+## YOUR TASK:
+
+Initialize market research by confirming understanding of {{research_topic}} and establishing clear research scope.
+
+## MARKET RESEARCH INITIALIZATION:
+
+### 1. Confirm Research Understanding
+
+**INITIALIZE - DO NOT RESEARCH YET**
+
+Start with research confirmation:
+"I understand you want to conduct **market research** for **{{research_topic}}** with these goals: {{research_goals}}
+
+**My Understanding of Your Research Needs:**
+
+- **Research Topic**: {{research_topic}}
+- **Research Goals**: {{research_goals}}
+- **Research Type**: Market Research using current {{current_year}} data
+- **Approach**: Comprehensive market analysis with rigorous source verification
+
+**Market Research Areas We'll Cover:**
+
+- Market size, growth dynamics, and trends
+- Customer insights and behavior analysis
+- Competitive landscape and positioning
+- Strategic recommendations and implementation guidance
+
+**Does this accurately capture what you're looking for?**"
+
+### 2. Refine Research Scope
+
+Gather any clarifications needed:
+
+#### Scope Clarification Questions:
+
+- "Are there specific customer segments or aspects of {{research_topic}} we should prioritize?"
+- "Should we focus on specific geographic regions or global market?"
+- "Is this for market entry, expansion, product development, or other business purpose?"
+- "Any competitors or market segments you specifically want us to analyze?"
+
+### 3. Document Initial Scope
+
+**WRITE IMMEDIATELY TO DOCUMENT**
+
+Write initial research scope to document:
+
+```markdown
+# Market Research: {{research_topic}}
+
+## Research Initialization
+
+### Research Understanding Confirmed
+
+**Topic**: {{research_topic}}
+**Goals**: {{research_goals}}
+**Research Type**: Market Research
+**Data Currency**: {{current_year}} with rigorous source verification
+**Date**: {{date}}
+
+### Research Scope
+
+**Market Analysis Focus Areas:**
+
+- Market size, growth projections, and dynamics
+- Customer segments, behavior patterns, and insights
+- Competitive landscape and positioning analysis
+- Strategic recommendations and implementation guidance
+
+**Research Methodology:**
+
+- Current {{current_year}} web data with source verification
+- Multiple independent sources for critical claims
+- Confidence level assessment for uncertain data
+- Comprehensive coverage with no critical gaps
+
+### Next Steps
+
+**Research Workflow:**
+
+1. ✅ Initialization and scope setting (current step)
+2. Customer Insights and Behavior Analysis
+3. Competitive Landscape Analysis
+4. Strategic Synthesis and Recommendations
+
+**Research Status**: Scope confirmed, ready to proceed with detailed market analysis
+```
+
+### 4. Present Confirmation and Continue Option
+
+Show initial scope document and present continue option:
+"I've documented our understanding and initial scope for **{{research_topic}}** market research.
+
+**What I've established:**
+
+- Research topic and goals confirmed
+- Market analysis focus areas defined
+- Research methodology with {{current_year}} data verification
+- Clear workflow progression
+
+**Document Status:** Initial scope written to research file for your review
+
+**Ready to begin detailed market research?**
+[C] Continue - Confirm scope and proceed to customer insights analysis
+[Modify] Suggest changes to research scope before proceeding
+
+### 5. Handle User Response
+
+#### If 'C' (Continue):
+
+- Update frontmatter: `stepsCompleted: [1]`
+- Add confirmation note to document: "Scope confirmed by user on {{date}}"
+- Load: `./step-02-customer-insights.md`
+
+#### If 'Modify':
+
+- Gather user changes to scope
+- Update document with modifications
+- Re-present updated scope for confirmation
+
+## SUCCESS METRICS:
+
+✅ Research topic and goals accurately understood
+✅ Market research scope clearly defined
+✅ Initial scope document written immediately
+✅ User opportunity to review and modify scope
+✅ [C] continue option presented and handled correctly
+✅ Document properly updated with scope confirmation
+
+## FAILURE MODES:
+
+❌ Not confirming understanding of research topic and goals
+❌ Generating research content instead of just scope clarification
+❌ Not writing initial scope document to file
+❌ Not providing opportunity for user to modify scope
+❌ Proceeding to next step without user confirmation
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor research decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## INITIALIZATION PRINCIPLES:
+
+This step ensures:
+
+- Clear mutual understanding of research objectives
+- Well-defined research scope and approach
+- Immediate documentation for user review
+- User control over research direction before detailed work begins
+
+## NEXT STEP:
+
+After user confirmation and scope finalization, load `./step-02-customer-insights.md` to begin detailed market research with customer insights analysis using {{current_year}} data and rigorous source verification.
+
+Remember: Init steps confirm understanding and scope, not generate research content!

src/modules/bmm/workflows/1-analysis/research/market-steps/step-02-customer-behavior.md

@@ -0,0 +1,235 @@
+# Market Research Step 2: Customer Behavior and Segments
+
+## 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 BEHAVIOR ANALYST, not content generator
+- 💬 FOCUS on customer behavior patterns and demographic analysis
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete research
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] continue option after customer behavior content generation
+- 📝 WRITE CUSTOMER BEHAVIOR ANALYSIS TO DOCUMENT IMMEDIATELY
+- 💾 ONLY proceed 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 patterns and demographic analysis
+- Web search capabilities with source verification are enabled
+- Previous step confirmed research scope and goals
+- **Research topic = "{{research_topic}}"** - established from initial discussion
+- **Research goals = "{{research_goals}}"** - established from initial discussion
+
+## YOUR TASK:
+
+Conduct customer behavior and segment analysis using current {{current_year}} web data with emphasis on patterns and demographics.
+
+## CUSTOMER BEHAVIOR ANALYSIS SEQUENCE:
+
+### 1. Begin Customer Behavior Analysis
+
+**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer behavior areas simultaneously and thoroughly.
+
+Start with customer behavior research approach:
+"Now I'll conduct **customer behavior analysis** for **{{research_topic}}** using current {{current_year}} web data to understand customer patterns.
+
+**Customer Behavior Focus:**
+
+- Customer behavior patterns and preferences
+- Demographic profiles and segmentation
+- Psychographic characteristics and values
+- Behavior drivers and influences
+- Customer interaction patterns and engagement
+
+**Let me search for current customer behavior insights.**"
+
+### 2. Parallel Customer Behavior Research Execution
+
+**Execute multiple web searches simultaneously:**
+
+`WebSearch: "{{research_topic}} customer behavior patterns {{current_year}}"`
+`WebSearch: "{{research_topic}} customer demographics {{current_year}}"`
+`WebSearch: "{{research_topic}} psychographic profiles {{current_year}}"`
+`WebSearch: "{{research_topic}} customer behavior drivers {{current_year}}"`
+
+**Analysis approach:**
+
+- Look for customer behavior studies and research reports
+- Search for demographic segmentation and analysis
+- Research psychographic profiling and value systems
+- Analyze behavior drivers and influencing factors
+- Study customer interaction and engagement patterns
+
+### 3. Analyze and Aggregate Results
+
+**Collect and analyze findings from all parallel searches:**
+
+"After executing comprehensive parallel web searches, let me analyze and aggregate customer behavior findings:
+
+**Research Coverage:**
+
+- Customer behavior patterns and preferences
+- Demographic profiles and segmentation
+- Psychographic characteristics and values
+- Behavior drivers and influences
+- Customer interaction patterns and engagement
+
+**Cross-Behavior Analysis:**
+[Identify patterns connecting demographics, psychographics, and behaviors]
+
+**Quality Assessment:**
+[Overall confidence levels and research gaps identified]"
+
+### 4. Generate Customer Behavior Content
+
+**WRITE IMMEDIATELY TO DOCUMENT**
+
+Prepare customer behavior analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Customer Behavior and Segments
+
+### Customer Behavior Patterns
+
+[Customer behavior patterns analysis with source citations]
+_Behavior Drivers: [Key motivations and patterns from web search]_
+_Interaction Preferences: [Customer engagement and interaction patterns]_
+_Decision Habits: [How customers typically make decisions]_
+_Source: [URL with {{current_year}} customer behavior data]_
+
+### Demographic Segmentation
+
+[Demographic analysis with source citations]
+_Age Demographics: [Age groups and preferences]_
+_Income Levels: [Income segments and purchasing behavior]_
+_Geographic Distribution: [Regional/city differences]_
+_Education Levels: [Education impact on behavior]_
+_Source: [URL with {{current_year}} demographic data]_
+
+### Psychographic Profiles
+
+[Psychographic analysis with source citations]
+_Values and Beliefs: [Core values driving customer behavior]_
+_Lifestyle Preferences: [Lifestyle choices and behaviors]_
+_Attitudes and Opinions: [Customer attitudes toward products/services]_
+_Personality Traits: [Personality influences on behavior]_
+_Source: [URL with {{current_year}} psychographic data]_
+
+### Customer Segment Profiles
+
+[Detailed customer segment profiles with source citations]
+_Segment 1: [Detailed profile including demographics, psychographics, behavior]_
+_Segment 2: [Detailed profile including demographics, psychographics, behavior]_
+_Segment 3: [Detailed profile including demographics, psychographics, behavior]_
+_Source: [URL with {{current_year}} segment data]_
+
+### Behavior Drivers and Influences
+
+[Behavior drivers analysis with source citations]
+_Emotional Drivers: [Emotional factors influencing behavior]_
+_Rational Drivers: [Logical decision factors]_
+_Social Influences: [Social and peer influences]_
+_Economic Influences: [Economic factors affecting behavior]_
+_Source: [URL with {{current_year}} behavior drivers data]_
+
+### Customer Interaction Patterns
+
+[Customer interaction analysis with source citations]
+_Research and Discovery: [How customers find and research options]_
+_Purchase Decision Process: [Steps in purchase decision making]_
+_Post-Purchase Behavior: [After-purchase engagement patterns]_
+_Loyalty and Retention: [Factors driving customer loyalty]_
+_Source: [URL with {{current_year}} interaction data]_
+```
+
+### 5. Present Analysis and Continue Option
+
+**Show analysis and present continue option:**
+
+"I've completed **customer behavior analysis** using current {{current_year}} data to understand customer patterns for {{research_topic}}.
+
+**Key Customer Behavior Findings:**
+
+- Customer behavior patterns clearly identified with drivers
+- Demographic segmentation thoroughly analyzed
+- Psychographic profiles mapped and documented
+- Customer interaction patterns captured
+- Multiple sources verified for critical insights
+
+**Ready to proceed to customer pain points?**
+[C] Continue - Save this to document and proceed to pain points analysis
+
+### 6. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- **CONTENT ALREADY WRITTEN TO DOCUMENT**
+- Update frontmatter: `stepsCompleted: [1, 2]`
+- Load: `./step-03-customer-pain-points.md`
+
+## APPEND TO DOCUMENT:
+
+Content is already written to document when generated in step 4. No additional append needed.
+
+## SUCCESS METRICS:
+
+✅ Customer behavior patterns identified with current {{current_year}} citations
+✅ Demographic segmentation thoroughly analyzed
+✅ Psychographic profiles clearly documented
+✅ Customer interaction patterns captured
+✅ Multiple sources verified for critical insights
+✅ Content written immediately to document
+✅ [C] continue option presented and handled correctly
+✅ Proper routing to next step (customer pain points)
+✅ Research goals alignment maintained
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in customer web searches
+❌ Missing critical customer behavior patterns
+❌ Incomplete demographic segmentation analysis
+❌ Missing psychographic profile documentation
+❌ Not writing content immediately to document
+❌ Not presenting [C] continue option after content generation
+❌ Not routing to customer pain points analysis step
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor research decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## CUSTOMER BEHAVIOR RESEARCH PROTOCOLS:
+
+- Research customer behavior studies and market research
+- Use demographic data from authoritative sources
+- Research psychographic profiling and value systems
+- Analyze customer interaction and engagement patterns
+- Focus on current {{current_year}} behavior data and trends
+- Present conflicting information when sources disagree
+- Apply confidence levels appropriately
+
+## BEHAVIOR ANALYSIS STANDARDS:
+
+- Always cite URLs for web search results
+- Use authoritative customer research sources
+- Note data currency and potential limitations
+- Present multiple perspectives when sources conflict
+- Apply confidence levels to uncertain data
+- Focus on actionable customer insights
+
+## NEXT STEP:
+
+After user selects 'C', load `./step-03-customer-pain-points.md` to analyze customer pain points, challenges, and unmet needs for {{research_topic}}.
+
+Remember: Always write research content to document immediately and emphasize current {{current_year}} customer data with rigorous source verification!

src/modules/bmm/workflows/1-analysis/research/market-steps/step-02-customer-insights.md

@@ -0,0 +1,198 @@
+# Market Research Step 2: Customer Insights
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ 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
+
+**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer areas simultaneously and thoroughly
+
+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 using parallel web searches for comprehensive coverage.**"
+
+### 2. Parallel Customer Research Execution
+
+**Execute multiple web searches simultaneously:**
+
+`WebSearch: "[product/service/market] customer behavior patterns {{current_year}}"`
+`WebSearch: "[product/service/market] customer pain points challenges {{current_year}}"`
+`WebSearch: "[product/service/market] customer decision process {{current_year}}"`
+
+**Analysis approach:**
+
+- Look for customer behavior studies and surveys
+- Search for customer experience and interaction patterns
+- Research customer satisfaction methodologies
+- Note generational and cultural customer variations
+- Research customer pain points and frustrations
+- Analyze decision-making processes and criteria
+
+### 3. Analyze and Aggregate Results
+
+**Collect and analyze findings from all parallel searches:**
+
+"After executing comprehensive parallel web searches, let me analyze and aggregate the customer insights:
+
+**Research Coverage:**
+
+- Customer behavior patterns and preferences
+- Pain points and challenges
+- Decision-making processes and journey mapping
+
+**Cross-Customer Analysis:**
+[Identify patterns connecting behavior, pain points, and decisions]
+
+**Quality Assessment:**
+[Overall confidence levels and research gaps identified]"
+
+### 4. 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]_
+```
+
+### 5. 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
+
+### 6. 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 4.
+
+## 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'
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## 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!

src/modules/bmm/workflows/1-analysis/research/market-steps/step-03-customer-pain-points.md

@@ -0,0 +1,247 @@
+# Market Research Step 3: Customer Pain Points and Needs
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ ALWAYS use {{current_year}} web searches for current customer data
+- 📋 YOU ARE A CUSTOMER NEEDS ANALYST, not content generator
+- 💬 FOCUS on customer pain points, challenges, and unmet needs
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] continue option after pain points content generation
+- 📝 WRITE CUSTOMER PAIN POINTS ANALYSIS TO DOCUMENT IMMEDIATELY
+- 💾 ONLY proceed 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
+- Customer behavior analysis completed in previous step
+- Focus on customer pain points, challenges, and unmet needs
+- Web search capabilities with source verification are enabled
+- **Research topic = "{{research_topic}}"** - established from initial discussion
+- **Research goals = "{{research_goals}}"** - established from initial discussion
+
+## YOUR TASK:
+
+Conduct customer pain points and needs analysis using current {{current_year}} web data with emphasis on challenges and frustrations.
+
+## CUSTOMER PAIN POINTS ANALYSIS SEQUENCE:
+
+### 1. Begin Customer Pain Points Analysis
+
+**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer pain point areas simultaneously and thoroughly.
+
+Start with customer pain points research approach:
+"Now I'll conduct **customer pain points analysis** for **{{research_topic}}** using current {{current_year}} web data to understand customer challenges.
+
+**Customer Pain Points Focus:**
+
+- Customer challenges and frustrations
+- Unmet needs and unaddressed problems
+- Barriers to adoption or usage
+- Service and support pain points
+- Customer satisfaction gaps
+
+**Let me search for current customer pain points insights.**"
+
+### 2. Parallel Pain Points Research Execution
+
+**Execute multiple web searches simultaneously:**
+
+`WebSearch: "{{research_topic}} customer pain points challenges {{current_year}}"`
+`WebSearch: "{{research_topic}} customer frustrations {{current_year}}"`
+`WebSearch: "{{research_topic}} unmet customer needs {{current_year}}"`
+`WebSearch: "{{research_topic}} customer barriers to adoption {{current_year}}"`
+
+**Analysis approach:**
+
+- Look for customer satisfaction surveys and reports
+- Search for customer complaints and reviews
+- Research customer support and service issues
+- Analyze barriers to customer adoption
+- Study unmet needs and market gaps
+
+### 3. Analyze and Aggregate Results
+
+**Collect and analyze findings from all parallel searches:**
+
+"After executing comprehensive parallel web searches, let me analyze and aggregate customer pain points findings:
+
+**Research Coverage:**
+
+- Customer challenges and frustrations
+- Unmet needs and unaddressed problems
+- Barriers to adoption or usage
+- Service and support pain points
+
+**Cross-Pain Points Analysis:**
+[Identify patterns connecting different types of pain points]
+
+**Quality Assessment:**
+[Overall confidence levels and research gaps identified]"
+
+### 4. Generate Customer Pain Points Content
+
+**WRITE IMMEDIATELY TO DOCUMENT**
+
+Prepare customer pain points analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Customer Pain Points and Needs
+
+### Customer Challenges and Frustrations
+
+[Customer challenges analysis with source citations]
+_Primary Frustrations: [Major customer frustrations identified]_
+_Usage Barriers: [Barriers preventing effective usage]_
+_Service Pain Points: [Customer service and support issues]_
+_Frequency Analysis: [How often these challenges occur]_
+_Source: [URL with {{current_year}} customer challenges data]_
+
+### Unmet Customer Needs
+
+[Unmet needs analysis with source citations]
+_Critical Unmet Needs: [Most important unaddressed needs]_
+_Solution Gaps: [Opportunities to address unmet needs]_
+_Market Gaps: [Market opportunities from unmet needs]_
+_Priority Analysis: [Which needs are most critical]_
+_Source: [URL with {{current_year}} unmet needs data]_
+
+### Barriers to Adoption
+
+[Adoption barriers analysis with source citations]
+_Price Barriers: [Cost-related barriers to adoption]_
+_Technical Barriers: [Complexity or technical barriers]_
+_Trust Barriers: [Trust and credibility issues]_
+_Convenience Barriers: [Ease of use or accessibility issues]_
+_Source: [URL with {{current_year}} adoption barriers data]_
+
+### Service and Support Pain Points
+
+[Service pain points analysis with source citations]
+_Customer Service Issues: [Common customer service problems]_
+_Support Gaps: [Areas where customer support is lacking]_
+_Communication Issues: [Communication breakdowns and frustrations]_
+_Response Time Issues: [Slow response and resolution problems]_
+_Source: [URL with {{current_year}} service pain points data]_
+
+### Customer Satisfaction Gaps
+
+[Satisfaction gap analysis with source citations]
+_Expectation Gaps: [Differences between expectations and reality]_
+_Quality Gaps: [Areas where quality expectations aren't met]_
+_Value Perception Gaps: [Perceived value vs actual value]_
+_Trust and Credibility Gaps: [Trust issues affecting satisfaction]_
+_Source: [URL with {{current_year}} satisfaction gap data]_
+
+### Emotional Impact Assessment
+
+[Emotional impact analysis with source citations]
+_Frustration Levels: [Customer frustration severity assessment]_
+_Loyalty Risks: [How pain points affect customer loyalty]_
+_Reputation Impact: [Impact on brand or product reputation]_
+_Customer Retention Risks: [Risk of customer loss from pain points]_
+_Source: [URL with {{current_year}} emotional impact data]_
+
+### Pain Point Prioritization
+
+[Pain point prioritization with source citations]
+_High Priority Pain Points: [Most critical pain points to address]_
+_Medium Priority Pain Points: [Important but less critical pain points]_
+_Low Priority Pain Points: [Minor pain points with lower impact]_
+_Opportunity Mapping: [Pain points with highest solution opportunity]_
+_Source: [URL with {{current_year}} prioritization data]_
+```
+
+### 5. Present Analysis and Continue Option
+
+**Show analysis and present continue option:**
+
+"I've completed **customer pain points analysis** using current {{current_year}} data to understand customer challenges for {{research_topic}}.
+
+**Key Pain Points Findings:**
+
+- Customer challenges and frustrations thoroughly documented
+- Unmet needs and solution gaps clearly identified
+- Adoption barriers and service pain points analyzed
+- Customer satisfaction gaps assessed
+- Pain points prioritized by impact and opportunity
+
+**Ready to proceed to customer decision processes?**
+[C] Continue - Save this to document and proceed to decision processes analysis
+
+### 6. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- **CONTENT ALREADY WRITTEN TO DOCUMENT**
+- Update frontmatter: `stepsCompleted: [1, 2, 3]`
+- Load: `./step-04-customer-decisions.md`
+
+## APPEND TO DOCUMENT:
+
+Content is already written to document when generated in step 4. No additional append needed.
+
+## SUCCESS METRICS:
+
+✅ Customer challenges and frustrations clearly documented
+✅ Unmet needs and solution gaps identified
+✅ Adoption barriers and service pain points analyzed
+✅ Customer satisfaction gaps assessed
+✅ Pain points prioritized by impact and opportunity
+✅ Content written immediately to document
+✅ [C] continue option presented and handled correctly
+✅ Proper routing to next step (customer decisions)
+✅ Research goals alignment maintained
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in customer web searches
+❌ Missing critical customer challenges or frustrations
+❌ Not identifying unmet needs or solution gaps
+❌ Incomplete adoption barriers analysis
+❌ Not writing content immediately to document
+❌ Not presenting [C] continue option after content generation
+❌ Not routing to customer decisions analysis step
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## CUSTOMER PAIN POINTS RESEARCH PROTOCOLS:
+
+- Research customer satisfaction surveys and reviews
+- Use customer feedback and complaint data
+- Analyze customer support and service issues
+- Study barriers to customer adoption
+- Focus on current {{current_year}} pain point data
+- Present conflicting information when sources disagree
+- Apply confidence levels appropriately
+
+## PAIN POINTS ANALYSIS STANDARDS:
+
+- Always cite URLs for web search results
+- Use authoritative customer research sources
+- Note data currency and potential limitations
+- Present multiple perspectives when sources conflict
+- Apply confidence levels to uncertain data
+- Focus on actionable pain point insights
+
+## NEXT STEP:
+
+After user selects 'C', load `./step-04-customer-decisions.md` to analyze customer decision processes, journey mapping, and decision factors for {{research_topic}}.
+
+Remember: Always write research content to document immediately and emphasize current {{current_year}} customer pain points data with rigorous source verification!

src/modules/bmm/workflows/1-analysis/research/market-steps/step-04-customer-decisions.md

@@ -0,0 +1,257 @@
+# Market Research Step 4: Customer Decisions and Journey
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ ALWAYS use {{current_year}} web searches for current customer data
+- 📋 YOU ARE A CUSTOMER DECISION ANALYST, not content generator
+- 💬 FOCUS on customer decision processes and journey mapping
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] continue option after decision processes content generation
+- 📝 WRITE CUSTOMER DECISIONS ANALYSIS TO DOCUMENT IMMEDIATELY
+- 💾 ONLY proceed 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
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- Customer behavior and pain points analysis completed in previous steps
+- Focus on customer decision processes and journey mapping
+- Web search capabilities with source verification are enabled
+- **Research topic = "{{research_topic}}"** - established from initial discussion
+- **Research goals = "{{research_goals}}"** - established from initial discussion
+
+## YOUR TASK:
+
+Conduct customer decision processes and journey analysis using current {{current_year}} web data with emphasis on decision factors and journey mapping.
+
+## CUSTOMER DECISIONS ANALYSIS SEQUENCE:
+
+### 1. Begin Customer Decisions Analysis
+
+**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer decision areas simultaneously and thoroughly.
+
+Start with customer decisions research approach:
+"Now I'll conduct **customer decision processes analysis** for **{{research_topic}}** using current {{current_year}} web data to understand customer decision-making.
+
+**Customer Decisions Focus:**
+
+- Customer decision-making processes
+- Decision factors and criteria
+- Customer journey mapping
+- Purchase decision influencers
+- Information gathering patterns
+
+**Let me search for current customer decision insights.**"
+
+### 2. Parallel Decisions Research Execution
+
+**Execute multiple web searches simultaneously:**
+
+`WebSearch: "{{research_topic}} customer decision process {{current_year}}"`
+`WebSearch: "{{research_topic}} buying criteria factors {{current_year}}"`
+`WebSearch: "{{research_topic}} customer journey mapping {{current_year}}"`
+`WebSearch: "{{research_topic}} decision influencing factors {{current_year}}"`
+
+**Analysis approach:**
+
+- Look for customer decision research studies
+- Search for buying criteria and factor analysis
+- Research customer journey mapping methodologies
+- Analyze decision influence factors and channels
+- Study information gathering and evaluation patterns
+
+### 3. Analyze and Aggregate Results
+
+**Collect and analyze findings from all parallel searches:**
+
+"After executing comprehensive parallel web searches, let me analyze and aggregate customer decision findings:
+
+**Research Coverage:**
+
+- Customer decision-making processes
+- Decision factors and criteria
+- Customer journey mapping
+- Decision influence factors
+
+**Cross-Decisions Analysis:**
+[Identify patterns connecting decision factors and journey stages]
+
+**Quality Assessment:**
+[Overall confidence levels and research gaps identified]"
+
+### 4. Generate Customer Decisions Content
+
+**WRITE IMMEDIATELY TO DOCUMENT**
+
+Prepare customer decisions analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Customer Decision Processes and Journey
+
+### Customer Decision-Making Processes
+
+[Decision processes analysis with source citations]
+_Decision Stages: [Key stages in customer decision making]_
+_Decision Timelines: [Timeframes for different decisions]_
+_Complexity Levels: [Decision complexity assessment]_
+_Evaluation Methods: [How customers evaluate options]_
+_Source: [URL with {{current_year}} decision process data]_
+
+### Decision Factors and Criteria
+
+[Decision factors analysis with source citations]
+_Primary Decision Factors: [Most important factors in decisions]_
+_Secondary Decision Factors: [Supporting factors influencing decisions]_
+_Weighing Analysis: [How different factors are weighed]_
+_Evoluton Patterns: [How factors change over time]_
+_Source: [URL with {{current_year}} decision factors data]_
+
+### Customer Journey Mapping
+
+[Journey mapping analysis with source citations]
+_Awareness Stage: [How customers become aware of {{research_topic}}]_
+_Consideration Stage: [Evaluation and comparison process]_
+_Decision Stage: [Final decision-making process]_
+_Purchase Stage: [Purchase execution and completion]_
+_Post-Purchase Stage: [Post-decision evaluation and behavior]_
+_Source: [URL with {{current_year}} journey mapping data]_
+
+### Touchpoint Analysis
+
+[Touchpoint analysis with source citations]
+_Digital Touchpoints: [Online and digital interaction points]_
+_Offline Touchpoints: [Physical and in-person interaction points]_
+_Information Sources: [Where customers get information]_
+_Influence Channels: [What influences customer decisions]_
+_Source: [URL with {{current_year}} touchpoint data]_
+
+### Information Gathering Patterns
+
+[Information patterns analysis with source citations]
+_Research Methods: [How customers research options]_
+_Information Sources Trusted: [Most trusted information sources]_
+_Research Duration: [Time spent gathering information]_
+_Evaluation Criteria: [How customers evaluate information]_
+_Source: [URL with {{current_year}} information gathering data]_
+
+### Decision Influencers
+
+[Decision influencer analysis with source citations]
+_Peer Influence: [How friends and family influence decisions]_
+_Expert Influence: [How expert opinions affect decisions]_
+_Media Influence: [How media and marketing affect decisions]_
+_Social Proof Influence: [How reviews and testimonials affect decisions]_
+_Source: [URL with {{current_year}} decision influencer data]_
+
+### Purchase Decision Factors
+
+[Purchase decision factors analysis with source citations]
+_Immediate Purchase Drivers: [Factors triggering immediate purchase]_
+_Delayed Purchase Drivers: [Factors causing purchase delays]_
+_Brand Loyalty Factors: [Factors driving repeat purchases]_
+_Price Sensitivity: [How price affects purchase decisions]_
+_Source: [URL with {{current_year}} purchase decision data]_
+
+### Customer Decision Optimizations
+
+[Decision optimization analysis with source citations]
+_Friction Reduction: [Ways to make decisions easier]_
+_Trust Building: [Building customer trust in decisions]_
+_Conversion Optimization: [Optimizing decision-to-purchase rates]_
+_Loyalty Building: [Building long-term customer relationships]_
+_Source: [URL with {{current_year}} decision optimization data]_
+```
+
+### 5. Present Analysis and Continue Option
+
+**Show analysis and present continue option:**
+
+"I've completed **customer decision processes analysis** using current {{current_year}} data to understand customer decision-making for {{research_topic}}.
+
+**Key Decision Findings:**
+
+- Customer decision-making processes clearly mapped
+- Decision factors and criteria thoroughly analyzed
+- Customer journey mapping completed across all stages
+- Decision influencers and touchpoints identified
+- Information gathering patterns documented
+
+**Ready to proceed to competitive analysis?**
+[C] Continue - Save this to document and proceed to competitive analysis
+
+### 6. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- **CONTENT ALREADY WRITTEN TO DOCUMENT**
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
+- Load: `./step-05-competitive-analysis.md`
+
+## APPEND TO DOCUMENT:
+
+Content is already written to document when generated in step 4. No additional append needed.
+
+## SUCCESS METRICS:
+
+✅ Customer decision-making processes clearly mapped
+✅ Decision factors and criteria thoroughly analyzed
+✅ Customer journey mapping completed across all stages
+✅ Decision influencers and touchpoints identified
+✅ Information gathering patterns documented
+✅ Content written immediately to document
+✅ [C] continue option presented and handled correctly
+✅ Proper routing to next step (competitive analysis)
+✅ Research goals alignment maintained
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in customer web searches
+❌ Missing critical decision-making process stages
+❌ Not identifying key decision factors
+❌ Incomplete customer journey mapping
+❌ Not writing content immediately to document
+❌ Not presenting [C] continue option after content generation
+❌ Not routing to competitive analysis step
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## CUSTOMER DECISIONS RESEARCH PROTOCOLS:
+
+- Research customer decision studies and psychology
+- Use customer journey mapping methodologies
+- Analyze buying criteria and decision factors
+- Study decision influence and touchpoint analysis
+- Focus on current {{current_year}} decision data
+- Present conflicting information when sources disagree
+- Apply confidence levels appropriately
+
+## DECISION ANALYSIS STANDARDS:
+
+- Always cite URLs for web search results
+- Use authoritative customer decision research sources
+- Note data currency and potential limitations
+- Present multiple perspectives when sources conflict
+- Apply confidence levels to uncertain data
+- Focus on actionable decision insights
+
+## NEXT STEP:
+
+After user selects 'C', load `./step-05-competitive-analysis.md` to analyze competitive landscape, market positioning, and competitive strategies for {{research_topic}}.
+
+Remember: Always write research content to document immediately and emphasize current {{current_year}} customer decision data with rigorous source verification!

src/modules/bmm/workflows/1-analysis/research/market-steps/step-05-competitive-analysis.md

@@ -0,0 +1,175 @@
+# Market Research Step 5: Competitive Analysis
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ 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, 4, 5]` 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'
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## 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! 🎉

src/modules/bmm/workflows/1-analysis/research/market-steps/step-06-research-completion.md

@@ -0,0 +1,475 @@
+# Market Research Step 6: Research Completion
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ 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, 5, 6]` before completing workflow
+- 🚫 FORBIDDEN to complete workflow until C is selected
+- 📚 GENERATE COMPLETE DOCUMENT STRUCTURE with intro, TOC, and summary
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- **Research topic = "{{research_topic}}"** - comprehensive market analysis
+- **Research goals = "{{research_goals}}"** - achieved through exhaustive market research
+- All market research sections have been completed (customer behavior, pain points, decisions, competitive analysis)
+- Web search capabilities with source verification are enabled
+- This is the final synthesis step producing the complete market research document
+
+## YOUR TASK:
+
+Produce a comprehensive, authoritative market research document on **{{research_topic}}** with compelling narrative introduction, detailed TOC, and executive summary based on exhaustive market research.
+
+## 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 Complete Market Research Document
+
+Prepare comprehensive market research document with full structure:
+
+#### Complete Document Structure:
+
+```markdown
+# [Compelling Title]: Comprehensive {{research_topic}} Market Research
+
+## Executive Summary
+
+[Brief compelling overview of key market findings and strategic implications]
+
+## Table of Contents
+
+- Market Research Introduction and Methodology
+- {{research_topic}} Market Analysis and Dynamics
+- Customer Insights and Behavior Analysis
+- Competitive Landscape and Positioning
+- Strategic Market Recommendations
+- Market Entry and Growth Strategies
+- Risk Assessment and Mitigation
+- Implementation Roadmap and Success Metrics
+- Future Market Outlook and Opportunities
+- Market Research Methodology and Source Documentation
+- Market Research Appendices and Additional Resources
+
+## 1. Market Research Introduction and Methodology
+
+### Market Research Significance
+
+[Compelling market narrative about why {{research_topic}} research is critical in {{current_year}}]
+_Market Importance: [Strategic market significance with {{current_year}} context]_
+_Business Impact: [Business implications of market research]_
+_Source: [URL with {{current_year}} market significance data]_
+
+### Market Research Methodology
+
+[Comprehensive description of market research approach including:]
+
+- **Market Scope**: [Comprehensive market coverage areas]
+- **Data Sources**: [Authoritative market sources and verification approach]
+- **Analysis Framework**: [Structured market analysis methodology]
+- **Time Period**: [{{current_year}} focus and market evolution context]
+- **Geographic Coverage**: [Regional/global market scope]
+
+### Market Research Goals and Objectives
+
+**Original Market Goals:** {{research_goals}}
+
+**Achieved Market Objectives:**
+
+- [Market Goal 1 achievement with supporting evidence]
+- [Market Goal 2 achievement with supporting evidence]
+- [Additional market insights discovered during research]
+
+## 2. {{research_topic}} Market Analysis and Dynamics
+
+### Market Size and Growth Projections
+
+[Comprehensive market analysis with {{current_year}} data]
+_Market Size: [Current market valuation and size]_
+_Growth Rate: [CAGR and market growth projections]_
+_Market Drivers: [Key factors driving market growth]_
+_Market Segments: [Detailed market segmentation analysis]_
+_Source: [URL with {{current_year}} market size data]_
+
+### Market Trends and Dynamics
+
+[Current market trends analysis]
+_Emerging Trends: [Key market trends and their implications]_
+_Market Dynamics: [Forces shaping market evolution]_
+_Consumer Behavior Shifts: [Changes in customer behavior and preferences]_
+_Source: [URL with {{current_year}} market trends data]_
+
+### Pricing and Business Model Analysis
+
+[Comprehensive pricing and business model analysis]
+_Pricing Strategies: [Current pricing approaches and models]_
+_Business Model Evolution: [Emerging and successful business models]_
+_Value Proposition Analysis: [Customer value proposition assessment]_
+_Source: [URL with {{current_year}} pricing data]_
+
+## 3. Customer Insights and Behavior Analysis
+
+### Customer Behavior Patterns
+
+[Customer insights analysis with {{current_year}} context]
+_Behavior Patterns: [Key customer behavior trends and patterns]_
+_Customer Journey: [Complete customer journey mapping]_
+_Decision Factors: [Factors influencing customer decisions]_
+_Source: [URL with {{current_year}} customer behavior data]_
+
+### Customer Pain Points and Needs
+
+[Comprehensive customer pain point analysis]
+_Pain Points: [Key customer challenges and frustrations]_
+_Unmet Needs: [Unsolved customer needs and opportunities]_
+_Customer Expectations: [Current customer expectations and requirements]_
+_Source: [URL with {{current_year}} customer insights data]_
+
+### Customer Segmentation and Targeting
+
+[Detailed customer segmentation analysis]
+_Customer Segments: [Detailed customer segment profiles]_
+_Target Market Analysis: [Most attractive customer segments]_
+_Segment-specific Strategies: [Tailored approaches for key segments]_
+_Source: [URL with {{current_year}} segmentation data]_
+
+## 4. Competitive Landscape and Positioning
+
+### Competitive Analysis
+
+[Comprehensive competitive analysis]
+_Market Leaders: [Dominant competitors and their strategies]_
+_Emerging Competitors: [New entrants and innovative approaches]_
+_Competitive Advantages: [Key differentiators and competitive advantages]_
+_Source: [URL with {{current_year}} competitive data]_
+
+### Market Positioning Strategies
+
+[Strategic positioning analysis]
+_Positioning Opportunities: [Opportunities for market differentiation]_
+_Competitive Gaps: [Unserved market needs and opportunities]_
+_Positioning Framework: [Recommended positioning approach]_
+_Source: [URL with {{current_year}} positioning data]_
+
+## 5. Strategic Market Recommendations
+
+### Market Opportunity Assessment
+
+[Strategic market opportunities analysis]
+_High-Value Opportunities: [Most attractive market opportunities]_
+_Market Entry Timing: [Optimal timing for market entry or expansion]_
+_Growth Strategies: [Recommended approaches for market growth]_
+_Source: [URL with {{current_year}} market opportunity data]_
+
+### Strategic Recommendations
+
+[Comprehensive strategic recommendations]
+_Market Entry Strategy: [Recommended approach for market entry/expansion]_
+_Competitive Strategy: [Recommended competitive positioning and approach]_
+_Customer Acquisition Strategy: [Recommended customer acquisition approach]_
+_Source: [URL with {{current_year}} strategic data]_
+
+## 6. Market Entry and Growth Strategies
+
+### Go-to-Market Strategy
+
+[Comprehensive go-to-market approach]
+_Market Entry Approach: [Recommended market entry strategy and tactics]_
+_Channel Strategy: [Optimal channels for market reach and customer acquisition]_
+_Partnership Strategy: [Strategic partnership and collaboration opportunities]_
+_Source: [URL with {{current_year}} market entry data]_
+
+### Growth and Scaling Strategy
+
+[Market growth and scaling analysis]
+_Growth Phases: [Recommended phased approach to market growth]_
+_Scaling Considerations: [Key factors for successful market scaling]_
+_Expansion Opportunities: [Opportunities for geographic or segment expansion]_
+_Source: [URL with {{current_year}} growth strategy data]_
+
+## 7. Risk Assessment and Mitigation
+
+### Market Risk Analysis
+
+[Comprehensive market risk assessment]
+_Market Risks: [Key market-related risks and uncertainties]_
+_Competitive Risks: [Competitive threats and mitigation strategies]_
+_Regulatory Risks: [Regulatory and compliance considerations]_
+_Source: [URL with {{current_year}} risk assessment data]_
+
+### Mitigation Strategies
+
+[Risk mitigation and contingency planning]
+_Risk Mitigation Approaches: [Strategies for managing identified risks]_
+_Contingency Planning: [Backup plans and alternative approaches]_
+_Market Sensitivity Analysis: [Impact of market changes on strategy]_
+_Source: [URL with {{current_year}} mitigation data]_
+
+## 8. Implementation Roadmap and Success Metrics
+
+### Implementation Framework
+
+[Comprehensive implementation guidance]
+_Implementation Timeline: [Recommended phased implementation approach]_
+_Required Resources: [Key resources and capabilities needed]_
+_Implementation Milestones: [Key milestones and success criteria]_
+_Source: [URL with {{current_year}} implementation data]_
+
+### Success Metrics and KPIs
+
+[Comprehensive success measurement framework]
+_Key Performance Indicators: [Critical metrics for measuring success]_
+_Monitoring and Reporting: [Approach for tracking and reporting progress]_
+_Success Criteria: [Clear criteria for determining success]_
+_Source: [URL with {{current_year}} metrics data]_
+
+## 9. Future Market Outlook and Opportunities
+
+### Future Market Trends
+
+[Forward-looking market analysis]
+_Near-term Market Evolution: [1-2 year market development expectations]_
+_Medium-term Market Trends: [3-5 year expected market developments]_
+_Long-term Market Vision: [5+ year market outlook for {{research_topic}}]_
+_Source: [URL with {{current_year}} future trends data]_
+
+### Strategic Opportunities
+
+[Market opportunity analysis and recommendations]
+_Emerging Opportunities: [New market opportunities and their potential]_
+_Innovation Opportunities: [Areas for market innovation and differentiation]_
+_Strategic Market Investments: [Recommended market investments and priorities]_
+_Source: [URL with {{current_year}} opportunity data]_
+
+## 10. Market Research Methodology and Source Verification
+
+### Comprehensive Market Source Documentation
+
+[Complete documentation of all market research sources]
+_Primary Market Sources: [Key authoritative market sources used]_
+_Secondary Market Sources: [Supporting market research and analysis]_
+_Market Web Search Queries: [Complete list of market search queries used]_
+_Market Data Currency: [All market data verified for {{current_year}} currency]_
+
+### Market Research Quality Assurance
+
+[Market research quality assurance and validation approach]
+_Market Source Verification: [All market claims verified with multiple sources]_
+_Market Confidence Levels: [Confidence assessments for uncertain market data]_
+_Market Research Limitations: [Market research limitations and areas for further investigation]_
+_Methodology Transparency: [Complete transparency about market research approach]_
+
+## 11. Market Research Appendices and Additional Resources
+
+### Detailed Market Data Tables
+
+[Comprehensive market data tables supporting research findings]
+_Market Size Data: [Detailed market size and growth data tables]_
+_Customer Analysis Data: [Detailed customer behavior and segmentation data]_
+_Competitive Analysis Data: [Detailed competitor comparison and positioning data]_
+
+### Market Resources and References
+
+[Valuable market resources for continued research and implementation]
+_Market Research Reports: [Authoritative market research reports and publications]_
+_Industry Associations: [Key industry organizations and market resources]_
+_Market Analysis Tools: [Tools and resources for ongoing market analysis]_
+
+---
+
+## Market Research Conclusion
+
+### Summary of Key Market Findings
+
+[Comprehensive summary of the most important market research findings]
+
+### Strategic Market Impact Assessment
+
+[Assessment of market implications for {{research_topic}}]
+
+### Next Steps Market Recommendations
+
+[Specific next steps for leveraging this market research]
+
+---
+
+**Market Research Completion Date:** {{date}}
+**Research Period:** {{current_year}} comprehensive market analysis
+**Document Length:** As needed for comprehensive market coverage
+**Source Verification:** All market facts cited with {{current_year}} sources
+**Market Confidence Level:** High - based on multiple authoritative market sources
+
+_This comprehensive market research document serves as an authoritative market reference on {{research_topic}} and provides strategic market insights for informed decision-making._
+```
+
+### 5. Present Complete Market Research Document and Final Option
+
+**Market Research Document Completion Presentation:**
+
+"I've completed the **comprehensive market research document synthesis** for **{{research_topic}}**, producing an authoritative market research document with:
+
+**Document Features:**
+
+- **Compelling Market Introduction**: Engaging opening that establishes market research significance
+- **Comprehensive Market TOC**: Complete navigation structure for market reference
+- **Exhaustive Market Research Coverage**: All market aspects of {{research_topic}} thoroughly analyzed
+- **Executive Market Summary**: Key market findings and strategic implications highlighted
+- **Strategic Market Recommendations**: Actionable market insights based on comprehensive research
+- **Complete Market Source Citations**: Every market claim verified with {{current_year}} sources
+
+**Market Research Completeness:**
+
+- Market analysis and dynamics fully documented
+- Customer insights and behavior analysis comprehensively covered
+- Competitive landscape and positioning detailed
+- Strategic market recommendations and implementation guidance provided
+
+**Document Standards Met:**
+
+- Exhaustive market research with no critical gaps
+- Professional market structure and compelling narrative
+- As long as needed for comprehensive market coverage
+- Multiple independent sources for all market claims
+- {{current_year}} market data throughout with proper citations
+
+**Ready to complete this comprehensive market research document?**
+[C] Complete Research - Save final comprehensive market research document
+
+### 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:
+
+✅ Compelling market introduction with research significance
+✅ Comprehensive market table of contents with complete document structure
+✅ Exhaustive market research coverage across all market aspects
+✅ Executive market summary with key findings and strategic implications
+✅ Strategic market recommendations grounded in comprehensive research
+✅ Complete market source verification with {{current_year}} citations
+✅ Professional market document structure and compelling narrative
+✅ [C] complete option presented and handled correctly
+✅ Market research workflow completed with comprehensive document
+
+## FAILURE MODES:
+
+❌ Not producing compelling market introduction
+❌ Missing comprehensive market table of contents
+❌ Incomplete market research coverage across market aspects
+❌ Not providing executive market summary with key findings
+❌ Missing strategic market recommendations based on research
+❌ Not using {{current_year}} market sources for all factual claims
+❌ Producing market document without professional structure
+❌ Not presenting completion option for final market document
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## 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
+
+## COMPREHENSIVE MARKET DOCUMENT STANDARDS:
+
+This step ensures the final market research document:
+
+- Serves as an authoritative market reference on {{research_topic}}
+- Provides strategic market insights for informed decision-making
+- Includes comprehensive market coverage with no gaps
+- Maintains rigorous market source verification standards
+- Delivers strategic market insights and actionable recommendations
+- Meets professional market research document quality standards
+
+## MARKET RESEARCH WORKFLOW COMPLETION:
+
+When 'C' is selected:
+
+- All market research steps completed (1-4)
+- Comprehensive market research document generated
+- Professional market document structure with intro, TOC, and summary
+- All market sections appended with source citations
+- Market research workflow status updated to complete
+- Final comprehensive market research document delivered to user
+
+## FINAL MARKET DELIVERABLE:
+
+Complete authoritative market research document on {{research_topic}} that:
+
+- Establishes professional market credibility through comprehensive research
+- Provides strategic market insights for informed decision-making
+- Serves as market reference document for continued use
+- Maintains highest market research quality standards with {{current_year}} verification
+
+## NEXT STEPS:
+
+Comprehensive market research workflow complete. User may:
+
+- Use market research document to inform business strategies and decisions
+- Conduct additional market research on specific segments or opportunities
+- Combine market research with other research types for comprehensive insights
+- Move forward with implementation based on strategic market recommendations
+
+Congratulations on completing comprehensive market research with professional documentation! 🎉

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]
+
+---
+
+<!-- Content will be appended sequentially through research workflow steps -->

src/modules/bmm/workflows/1-analysis/research/technical-steps/step-01-init.md

@@ -0,0 +1,136 @@
+# Technical Research Step 1: Technical Research Scope Confirmation
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user confirmation
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ FOCUS EXCLUSIVELY on confirming technical research scope and approach
+- 📋 YOU ARE A TECHNICAL RESEARCH PLANNER, not content generator
+- 💬 ACKNOWLEDGE and CONFIRM understanding of technical research goals
+- 🔍 This is SCOPE CONFIRMATION ONLY - no web research yet
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis before taking any action
+- ⚠️ Present [C] continue option after scope confirmation
+- 💾 ONLY proceed when user chooses C (Continue)
+- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
+- 🚫 FORBIDDEN to load next step until C is selected
+
+## CONTEXT BOUNDARIES:
+
+- Research type = "technical" is already set
+- **Research topic = "{{research_topic}}"** - discovered from initial discussion
+- **Research goals = "{{research_goals}}"** - captured from initial discussion
+- Focus on technical architecture and implementation research
+- Web search capabilities with {{current_year}} data are enabled
+
+## YOUR TASK:
+
+Confirm technical research scope and approach for **{{research_topic}}** with the user's goals in mind.
+
+## TECHNICAL SCOPE CONFIRMATION:
+
+### 1. Begin Scope Confirmation
+
+Start with technical scope understanding:
+"I understand you want to conduct **technical research** for **{{research_topic}}** with these goals: {{research_goals}}
+
+**Technical Research Scope:**
+
+- **Architecture Analysis**: System design patterns, frameworks, and architectural decisions
+- **Implementation Approaches**: Development methodologies, coding patterns, and best practices
+- **Technology Stack**: Languages, frameworks, tools, and platforms relevant to {{research_topic}}
+- **Integration Patterns**: APIs, communication protocols, and system interoperability
+- **Performance Considerations**: Scalability, optimization, and performance patterns
+
+**Research Approach:**
+
+- Current {{current_year}} web data with rigorous source verification
+- Multi-source validation for critical technical claims
+- Confidence levels for uncertain technical information
+- Comprehensive technical coverage with architecture-specific insights
+
+### 2. Scope Confirmation
+
+Present clear scope confirmation:
+"**Technical Research Scope Confirmation:**
+
+For **{{research_topic}}**, I will research:
+
+✅ **Architecture Analysis** - design patterns, frameworks, system architecture
+✅ **Implementation Approaches** - development methodologies, coding patterns
+✅ **Technology Stack** - languages, frameworks, tools, platforms
+✅ **Integration Patterns** - APIs, protocols, interoperability
+✅ **Performance Considerations** - scalability, optimization, patterns
+
+**All using current {{current_year}} web data with source verification.**
+
+**Does this technical research scope and approach align with your goals?**
+[C] Continue - Begin technical research with this scope
+
+### 3. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- Document scope confirmation in research file
+- Update frontmatter: `stepsCompleted: [1]`
+- Load: `./step-02-technology-stack.md`
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append scope confirmation:
+
+```markdown
+## Technical Research Scope Confirmation
+
+**Research Topic:** {{research_topic}}
+**Research Goals:** {{research_goals}}
+
+**Technical Research Scope:**
+
+- Architecture Analysis - design patterns, frameworks, system architecture
+- Implementation Approaches - development methodologies, coding patterns
+- Technology Stack - languages, frameworks, tools, platforms
+- Integration Patterns - APIs, protocols, interoperability
+- Performance Considerations - scalability, optimization, patterns
+
+**Research Methodology:**
+
+- Current {{current_year}} web data with rigorous source verification
+- Multi-source validation for critical technical claims
+- Confidence level framework for uncertain information
+- Comprehensive technical coverage with architecture-specific insights
+
+**Scope Confirmed:** {{date}}
+```
+
+## SUCCESS METRICS:
+
+✅ Technical research scope clearly confirmed with user
+✅ All technical analysis areas identified and explained
+✅ Research methodology with {{current_year}} data emphasized
+✅ [C] continue option presented and handled correctly
+✅ Scope confirmation documented when user proceeds
+✅ Proper routing to next technical research step
+
+## FAILURE MODES:
+
+❌ Not clearly confirming technical research scope with user
+❌ Missing critical technical analysis areas
+❌ Not emphasizing {{current_year}} web data requirement
+❌ Not presenting [C] continue option
+❌ Proceeding without user scope confirmation
+❌ Not routing to next technical research step
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## NEXT STEP:
+
+After user selects 'C', load `./step-02-technology-stack.md` to begin technology stack analysis with current {{current_year}} web data.
+
+Remember: This is SCOPE CONFIRMATION ONLY - no actual technical research yet, just confirming the research approach and scope!

src/modules/bmm/workflows/1-analysis/research/technical-steps/step-02-technical-overview.md

@@ -0,0 +1,237 @@
+# Technical Research Step 2: Technology Stack Analysis
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ ALWAYS use {{current_year}} web searches for current technology data
+- 📋 YOU ARE A TECHNOLOGY STACK ANALYST, not content generator
+- 💬 FOCUS on languages, frameworks, tools, and platforms
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] continue option after technology stack content generation
+- 📝 WRITE TECHNOLOGY STACK ANALYSIS TO DOCUMENT IMMEDIATELY
+- 💾 ONLY proceed 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 topic = "{{research_topic}}"** - established from initial discussion
+- **Research goals = "{{research_goals}}"** - established from initial discussion
+- Focus on languages, frameworks, tools, and platforms
+- Web search capabilities with source verification are enabled
+
+## YOUR TASK:
+
+Conduct technology stack analysis focusing on languages, frameworks, tools, and platforms using current {{current_year}} web data with rigorous source verification.
+
+## TECHNOLOGY STACK ANALYSIS SEQUENCE:
+
+### 1. Begin Technology Stack Analysis
+
+**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different technology stack areas simultaneously and thoroughly.
+
+Start with technology stack research approach:
+"Now I'll conduct **technology stack analysis** for **{{research_topic}}** using current {{current_year}} web data to understand the technology landscape.
+
+**Technology Stack Focus:**
+
+- Programming languages and their evolution
+- Development frameworks and libraries
+- Database and storage technologies
+- Development tools and platforms
+- Cloud infrastructure and deployment platforms
+
+**Let me search for current technology stack insights.**"
+
+### 2. Parallel Technology Stack Research Execution
+
+**Execute multiple web searches simultaneously:**
+
+`WebSearch: "{{research_topic}} programming languages frameworks {{current_year}}"`
+`WebSearch: "{{research_topic}} development tools platforms {{current_year}}"`
+`WebSearch: "{{research_topic}} database storage technologies {{current_year}}"`
+`WebSearch: "{{research_topic}} cloud infrastructure platforms {{current_year}}"`
+
+**Analysis approach:**
+
+- Look for recent technology trend reports and developer surveys
+- Search for technology documentation and best practices
+- Research open-source projects and their technology choices
+- Analyze technology adoption patterns and migration trends
+- Study platform and tool evolution in the domain
+
+### 3. Analyze and Aggregate Results
+
+**Collect and analyze findings from all parallel searches:**
+
+"After executing comprehensive parallel web searches, let me analyze and aggregate technology stack findings:
+
+**Research Coverage:**
+
+- Programming languages and frameworks analysis
+- Development tools and platforms evaluation
+- Database and storage technologies assessment
+- Cloud infrastructure and deployment platform analysis
+
+**Cross-Technology Analysis:**
+[Identify patterns connecting language choices, frameworks, and platform decisions]
+
+**Quality Assessment:**
+[Overall confidence levels and research gaps identified]"
+
+### 4. Generate Technology Stack Content
+
+**WRITE IMMEDIATELY TO DOCUMENT**
+
+Prepare technology stack analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Technology Stack Analysis
+
+### Programming Languages
+
+[Programming languages analysis with source citations]
+_Popular Languages: [Most widely used languages for {{research_topic}}]_
+_Emerging Languages: [Growing languages gaining adoption]_
+_Language Evolution: [How language preferences are changing]_
+_Performance Characteristics: [Language performance and suitability]_
+_Source: [URL with {{current_year}} language data]_
+
+### Development Frameworks and Libraries
+
+[Frameworks analysis with source citations]
+_Major Frameworks: [Dominant frameworks and their use cases]_
+_Micro-frameworks: [Lightweight options and specialized libraries]_
+_Evolution Trends: [How frameworks are evolving and changing]_
+_Ecosystem Maturity: [Library availability and community support]_
+_Source: [URL with {{current_year}} framework data]_
+
+### Database and Storage Technologies
+
+[Database analysis with source citations]
+_Relational Databases: [Traditional SQL databases and their evolution]_
+_NoSQL Databases: [Document, key-value, graph, and other NoSQL options]_
+_In-Memory Databases: [Redis, Memcached, and performance-focused solutions]_
+_Data Warehousing: [Analytics and big data storage solutions]_
+_Source: [URL with {{current_year}} database data]_
+
+### Development Tools and Platforms
+
+[Tools and platforms analysis with source citations]
+_IDE and Editors: [Development environments and their evolution]_
+_Version Control: [Git and related development tools]_
+_Build Systems: [Compilation, packaging, and automation tools]_
+_Testing Frameworks: [Unit testing, integration testing, and QA tools]_
+_Source: [URL with {{current_year}} tools data]_
+
+### Cloud Infrastructure and Deployment
+
+[Cloud platforms analysis with source citations]
+_Major Cloud Providers: [AWS, Azure, GCP and their services]_
+_Container Technologies: [Docker, Kubernetes, and orchestration]_
+_Serverless Platforms: [FaaS and event-driven computing]_
+_CDN and Edge Computing: [Content delivery and distributed computing]_
+_Source: [URL with {{current_year}} cloud data]_
+
+### Technology Adoption Trends
+
+[Adoption trends analysis with source citations]
+_Migration Patterns: [How technology choices are evolving]_
+_Emerging Technologies: [New technologies gaining traction]_
+_Legacy Technology: [Older technologies being phased out]_
+_Community Trends: [Developer preferences and open-source adoption]_
+_Source: [URL with {{current_year}} adoption data]_
+```
+
+### 5. Present Analysis and Continue Option
+
+**Show analysis and present continue option:**
+
+"I've completed **technology stack analysis** using current {{current_year}} data to understand the technology landscape for {{research_topic}}.
+
+**Key Technology Stack Findings:**
+
+- Programming languages and frameworks thoroughly analyzed
+- Database and storage technologies evaluated
+- Development tools and platforms documented
+- Cloud infrastructure and deployment options mapped
+- Technology adoption trends identified
+
+**Ready to proceed to integration patterns analysis?**
+[C] Continue - Save this to document and proceed to integration patterns
+
+### 6. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- **CONTENT ALREADY WRITTEN TO DOCUMENT**
+- Update frontmatter: `stepsCompleted: [1, 2]`
+- Load: `./step-03-integration-patterns.md`
+
+## APPEND TO DOCUMENT:
+
+Content is already written to document when generated in step 4. No additional append needed.
+
+## SUCCESS METRICS:
+
+✅ Programming languages and frameworks thoroughly analyzed
+✅ Database and storage technologies evaluated
+✅ Development tools and platforms documented
+✅ Cloud infrastructure and deployment options mapped
+✅ Technology adoption trends identified
+✅ Content written immediately to document
+✅ [C] continue option presented and handled correctly
+✅ Proper routing to next step (integration patterns)
+✅ Research goals alignment maintained
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in technology web searches
+❌ Missing critical programming languages or frameworks
+❌ Incomplete database and storage technology analysis
+❌ Not identifying development tools and platforms
+❌ Not writing content immediately to document
+❌ Not presenting [C] continue option after content generation
+❌ Not routing to integration patterns step
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## TECHNOLOGY STACK RESEARCH PROTOCOLS:
+
+- Research technology trend reports and developer surveys
+- Use technology documentation and best practices guides
+- Analyze open-source projects and their technology choices
+- Study technology adoption patterns and migration trends
+- Focus on current {{current_year}} technology data
+- Present conflicting information when sources disagree
+- Apply confidence levels appropriately
+
+## TECHNOLOGY STACK ANALYSIS STANDARDS:
+
+- Always cite URLs for web search results
+- Use authoritative technology research sources
+- Note data currency and potential limitations
+- Present multiple perspectives when sources conflict
+- Apply confidence levels to uncertain data
+- Focus on actionable technology insights
+
+## NEXT STEP:
+
+After user selects 'C', load `./step-03-integration-patterns.md` to analyze APIs, communication protocols, and system interoperability for {{research_topic}}.
+
+Remember: Always write research content to document immediately and emphasize current {{current_year}} technology data with rigorous source verification!

src/modules/bmm/workflows/1-analysis/research/technical-steps/step-03-integration-patterns.md

@@ -0,0 +1,246 @@
+# Technical Research Step 3: Integration Patterns
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ ALWAYS use {{current_year}} web searches for current integration data
+- 📋 YOU ARE AN INTEGRATION ANALYST, not content generator
+- 💬 FOCUS on APIs, protocols, and system interoperability
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] continue option after integration patterns content generation
+- 📝 WRITE INTEGRATION PATTERNS ANALYSIS TO DOCUMENT IMMEDIATELY
+- 💾 ONLY proceed 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
+- **Research topic = "{{research_topic}}"** - established from initial discussion
+- **Research goals = "{{research_goals}}"** - established from initial discussion
+- Focus on APIs, protocols, and system interoperability
+- Web search capabilities with source verification are enabled
+
+## YOUR TASK:
+
+Conduct integration patterns analysis focusing on APIs, communication protocols, and system interoperability using current {{current_year}} web data with rigorous source verification.
+
+## INTEGRATION PATTERNS ANALYSIS SEQUENCE:
+
+### 1. Begin Integration Patterns Analysis
+
+**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different integration areas simultaneously and thoroughly.
+
+Start with integration patterns research approach:
+"Now I'll conduct **integration patterns analysis** for **{{research_topic}}** using current {{current_year}} web data to understand system integration approaches.
+
+**Integration Patterns Focus:**
+
+- API design patterns and protocols
+- Communication protocols and data formats
+- System interoperability approaches
+- Microservices integration patterns
+- Event-driven architectures and messaging
+
+**Let me search for current integration patterns insights.**"
+
+### 2. Parallel Integration Patterns Research Execution
+
+**Execute multiple web searches simultaneously:**
+
+`WebSearch: "{{research_topic}} API design patterns protocols {{current_year}}"`
+`WebSearch: "{{research_topic}} communication protocols data formats {{current_year}}"`
+`WebSearch: "{{research_topic}} system interoperability integration {{current_year}}"`
+`WebSearch: "{{research_topic}} microservices integration patterns {{current_year}}"`
+
+**Analysis approach:**
+
+- Look for recent API design guides and best practices
+- Search for communication protocol documentation and standards
+- Research integration platform and middleware solutions
+- Analyze microservices architecture patterns and approaches
+- Study event-driven systems and messaging patterns
+
+### 3. Analyze and Aggregate Results
+
+**Collect and analyze findings from all parallel searches:**
+
+"After executing comprehensive parallel web searches, let me analyze and aggregate integration patterns findings:
+
+**Research Coverage:**
+
+- API design patterns and protocols analysis
+- Communication protocols and data formats evaluation
+- System interoperability approaches assessment
+- Microservices integration patterns documentation
+
+**Cross-Integration Analysis:**
+[Identify patterns connecting API choices, communication protocols, and system design]
+
+**Quality Assessment:**
+[Overall confidence levels and research gaps identified]"
+
+### 4. Generate Integration Patterns Content
+
+**WRITE IMMEDIATELY TO DOCUMENT**
+
+Prepare integration patterns analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Integration Patterns Analysis
+
+### API Design Patterns
+
+[API design patterns analysis with source citations]
+_RESTful APIs: [REST principles and best practices for {{research_topic}}]_
+_GraphQL APIs: [GraphQL adoption and implementation patterns]_
+_RPC and gRPC: [High-performance API communication patterns]_
+_Webhook Patterns: [Event-driven API integration approaches]_
+_Source: [URL with {{current_year}} API design data]_
+
+### Communication Protocols
+
+[Communication protocols analysis with source citations]
+_HTTP/HTTPS Protocols: [Web-based communication patterns and evolution]_
+_WebSocket Protocols: [Real-time communication and persistent connections]_
+_Message Queue Protocols: [AMQP, MQTT, and messaging patterns]_
+_grpc and Protocol Buffers: [High-performance binary communication protocols]_
+_Source: [URL with {{current_year}} communication protocols data]_
+
+### Data Formats and Standards
+
+[Data formats analysis with source citations]
+_JSON and XML: [Structured data exchange formats and their evolution]_
+_Protobuf and MessagePack: [Efficient binary serialization formats]_
+_CSV and Flat Files: [Legacy data integration and bulk transfer patterns]_
+_Custom Data Formats: [Domain-specific data exchange standards]_
+_Source: [URL with {{current_year}} data formats data]_
+
+### System Interoperability Approaches
+
+[Interoperability analysis with source citations]
+_Point-to-Point Integration: [Direct system-to-system communication patterns]_
+_API Gateway Patterns: [Centralized API management and routing]_
+_Service Mesh: [Service-to-service communication and observability]_
+_Enterprise Service Bus: [Traditional enterprise integration patterns]_
+_Source: [URL with {{current_year}} interoperability data]_
+
+### Microservices Integration Patterns
+
+[Microservices integration analysis with source citations]
+_API Gateway Pattern: [External API management and routing]_
+_Service Discovery: [Dynamic service registration and discovery]_
+_Circuit Breaker Pattern: [Fault tolerance and resilience patterns]_
+_Saga Pattern: [Distributed transaction management]_
+_Source: [URL with {{current_year}} microservices data]_
+
+### Event-Driven Integration
+
+[Event-driven analysis with source citations]
+_Publish-Subscribe Patterns: [Event broadcasting and subscription models]_
+_Event Sourcing: [Event-based state management and persistence]_
+_Message Broker Patterns: [RabbitMQ, Kafka, and message routing]_
+_CQRS Patterns: [Command Query Responsibility Segregation]_
+_Source: [URL with {{current_year}} event-driven data]_
+
+### Integration Security Patterns
+
+[Security patterns analysis with source citations]
+_OAuth 2.0 and JWT: [API authentication and authorization patterns]_
+_API Key Management: [Secure API access and key rotation]_
+_Mutual TLS: [Certificate-based service authentication]_
+_Data Encryption: [Secure data transmission and storage]_
+_Source: [URL with {{current_year}} integration security data]_
+```
+
+### 5. Present Analysis and Continue Option
+
+**Show analysis and present continue option:**
+
+"I've completed **integration patterns analysis** using current {{current_year}} data to understand system integration approaches for {{research_topic}}.
+
+**Key Integration Patterns Findings:**
+
+- API design patterns and protocols thoroughly analyzed
+- Communication protocols and data formats evaluated
+- System interoperability approaches documented
+- Microservices integration patterns mapped
+- Event-driven integration strategies identified
+
+**Ready to proceed to architectural patterns analysis?**
+[C] Continue - Save this to document and proceed to architectural patterns
+
+### 6. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- **CONTENT ALREADY WRITTEN TO DOCUMENT**
+- Update frontmatter: `stepsCompleted: [1, 2, 3]`
+- Load: `./step-04-architectural-patterns.md`
+
+## APPEND TO DOCUMENT:
+
+Content is already written to document when generated in step 4. No additional append needed.
+
+## SUCCESS METRICS:
+
+✅ API design patterns and protocols thoroughly analyzed
+✅ Communication protocols and data formats evaluated
+✅ System interoperability approaches documented
+✅ Microservices integration patterns mapped
+✅ Event-driven integration strategies identified
+✅ Content written immediately to document
+✅ [C] continue option presented and handled correctly
+✅ Proper routing to next step (architectural patterns)
+✅ Research goals alignment maintained
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in integration web searches
+❌ Missing critical API design patterns or protocols
+❌ Incomplete communication protocols analysis
+❌ Not identifying system interoperability approaches
+❌ Not writing content immediately to document
+❌ Not presenting [C] continue option after content generation
+❌ Not routing to architectural patterns step
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## INTEGRATION PATTERNS RESEARCH PROTOCOLS:
+
+- Research API design guides and best practices documentation
+- Use communication protocol specifications and standards
+- Analyze integration platform and middleware solutions
+- Study microservices architecture patterns and case studies
+- Focus on current {{current_year}} integration data
+- Present conflicting information when sources disagree
+- Apply confidence levels appropriately
+
+## INTEGRATION PATTERNS ANALYSIS STANDARDS:
+
+- Always cite URLs for web search results
+- Use authoritative integration research sources
+- Note data currency and potential limitations
+- Present multiple perspectives when sources conflict
+- Apply confidence levels to uncertain data
+- Focus on actionable integration insights
+
+## NEXT STEP:
+
+After user selects 'C', load `./step-04-architectural-patterns.md` to analyze architectural patterns, design decisions, and system structures for {{research_topic}}.
+
+Remember: Always write research content to document immediately and emphasize current {{current_year}} integration data with rigorous source verification!

src/modules/bmm/workflows/1-analysis/research/technical-steps/step-04-architectural-patterns.md

@@ -0,0 +1,200 @@
+# Technical Research Step 4: Architectural Patterns
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ 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
+- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] continue option after architectural patterns content generation
+- 📝 WRITE ARCHITECTURAL PATTERNS ANALYSIS TO DOCUMENT IMMEDIATELY
+- 💾 ONLY proceed 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
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- **Research topic = "{{research_topic}}"** - established from initial discussion
+- **Research goals = "{{research_goals}}"** - established from initial discussion
+- Focus on architectural patterns and design decisions
+- Web search capabilities with source verification are enabled
+
+## YOUR TASK:
+
+Conduct comprehensive architectural patterns analysis using current {{current_year}} web data with emphasis on design decisions and implementation approaches for {{research_topic}}.
+
+## 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'
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## 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!

src/modules/bmm/workflows/1-analysis/research/technical-steps/step-05-implementation-research.md

@@ -0,0 +1,237 @@
+# Technical Research Step 4: Implementation Research
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ 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'
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## 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! 🎉

src/modules/bmm/workflows/1-analysis/research/technical-steps/step-06-research-synthesis.md

@@ -0,0 +1,486 @@
+# Technical Research Step 5: Technical Synthesis and Completion
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ ALWAYS use {{current_year}} web searches for current technical data
+- 📋 YOU ARE A TECHNICAL RESEARCH STRATEGIST, not content generator
+- 💬 FOCUS on comprehensive technical synthesis and authoritative conclusions
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+- 📄 PRODUCE COMPREHENSIVE DOCUMENT with narrative intro, TOC, and summary
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] complete option after synthesis content generation
+- 💾 ONLY save when user chooses C (Complete)
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before completing workflow
+- 🚫 FORBIDDEN to complete workflow until C is selected
+- 📚 GENERATE COMPLETE DOCUMENT STRUCTURE with intro, TOC, and summary
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- **Research topic = "{{research_topic}}"** - comprehensive technical analysis
+- **Research goals = "{{research_goals}}"** - achieved through exhaustive technical research
+- All technical research sections have been completed (overview, architecture, implementation)
+- Web search capabilities with source verification are enabled
+- This is the final synthesis step producing the complete technical research document
+
+## YOUR TASK:
+
+Produce a comprehensive, authoritative technical research document on **{{research_topic}}** with compelling narrative introduction, detailed TOC, and executive summary based on exhaustive technical research.
+
+## COMPREHENSIVE TECHNICAL DOCUMENT SYNTHESIS:
+
+### 1. Technical Document Structure Planning
+
+**Complete Technical Research Document Structure:**
+
+```markdown
+# [Compelling Technical Title]: Comprehensive {{research_topic}} Technical Research
+
+## Executive Summary
+
+[Brief compelling overview of key technical findings and strategic implications]
+
+## Table of Contents
+
+- Technical Research Introduction and Methodology
+- Technical Landscape and Architecture Analysis
+- Implementation Approaches and Best Practices
+- Technology Stack Evolution and Trends
+- Integration and Interoperability Patterns
+- Performance and Scalability Analysis
+- Security and Compliance Considerations
+- Strategic Technical Recommendations
+- Implementation Roadmap and Risk Assessment
+- Future Technical Outlook and Innovation Opportunities
+- Technical Research Methodology and Source Documentation
+- Technical Appendices and Reference Materials
+```
+
+### 2. Generate Compelling Technical Introduction
+
+**Technical Introduction Requirements:**
+
+- Hook reader with compelling technical opening about {{research_topic}}
+- Establish technical research significance and current relevance
+- Outline comprehensive technical research methodology
+- Preview key technical findings and strategic implications
+- Set authoritative, technical expert tone
+
+**Web Search for Technical Introduction Context:**
+`WebSearch: "{{research_topic}} technical significance importance {{current_year}}"`
+
+### 3. Synthesize All Technical Research Sections
+
+**Technical Section-by-Section Integration:**
+
+- Combine technical overview from step-02
+- Integrate architectural patterns from step-03
+- Incorporate implementation research from step-04
+- Add cross-technical insights and connections
+- Ensure comprehensive technical coverage with no gaps
+
+### 4. Generate Complete Technical Document Content
+
+#### Final Technical Document Structure:
+
+```markdown
+# [Compelling Title]: Comprehensive {{research_topic}} Technical Research
+
+## Executive Summary
+
+[2-3 paragraph compelling summary of the most critical technical findings and strategic implications for {{research_topic}} based on comprehensive {{current_year}} technical research]
+
+**Key Technical Findings:**
+
+- [Most significant architectural insights]
+- [Critical implementation considerations]
+- [Important technology trends]
+- [Strategic technical implications]
+
+**Technical Recommendations:**
+
+- [Top 3-5 actionable technical recommendations based on research]
+
+## Table of Contents
+
+1. Technical Research Introduction and Methodology
+2. {{research_topic}} Technical Landscape and Architecture Analysis
+3. Implementation Approaches and Best Practices
+4. Technology Stack Evolution and Current Trends
+5. Integration and Interoperability Patterns
+6. Performance and Scalability Analysis
+7. Security and Compliance Considerations
+8. Strategic Technical Recommendations
+9. Implementation Roadmap and Risk Assessment
+10. Future Technical Outlook and Innovation Opportunities
+11. Technical Research Methodology and Source Verification
+12. Technical Appendices and Reference Materials
+
+## 1. Technical Research Introduction and Methodology
+
+### Technical Research Significance
+
+[Compelling technical narrative about why {{research_topic}} research is critical in {{current_year}}]
+_Technical Importance: [Strategic technical significance with {{current_year}} context]_
+_Business Impact: [Business implications of technical research]_
+_Source: [URL with {{current_year}} technical significance data]_
+
+### Technical Research Methodology
+
+[Comprehensive description of technical research approach including:]
+
+- **Technical Scope**: [Comprehensive technical coverage areas]
+- **Data Sources**: [Authoritative technical sources and verification approach]
+- **Analysis Framework**: [Structured technical analysis methodology]
+- **Time Period**: [{{current_year}} focus and technical evolution context]
+- **Technical Depth**: [Level of technical detail and analysis]
+
+### Technical Research Goals and Objectives
+
+**Original Technical Goals:** {{research_goals}}
+
+**Achieved Technical Objectives:**
+
+- [Technical Goal 1 achievement with supporting evidence]
+- [Technical Goal 2 achievement with supporting evidence]
+- [Additional technical insights discovered during research]
+
+## 2. {{research_topic}} Technical Landscape and Architecture Analysis
+
+### Current Technical Architecture Patterns
+
+[Comprehensive architectural analysis synthesized from step-03 with {{current_year}} context]
+_Dominant Patterns: [Current architectural approaches]_
+_Architectural Evolution: [Historical and current evolution patterns]_
+_Architectural Trade-offs: [Key architectural decisions and implications]_
+_Source: [URL with {{current_year}} architectural data]_
+
+### System Design Principles and Best Practices
+
+[Complete system design analysis]
+_Design Principles: [Core principles guiding {{research_topic}} implementations]_
+_Best Practice Patterns: [Industry-standard approaches and methodologies]_
+_Architectural Quality Attributes: [Performance, scalability, maintainability considerations]_
+_Source: [URL with {{current_year}} design principles data]_
+
+## 3. Implementation Approaches and Best Practices
+
+### Current Implementation Methodologies
+
+[Implementation analysis from step-04 with {{current_year}} context]
+_Development Approaches: [Current development methodologies and approaches]_
+_Code Organization Patterns: [Structural patterns and organization strategies]_
+_Quality Assurance Practices: [Testing, validation, and quality approaches]_
+_Deployment Strategies: [Current deployment and operations practices]_
+_Source: [URL with {{current_year}} implementation data]_
+
+### Implementation Framework and Tooling
+
+[Comprehensive implementation framework analysis]
+_Development Frameworks: [Popular frameworks and their characteristics]_
+_Tool Ecosystem: [Development tools and platform considerations]_
+_Build and Deployment Systems: [CI/CD and automation approaches]_
+_Source: [URL with {{current_year}} framework data]_
+
+## 4. Technology Stack Evolution and Current Trends
+
+### Current Technology Stack Landscape
+
+[Technology stack analysis from step-02 with {{current_year}} updates]
+_Programming Languages: [Current language trends and adoption patterns]_
+_Frameworks and Libraries: [Popular frameworks and their use cases]_
+_Database and Storage Technologies: [Current data storage and management trends]_
+_API and Communication Technologies: [Integration and communication patterns]_
+_Source: [URL with {{current_year}} technology stack data]_
+
+### Technology Adoption Patterns
+
+[Comprehensive technology adoption analysis]
+_Adoption Trends: [Technology adoption rates and patterns]_
+_Migration Patterns: [Technology migration and evolution trends]_
+_Emerging Technologies: [New technologies and their potential impact]_
+_Source: [URL with {{current_year}} adoption data]_
+
+## 5. Integration and Interoperability Patterns
+
+### Current Integration Approaches
+
+[Integration patterns analysis with {{current_year}} context]
+_API Design Patterns: [Current API design and implementation patterns]_
+_Service Integration: [Microservices and service integration approaches]_
+_Data Integration: [Data exchange and integration patterns]_
+_Source: [URL with {{current_year}} integration data]_
+
+### Interoperability Standards and Protocols
+
+[Comprehensive interoperability analysis]
+_Standards Compliance: [Industry standards and compliance requirements]_
+_Protocol Selection: [Communication protocols and selection criteria]_
+_Integration Challenges: [Common integration challenges and solutions]_
+_Source: [URL with {{current_year}} interoperability data]_
+
+## 6. Performance and Scalability Analysis
+
+### Performance Characteristics and Optimization
+
+[Performance analysis based on research findings]
+_Performance Benchmarks: [Current performance characteristics and benchmarks]_
+_Optimization Strategies: [Performance optimization approaches and techniques]_
+_Monitoring and Measurement: [Performance monitoring and measurement practices]_
+_Source: [URL with {{current_year}} performance data]_
+
+### Scalability Patterns and Approaches
+
+[Comprehensive scalability analysis]
+_Scalability Patterns: [Architectural and design patterns for scalability]_
+_Capacity Planning: [Capacity planning and resource management approaches]_
+_Elasticity and Auto-scaling: [Dynamic scaling approaches and implementations]_
+_Source: [URL with {{current_year}} scalability data]_
+
+## 7. Security and Compliance Considerations
+
+### Security Best Practices and Frameworks
+
+[Security analysis with {{current_year}} context]
+_Security Frameworks: [Current security frameworks and best practices]_
+_Threat Landscape: [Current security threats and mitigation approaches]_
+_Secure Development Practices: [Secure coding and development lifecycle]_
+_Source: [URL with {{current_year}} security data]_
+
+### Compliance and Regulatory Considerations
+
+[Comprehensive compliance analysis]
+_Industry Standards: [Relevant industry standards and compliance requirements]_
+_Regulatory Compliance: [Legal and regulatory considerations for {{research_topic}}]_
+_Audit and Governance: [Technical audit and governance practices]_
+_Source: [URL with {{current_year}} compliance data]_
+
+## 8. Strategic Technical Recommendations
+
+### Technical Strategy and Decision Framework
+
+[Strategic technical recommendations based on comprehensive research]
+_Architecture Recommendations: [Recommended architectural approaches and patterns]_
+_Technology Selection: [Recommended technology stack and selection criteria]_
+_Implementation Strategy: [Recommended implementation approaches and methodologies]_
+_Source: [URL with {{current_year}} technical strategy data]_
+
+### Competitive Technical Advantage
+
+[Analysis of technical competitive positioning]
+_Technology Differentiation: [Technical approaches that provide competitive advantage]_
+_Innovation Opportunities: [Areas for technical innovation and differentiation]_
+_Strategic Technology Investments: [Recommended technology investments and priorities]_
+_Source: [URL with {{current_year}} competitive analysis data]_
+
+## 9. Implementation Roadmap and Risk Assessment
+
+### Technical Implementation Framework
+
+[Comprehensive implementation guidance based on research findings]
+_Implementation Phases: [Recommended phased implementation approach]_
+_Technology Migration Strategy: [Approach for technology adoption and migration]_
+_Resource Planning: [Technical resources and capabilities planning]_
+_Source: [URL with {{current_year}} implementation planning data]_
+
+### Technical Risk Management
+
+[Comprehensive technical risk assessment]
+_Technical Risks: [Major technical risks and mitigation strategies]_
+_Implementation Risks: [Risks associated with implementation and deployment]_
+_Business Impact Risks: [Technical risks and their business implications]_
+_Source: [URL with {{current_year}} technical risk data]_
+
+## 10. Future Technical Outlook and Innovation Opportunities
+
+### Emerging Technology Trends
+
+[Forward-looking technical analysis based on comprehensive research]
+_Near-term Technical Evolution: [1-2 year technical development expectations]_
+_Medium-term Technology Trends: [3-5 year expected technical developments]_
+_Long-term Technical Vision: [5+ year technical outlook for {{research_topic}}]_
+_Source: [URL with {{current_year}} future trends data]_
+
+### Innovation and Research Opportunities
+
+[Technical innovation analysis and recommendations]
+_Research Opportunities: [Areas for technical research and innovation]_
+_Emerging Technology Adoption: [Potential new technologies and adoption timelines]_
+_Innovation Framework: [Approach for fostering technical innovation]_
+_Source: [URL with {{current_year}} innovation data]_
+
+## 11. Technical Research Methodology and Source Verification
+
+### Comprehensive Technical Source Documentation
+
+[Complete documentation of all technical research sources]
+_Primary Technical Sources: [Key authoritative technical sources used]_
+_Secondary Technical Sources: [Supporting technical research and analysis]_
+_Technical Web Search Queries: [Complete list of technical search queries used]_
+_Technical Data Currency: [All technical data verified for {{current_year}} currency]_
+
+### Technical Research Quality Assurance
+
+[Technical quality assurance and validation approach]
+_Technical Source Verification: [All technical claims verified with multiple sources]_
+_Technical Confidence Levels: [Confidence assessments for uncertain technical data]_
+_Technical Limitations: [Technical research limitations and areas for further investigation]_
+_Methodology Transparency: [Complete transparency about technical research approach]_
+
+## 12. Technical Appendices and Reference Materials
+
+### Detailed Technical Data Tables
+
+[Comprehensive technical data tables supporting research findings]
+_Architectural Pattern Tables: [Detailed architectural pattern comparisons]_
+_Technology Stack Analysis: [Detailed technology evaluation and comparison data]_
+_Performance Benchmark Data: [Comprehensive performance measurement data]_
+
+### Technical Resources and References
+
+[Valuable technical resources for continued research and implementation]
+_Technical Standards: [Relevant technical standards and specifications]_
+_Open Source Projects: [Key open source projects and communities]_
+_Research Papers and Publications: [Academic and industry research sources]_
+_Technical Communities: [Professional networks and technical communities]_
+
+---
+
+## Technical Research Conclusion
+
+### Summary of Key Technical Findings
+
+[Comprehensive summary of the most important technical research findings]
+
+### Strategic Technical Impact Assessment
+
+[Assessment of technical implications for {{research_topic}}]
+
+### Next Steps Technical Recommendations
+
+[Specific next steps for leveraging this technical research]
+
+---
+
+**Technical Research Completion Date:** {{date}}
+**Research Period:** {{current_year}} comprehensive technical analysis
+**Document Length:** As needed for comprehensive technical coverage
+**Source Verification:** All technical facts cited with {{current_year}} sources
+**Technical Confidence Level:** High - based on multiple authoritative technical sources
+
+_This comprehensive technical research document serves as an authoritative technical reference on {{research_topic}} and provides strategic technical insights for informed decision-making and implementation._
+```
+
+### 5. Present Complete Technical Document and Final Option
+
+**Technical Document Completion Presentation:**
+
+"I've completed the **comprehensive technical research document synthesis** for **{{research_topic}}**, producing an authoritative technical research document with:
+
+**Technical Document Features:**
+
+- **Compelling Technical Introduction**: Engaging technical opening that establishes research significance
+- **Comprehensive Technical TOC**: Complete navigation structure for technical reference
+- **Exhaustive Technical Research Coverage**: All technical aspects of {{research_topic}} thoroughly analyzed
+- **Executive Technical Summary**: Key technical findings and strategic implications highlighted
+- **Strategic Technical Recommendations**: Actionable technical insights based on comprehensive research
+- **Complete Technical Source Citations**: Every technical claim verified with {{current_year}} sources
+
+**Technical Research Completeness:**
+
+- Technical landscape and architecture analysis fully documented
+- Implementation approaches and best practices comprehensively covered
+- Technology stack evolution and trends detailed
+- Integration, performance, and security analysis complete
+- Strategic technical insights and implementation guidance provided
+
+**Technical Document Standards Met:**
+
+- Exhaustive technical research with no critical gaps
+- Professional technical structure and compelling narrative
+- As long as needed for comprehensive technical coverage
+- Multiple independent technical sources for all claims
+- {{current_year}} technical data throughout with proper citations
+
+**Ready to complete this comprehensive technical research document?**
+[C] Complete Research - Save final comprehensive technical document
+
+### 6. Handle Final Technical Completion
+
+#### If 'C' (Complete Research):
+
+- Append the complete technical document to the research file
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
+- Complete the technical research workflow
+- Provide final technical document delivery confirmation
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the complete comprehensive technical research document using the full structure above.
+
+## SUCCESS METRICS:
+
+✅ Compelling technical introduction with research significance
+✅ Comprehensive technical table of contents with complete document structure
+✅ Exhaustive technical research coverage across all technical aspects
+✅ Executive technical summary with key findings and strategic implications
+✅ Strategic technical recommendations grounded in comprehensive research
+✅ Complete technical source verification with {{current_year}} citations
+✅ Professional technical document structure and compelling narrative
+✅ [C] complete option presented and handled correctly
+✅ Technical research workflow completed with comprehensive document
+
+## FAILURE MODES:
+
+❌ Not producing compelling technical introduction
+❌ Missing comprehensive technical table of contents
+❌ Incomplete technical research coverage across technical aspects
+❌ Not providing executive technical summary with key findings
+❌ Missing strategic technical recommendations based on research
+❌ Not using {{current_year}} technical sources for all factual claims
+❌ Producing technical document without professional structure
+❌ Not presenting completion option for final technical document
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## COMPREHENSIVE TECHNICAL DOCUMENT STANDARDS:
+
+This step ensures the final technical research document:
+
+- Serves as an authoritative technical reference on {{research_topic}}
+- Provides strategic technical insights for informed decision-making
+- Includes comprehensive technical coverage with no gaps
+- Maintains rigorous technical source verification standards
+- Delivers strategic technical insights and actionable recommendations
+- Meets professional technical research document quality standards
+
+## TECHNICAL RESEARCH WORKFLOW COMPLETION:
+
+When 'C' is selected:
+
+- All technical research steps completed (1-5)
+- Comprehensive technical research document generated
+- Professional technical document structure with intro, TOC, and summary
+- All technical sections appended with source citations
+- Technical research workflow status updated to complete
+- Final comprehensive technical research document delivered to user
+
+## FINAL TECHNICAL DELIVERABLE:
+
+Complete authoritative technical research document on {{research_topic}} that:
+
+- Establishes technical credibility through comprehensive research
+- Provides strategic technical insights for informed decision-making
+- Serves as technical reference document for continued use
+- Maintains highest technical research quality standards with {{current_year}} verification
+
+Congratulations on completing comprehensive technical research with professional documentation! 🎉

src/modules/bmm/workflows/1-analysis/research/template-deep-prompt.md

@@ -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)._

src/modules/bmm/workflows/1-analysis/research/template-market.md

@@ -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._

src/modules/bmm/workflows/1-analysis/research/template-technical.md

@@ -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._

src/modules/bmm/workflows/1-analysis/research/workflow.md

@@ -0,0 +1,198 @@
+---
+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, exhaustive research across multiple domains using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.
+
+**Document Standards:**
+
+- **Comprehensive Coverage**: Exhaustive research with no critical gaps
+- **Source Verification**: Every factual claim cited with URLs from {{current_year}}
+- **Document Length**: As long as needed to fully cover the research topic
+- **Professional Structure**: Compelling narrative introduction, detailed TOC, and comprehensive summary
+- **Authoritative Sources**: Multiple independent sources for all critical claims
+
+**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.
+
+**Final Deliverable**: A complete research document that serves as an authoritative reference on the research topic with:
+
+- Compelling narrative introduction
+- Comprehensive table of contents
+- Detailed research sections with proper citations
+- Executive summary and conclusions
+
+---
+
+## 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.
+
+**Let me help you clarify what you'd like to research.**
+
+**First, tell me: What specific topic, problem, or area do you want to research?**
+
+For example:
+
+- 'The electric vehicle market in Europe'
+- 'Cloud migration strategies for healthcare'
+- 'AI implementation in financial services'
+- 'Sustainable packaging regulations'
+- 'Or anything else you have in mind...'
+
+### Topic Exploration and Clarification
+
+Based on the user's initial topic, explore and refine the research scope:
+
+#### Topic Clarification Questions:
+
+1. **Core Topic**: "What exactly about [topic] are you most interested in?"
+2. **Research Goals**: "What do you hope to achieve with this research?"
+3. **Scope**: "Should we focus broadly or dive deep into specific aspects?"
+4. **Timeline**: "Are you looking at current state, historical context, or future trends?"
+5. **Application**: "How will you use this research? (product development, strategy, academic, etc.)"
+
+#### Context Building:
+
+- **Initial Input**: User provides topic or research interest
+- **Collaborative Refinement**: Work together to clarify scope and objectives
+- **Goal Alignment**: Ensure research direction matches user needs
+- **Research Boundaries**: Establish clear focus areas and deliverables
+
+### Research Type Identification
+
+After understanding the research topic and goals, identify the most appropriate research approach:
+
+**Research Type Options:**
+
+1. **Market Research** - Market size, growth, competition, customer insights
+   _Best for: Understanding market dynamics, customer behavior, competitive landscape_
+
+2. **Domain Research** - Industry analysis, regulations, technology trends in specific domain
+   _Best for: Understanding industry context, regulatory environment, ecosystem_
+
+3. **Technical Research** - Technology evaluation, architecture decisions, implementation approaches
+   _Best for: Technical feasibility, technology selection, implementation strategies_
+
+**Recommendation**: Based on [topic] and [goals], I recommend [suggested research type] because [specific rationale].
+
+**What type of research would work best for your needs?**
+
+### Research Type Routing
+
+Based on user selection, route to appropriate sub-workflow with the discovered topic:
+
+#### If Market Research:
+
+- Set `research_type = "market"`
+- Set `research_topic = [discovered topic from discussion]`
+- Set output file: `{output_folder}/analysis/research/market-{{research_topic}}-research-{{date}}.md`
+- Load: `./market-steps/step-01-init.md` with topic context
+
+#### If Domain Research:
+
+- Set `research_type = "domain"`
+- Set `research_topic = [discovered topic from discussion]`
+- Set output file: `{output_folder}/analysis/research/domain-{{research_topic}}-research-{{date}}.md`
+- Load: `./domain-steps/step-01-init.md` with topic context
+
+#### If Technical Research:
+
+- Set `research_type = "technical"`
+- Set `research_topic = [discovered topic from discussion]`
+- Set output file: `{output_folder}/analysis/research/technical-{{research_topic}}-research-{{date}}.md`
+- Load: `./technical-steps/step-01-init.md` with topic context
+
+**Important**: The discovered topic from the collaborative discussion should be passed to the research initialization steps, so they don't need to ask "What do you want to research?" again - they can focus on refining the scope for their specific research type.
+
+### Document Initialization
+
+Create research document with proper metadata:
+
+```yaml
+---
+stepsCompleted: [1]
+inputDocuments: []
+workflowType: 'research'
+lastStep: 1
+research_type: '{{research_type}}'
+research_topic: '{{research_topic}}'
+research_goals: '{{research_goals}}'
+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.

src/modules/bmm/workflows/1-analysis/research/workflow.yaml

@@ -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"

src/modules/bmm/workflows/2-plan-workflows/create-ux-design/checklist.md

@@ -1,310 +0,0 @@
-# Create UX Design Workflow Validation Checklist
-
-**Purpose**: Validate UX Design Specification is complete, collaborative, and implementation-ready.
-
-**Paradigm**: Visual collaboration-driven, not template generation
-
-**Expected Outputs**:
-
-- ux-design-specification.md
-- ux-color-themes.html (color theme visualizer)
-- ux-design-directions.html (design mockups)
-- Optional: ux-prototype.html, ux-component-showcase.html, ai-frontend-prompt.md
-
----
-
-## 1. Output Files Exist
-
-- [ ] **ux-design-specification.md** created in output folder
-- [ ] **ux-color-themes.html** generated (interactive color exploration)
-- [ ] **ux-design-directions.html** generated (6-8 design mockups)
-- [ ] No unfilled {{template_variables}} in specification
-- [ ] All sections have content (not placeholder text)
-
----
-
-## 2. Collaborative Process Validation
-
-**The workflow should facilitate decisions WITH the user, not FOR them**
-
-- [ ] **Design system chosen by user** (not auto-selected)
-- [ ] **Color theme selected from options** (user saw visualizations and chose)
-- [ ] **Design direction chosen from mockups** (user explored 6-8 options)
-- [ ] **User journey flows designed collaboratively** (options presented, user decided)
-- [ ] **UX patterns decided with user input** (not just generated)
-- [ ] **Decisions documented WITH rationale** (why each choice was made)
-
----
-
-## 3. Visual Collaboration Artifacts
-
-### Color Theme Visualizer
-
-- [ ] **HTML file exists and is valid** (ux-color-themes.html)
-- [ ] **Shows 3-4 theme options** (or documented existing brand)
-- [ ] **Each theme has complete palette** (primary, secondary, semantic colors)
-- [ ] **Live UI component examples** in each theme (buttons, forms, cards)
-- [ ] **Side-by-side comparison** enabled
-- [ ] **User's selection documented** in specification
-
-### Design Direction Mockups
-
-- [ ] **HTML file exists and is valid** (ux-design-directions.html)
-- [ ] **6-8 different design approaches** shown
-- [ ] **Full-screen mockups** of key screens
-- [ ] **Design philosophy labeled** for each direction (e.g., "Dense Dashboard", "Spacious Explorer")
-- [ ] **Interactive navigation** between directions
-- [ ] **Responsive preview** toggle available
-- [ ] **User's choice documented WITH reasoning** (what they liked, why it fits)
-
----
-
-## 4. Design System Foundation
-
-- [ ] **Design system chosen** (or custom design decision documented)
-- [ ] **Current version identified** (if using established system)
-- [ ] **Components provided by system documented**
-- [ ] **Custom components needed identified**
-- [ ] **Decision rationale clear** (why this system for this project)
-
----
-
-## 5. Core Experience Definition
-
-- [ ] **Defining experience articulated** (the ONE thing that makes this app unique)
-- [ ] **Novel UX patterns identified** (if applicable)
-- [ ] **Novel patterns fully designed** (interaction model, states, feedback)
-- [ ] **Core experience principles defined** (speed, guidance, flexibility, feedback)
-
----
-
-## 6. Visual Foundation
-
-### Color System
-
-- [ ] **Complete color palette** (primary, secondary, accent, semantic, neutrals)
-- [ ] **Semantic color usage defined** (success, warning, error, info)
-- [ ] **Color accessibility considered** (contrast ratios for text)
-- [ ] **Brand alignment** (follows existing brand or establishes new identity)
-
-### Typography
-
-- [ ] **Font families selected** (heading, body, monospace if needed)
-- [ ] **Type scale defined** (h1-h6, body, small, etc.)
-- [ ] **Font weights documented** (when to use each)
-- [ ] **Line heights specified** for readability
-
-### Spacing & Layout
-
-- [ ] **Spacing system defined** (base unit, scale)
-- [ ] **Layout grid approach** (columns, gutters)
-- [ ] **Container widths** for different breakpoints
-
----
-
-## 7. Design Direction
-
-- [ ] **Specific direction chosen** from mockups (not generic)
-- [ ] **Layout pattern documented** (navigation, content structure)
-- [ ] **Visual hierarchy defined** (density, emphasis, focus)
-- [ ] **Interaction patterns specified** (modal vs inline, disclosure approach)
-- [ ] **Visual style documented** (minimal, balanced, rich, maximalist)
-- [ ] **User's reasoning captured** (why this direction fits their vision)
-
----
-
-## 8. User Journey Flows
-
-- [ ] **All critical journeys from PRD designed** (no missing flows)
-- [ ] **Each flow has clear goal** (what user accomplishes)
-- [ ] **Flow approach chosen collaboratively** (user picked from options)
-- [ ] **Step-by-step documentation** (screens, actions, feedback)
-- [ ] **Decision points and branching** defined
-- [ ] **Error states and recovery** addressed
-- [ ] **Success states specified** (completion feedback)
-- [ ] **Mermaid diagrams or clear flow descriptions** included
-
----
-
-## 9. Component Library Strategy
-
-- [ ] **All required components identified** (from design system + custom)
-- [ ] **Custom components fully specified**:
-  - Purpose and user-facing value
-  - Content/data displayed
-  - User actions available
-  - All states (default, hover, active, loading, error, disabled)
-  - Variants (sizes, styles, layouts)
-  - Behavior on interaction
-  - Accessibility considerations
-- [ ] **Design system components customization needs** documented
-
----
-
-## 10. UX Pattern Consistency Rules
-
-**These patterns ensure consistent UX across the entire app**
-
-- [ ] **Button hierarchy defined** (primary, secondary, tertiary, destructive)
-- [ ] **Feedback patterns established** (success, error, warning, info, loading)
-- [ ] **Form patterns specified** (labels, validation, errors, help text)
-- [ ] **Modal patterns defined** (sizes, dismiss behavior, focus, stacking)
-- [ ] **Navigation patterns documented** (active state, breadcrumbs, back button)
-- [ ] **Empty state patterns** (first use, no results, cleared content)
-- [ ] **Confirmation patterns** (when to confirm destructive actions)
-- [ ] **Notification patterns** (placement, duration, stacking, priority)
-- [ ] **Search patterns** (trigger, results, filters, no results)
-- [ ] **Date/time patterns** (format, timezone, pickers)
-
-**Each pattern should have:**
-
-- [ ] Clear specification (how it works)
-- [ ] Usage guidance (when to use)
-- [ ] Examples (concrete implementations)
-
----
-
-## 11. Responsive Design
-
-- [ ] **Breakpoints defined** for target devices (mobile, tablet, desktop)
-- [ ] **Adaptation patterns documented** (how layouts change)
-- [ ] **Navigation adaptation** (how nav changes on small screens)
-- [ ] **Content organization changes** (multi-column to single, grid to list)
-- [ ] **Touch targets adequate** on mobile (minimum size specified)
-- [ ] **Responsive strategy aligned** with chosen design direction
-
----
-
-## 12. Accessibility
-
-- [ ] **WCAG compliance level specified** (A, AA, or AAA)
-- [ ] **Color contrast requirements** documented (ratios for text)
-- [ ] **Keyboard navigation** addressed (all interactive elements accessible)
-- [ ] **Focus indicators** specified (visible focus states)
-- [ ] **ARIA requirements** noted (roles, labels, announcements)
-- [ ] **Screen reader considerations** (meaningful labels, structure)
-- [ ] **Alt text strategy** for images
-- [ ] **Form accessibility** (label associations, error identification)
-- [ ] **Testing strategy** defined (automated tools, manual testing)
-
----
-
-## 13. Coherence and Integration
-
-- [ ] **Design system and custom components visually consistent**
-- [ ] **All screens follow chosen design direction**
-- [ ] **Color usage consistent with semantic meanings**
-- [ ] **Typography hierarchy clear and consistent**
-- [ ] **Similar actions handled the same way** (pattern consistency)
-- [ ] **All PRD user journeys have UX design**
-- [ ] **All entry points designed**
-- [ ] **Error and edge cases handled**
-- [ ] **Every interactive element meets accessibility requirements**
-- [ ] **All flows keyboard-navigable**
-- [ ] **Colors meet contrast requirements**
-
----
-
-## 14. Cross-Workflow Alignment (Epics File Update)
-
-**As UX design progresses, you discover implementation details that affect the story breakdown**
-
-### Stories Discovered During UX Design
-
-- [ ] **Review epics.md file** for alignment with UX design
-- [ ] **New stories identified** during UX design that weren't in epics.md:
-  - [ ] Custom component build stories (if significant)
-  - [ ] UX pattern implementation stories
-  - [ ] Animation/transition stories
-  - [ ] Responsive adaptation stories
-  - [ ] Accessibility implementation stories
-  - [ ] Edge case handling stories discovered during journey design
-  - [ ] Onboarding/empty state stories
-  - [ ] Error state handling stories
-
-### Story Complexity Adjustments
-
-- [ ] **Existing stories complexity reassessed** based on UX design:
-  - [ ] Stories that are now more complex (UX revealed additional requirements)
-  - [ ] Stories that are simpler (design system handles more than expected)
-  - [ ] Stories that should be split (UX design shows multiple components/flows)
-  - [ ] Stories that can be combined (UX design shows they're tightly coupled)
-
-### Epic Alignment
-
-- [ ] **Epic scope still accurate** after UX design
-- [ ] **New epic needed** for discovered work (if significant)
-- [ ] **Epic ordering might change** based on UX dependencies
-
-### Action Items for Epics File Update
-
-- [ ] **List of new stories to add** to epics.md documented
-- [ ] **Complexity adjustments noted** for existing stories
-- [ ] **Update epics.md** OR flag for architecture review first
-- [ ] **Rationale documented** for why new stories/changes are needed
-
-**Note:** If significant story changes are identified, consider running architecture workflow BEFORE updating epics.md, since architecture decisions might reveal additional adjustments needed.
-
----
-
-## 15. Decision Rationale
-
-**Unlike template-driven workflows, this workflow should document WHY**
-
-- [ ] **Design system choice has rationale** (why this fits the project)
-- [ ] **Color theme selection has reasoning** (why this emotional impact)
-- [ ] **Design direction choice explained** (what user liked, how it fits vision)
-- [ ] **User journey approaches justified** (why this flow pattern)
-- [ ] **UX pattern decisions have context** (why these patterns for this app)
-- [ ] **Responsive strategy aligned with user priorities**
-- [ ] **Accessibility level appropriate for deployment intent**
-
----
-
-## 16. Implementation Readiness
-
-- [ ] **Designers can create high-fidelity mockups** from this spec
-- [ ] **Developers can implement** with clear UX guidance
-- [ ] **Sufficient detail** for frontend development
-- [ ] **Component specifications actionable** (states, variants, behaviors)
-- [ ] **Flows implementable** (clear steps, decision logic, error handling)
-- [ ] **Visual foundation complete** (colors, typography, spacing all defined)
-- [ ] **Pattern consistency enforceable** (clear rules for implementation)
-
----
-
-## 17. Critical Failures (Auto-Fail)
-
-- [ ] ❌ **No visual collaboration** (color themes or design mockups not generated)
-- [ ] ❌ **User not involved in decisions** (auto-generated without collaboration)
-- [ ] ❌ **No design direction chosen** (missing key visual decisions)
-- [ ] ❌ **No user journey designs** (critical flows not documented)
-- [ ] ❌ **No UX pattern consistency rules** (implementation will be inconsistent)
-- [ ] ❌ **Missing core experience definition** (no clarity on what makes app unique)
-- [ ] ❌ **No component specifications** (components not actionable)
-- [ ] ❌ **Responsive strategy missing** (for multi-platform projects)
-- [ ] ❌ **Accessibility ignored** (no compliance target or requirements)
-- [ ] ❌ **Generic/templated content** (not specific to this project)
-
----
-
-## Validation Notes
-
-**Document findings:**
-
-- UX Design Quality: [Exceptional / Strong / Adequate / Needs Work / Incomplete]
-- Collaboration Level: [Highly Collaborative / Collaborative / Somewhat Collaborative / Generated]
-- Visual Artifacts: [Complete & Interactive / Partial / Missing]
-- Implementation Readiness: [Ready / Needs Design Phase / Not Ready]
-
-## **Strengths:**
-
-## **Areas for Improvement:**
-
-## **Recommended Actions:**
-
-**Ready for next phase?** [Yes - Proceed to Design / Yes - Proceed to Development / Needs Refinement]
-
----
-
-_This checklist validates collaborative UX design facilitation, not template generation. A successful UX workflow creates design decisions WITH the user through visual exploration and informed choices._

src/modules/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md

@@ -1,289 +0,0 @@
-# Create UX Design Workflow Instructions
-
-<workflow name="create-ux-design">
-
-<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
-<critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical>
-<critical>Communicate all responses in {communication_language} and tailor to {user_skill_level}</critical>
-<critical>Generate all documents in {document_output_language}</critical>
-<critical>SAVE PROGRESS after each major step - use <template-output> tags throughout</critical>
-<critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions</critical>
-<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, follow workflow.xml substep 2c: SAVE → SHOW checkpoint separator → DISPLAY content → PRESENT options → WAIT for user response</critical>
-
-<step n="0" goal="Validate workflow readiness" tag="workflow-status">
-<action>Check if {output_folder}/bmm-workflow-status.yaml exists</action>
-
-<check if="status file not found">
-  <output>No workflow status file found. Create UX Design can run standalone or as part of BMM planning workflow.</output>
-  <action>Set standalone_mode = true</action>
-</check>
-
-<check if="status file found">
-  <action>Load and validate workflow status, check if create-ux-design is completed or out of sequence</action>
-  <ask>UX Design already completed or out of sequence. Continue anyway? (y/n)</ask>
-  <check if="n">
-    <action>Exit workflow</action>
-  </check>
-  <action>Set standalone_mode = false</action>
-</check>
-</step>
-
-<step n="1" goal="Discover and load input documents">
-<invoke-protocol name="discover_inputs" />
-</step>
-
-<step n="2" goal="Understand project and users">
-<action>Review loaded context from Step 1</action>
-
-<check if="documents_found">
-  <output>I've loaded your project documentation. Let me confirm what I'm seeing:
-
-**Project:** {{project_summary_from_docs}}
-**Target Users:** {{user_summary_from_docs}}</output>
-<ask>Does this match your understanding? Any corrections or additions?</ask>
-</check>
-
-<check if="no_documents_found">
-  <ask>Let's start by understanding what you're building.
-
-**What are you building?** (1-2 sentences)
-**Who is this for?** (Describe your ideal user)</ask>
-</check>
-
-<template-output>project_and_users_confirmed</template-output>
-</step>
-
-<step n="3" goal="Define core experience and platform">
-<ask>Now let's dig into the experience itself.
-
-**What's the core experience?** (What's the ONE thing users will do most?)
-**What should be absolutely effortless?**
-**Which user action is most critical to get right?**
-**Platform:** Web, mobile app, desktop, multiple?</ask>
-
-<template-output>core_experience_and_platform</template-output>
-</step>
-
-<step n="4" goal="Define desired emotional response">
-<ask>What should users FEEL when using this?
-
-Empowered and in control? Delighted and surprised? Efficient and productive? Creative and inspired? Calm and focused? Connected and engaged? Something else?
-
-What feeling would make them tell a friend about this?</ask>
-
-<template-output>desired_emotional_response</template-output>
-</step>
-
-<step n="5" goal="Gather inspiration and analyze patterns">
-<ask>Name 2-3 apps your users already love and USE regularly.
-
-For each one, what do they do well from a UX perspective? What makes the experience compelling?</ask>
-
-<action>Research mentioned apps to analyze current UX patterns and principles</action>
-<template-output>inspiration_analysis</template-output>
-</step>
-
-<step n="6" goal="Set facilitation approach and synthesize understanding">
-<action>Analyze project complexity and set facilitation mode based on {user_skill_level}</action>
-
-<output>Here's what I'm understanding about {{project_name}}:
-
-**Vision:** {{project_vision_summary}}
-**Users:** {{user_summary}}
-**Core Experience:** {{core_action_summary}}
-**Desired Feeling:** {{emotional_goal}}
-**Platform:** {{platform_summary}}
-**Inspiration:** {{inspiration_summary_with_ux_patterns}}
-
-This helps me understand both what we're building and the experience we're aiming for. Let's start designing!</output>
-
-<action>Load UX design template and initialize output document</action>
-<template-output>project_vision</template-output>
-</step>
-
-<step n="7" goal="Choose design system">
-<action>Identify appropriate design system options based on platform and requirements</action>
-
-<ask>Which design system approach resonates with you?
-
-I'll present options for your platform - think of design systems like foundations that provide proven UI components and patterns, speeding development and ensuring consistency.
-
-- Want complete visual uniqueness? (→ custom)
-- Want fast development with great defaults? (→ established system)
-- Have brand guidelines to follow? (→ themeable system)</ask>
-
-<template-output>design_system_decision</template-output>
-</step>
-
-<step n="8" goal="Identify defining experience">
-<ask>What's your app's defining experience - the core interaction that, if we nail it, everything else follows?
-
-When someone describes your app to a friend, what would they say?
-
-Examples: "Swipe to match with people" (Tinder), "Share photos that disappear" (Snapchat), "Have conversations with AI" (ChatGPT)</ask>
-
-<action>Analyze if this core experience has established UX patterns or requires novel pattern design</action>
-<template-output>defining_experience</template-output>
-</step>
-
-<step n="9" goal="Design novel patterns (if needed)">
-<check if="novel_pattern_detected">
-  <ask>The {{pattern_name}} interaction is novel! Let's design this interaction systematically.
-
-What's the user's goal? How should they initiate this action? What feedback should they see? How do they know it succeeded? What if something goes wrong?</ask>
-<template-output>novel_pattern_mechanics</template-output>
-</check>
-</step>
-
-<step n="10" goal="Define core experience principles">
-<output>Based on our understanding, here are the guiding principles for the entire experience:
-
-**Speed:** {{speed_principle}}
-**Guidance:** {{guidance_principle}}
-**Flexibility:** {{flexibility_principle}}
-**Feedback:** {{feedback_principle}}
-
-These principles will guide every UX decision from here forward.</output>
-<template-output>core_experience_principles</template-output>
-</step>
-
-<step n="11" goal="Choose color theme and visual foundation">
-<ask>Do you have existing brand guidelines or specific color palette? (y/n)
-
-If no, I'll generate theme options based on your project's personality and goals.</ask>
-
-<check if="existing_brand == true">
-  <action>Extract and document brand colors, generate semantic color mappings</action>
-</check>
-
-<check if="existing_brand == false">
-  <action>Generate comprehensive HTML color theme visualizer with multiple options</action>
-  <output>🎨 I've created a color theme visualizer! Open {color_themes_html} to explore theme options with complete UI examples.</output>
-  <ask>Which color theme direction resonates most? You can choose, combine, or request variations.</ask>
-</check>
-
-<action>Define typography system, spacing, and layout foundation</action>
-<template-output>visual_foundation</template-output>
-</step>
-
-<step n="12" goal="Generate design direction mockups">
-<action>Create 6-8 different design direction variations exploring layout, hierarchy, density, interaction patterns, and visual weight</action>
-
-<action>Generate comprehensive HTML design direction showcase with full-screen mockups, interactive states, and comparison tools</action>
-<output>🎨 Design Direction Mockups Generated! Open: {design_directions_html}
-
-Each mockup shows a complete vision for your app's look and feel. As you explore, look for:
-✓ Which layout feels most intuitive?
-✓ Which information hierarchy matches your priorities?
-✓ Which interaction style fits your core experience?
-✓ Which visual weight feels right for your brand?</output>
-
-<ask>Which design direction(s) resonate most? Pick a favorite, combine elements, or request modifications.</ask>
-<template-output>design_direction_decision</template-output>
-</step>
-
-<step n="13" goal="Design user journeys">
-<action>Extract critical user journeys from PRD</action>
-
-<for-each journey="critical_user_journeys">
-  <ask>Let's design the flow for {{journey_name}}. Walk me through how a user should accomplish this task - entry, input, feedback, success. Consider the minimum steps to value, decision points, error recovery, and progressive disclosure.</ask>
-
-<action>Present 2-3 flow approach options based on journey complexity, then create detailed flow documentation with Mermaid diagram</action>
-</for-each>
-
-<template-output>user_journey_flows</template-output>
-</step>
-
-<step n="14" goal="Define component strategy">
-<action>Identify required components from design system vs custom needs</action>
-
-<ask>For components not covered by {{design_system}}, let's define them together.
-
-For each custom component: What's its purpose? What content/data does it display? What actions can users take? What states does it have?</ask>
-
-<action>Document each custom component with anatomy, states, variants, behavior, and accessibility requirements</action>
-<template-output>component_library_strategy</template-output>
-</step>
-
-<step n="15" goal="Define UX pattern decisions">
-<output>Let's establish consistency patterns for how your app behaves in common situations - button hierarchy, feedback patterns, form patterns, modals, navigation, empty states, confirmations, notifications, search, and date/time patterns.</output>
-
-<ask>Do you want to go through each pattern category thoroughly, focus only on the most critical for your app, or let me recommend smart defaults and you override where needed?</ask>
-
-<action>Facilitate pattern decisions with appropriate depth, documenting chosen approaches and rationale for consistency</action>
-<template-output>ux_pattern_decisions</template-output>
-</step>
-
-<step n="16" goal="Define responsive and accessibility strategy">
-<ask>Let's define how your app adapts across devices.
-
-**Desktop:** How should we use extra space? Multi-column? Side navigation?
-**Tablet:** Simplified layout? Touch-optimized?
-**Mobile:** Bottom navigation or hamburger menu? How do layouts collapse?</ask>
-
-<action>Define breakpoint strategy and adaptation patterns</action>
-
-<ask>Accessibility strategy: WCAG Level A (basic), AA (recommended standard), or AAA (highest)?
-
-Based on your deployment intent: {{recommendation}}</ask>
-
-<action>Define accessibility requirements and testing strategy</action>
-<template-output>responsive_accessibility_strategy</template-output>
-</step>
-
-<step n="17" goal="Generate optional visualizations">
-<ask>🎨 One more thing! Want to see your design come to life?
-
-1. **Key Screens Showcase** - 6-8 panels showing your app's main screens with all your design choices applied
-2. **User Journey Visualization** - Step-by-step HTML mockup of one critical user journey
-3. **Something else** - Tell me what you want to see!
-4. **Skip for now** - I'll just finalize the documentation</ask>
-
-<check if="user_wants_visualizations">
-  <action>Generate requested HTML visualizations applying all design decisions</action>
-</check>
-
-<template-output>completion_summary</template-output>
-</step>
-
-<step n="18" goal="Finalize UX design specification">
-<action>Ensure document is complete with all template-output sections filled</action>
-
-<output>✅ **UX Design Specification Complete!**
-
-**Core Deliverables:**
-
-- ✅ UX Design Specification: {default_output_file}
-- ✅ Color Theme Visualizer: {color_themes_html}
-- ✅ Design Direction Mockups: {design_directions_html}
-
-**Recommended Next Steps:**
-
-<check if="tracking_mode == true">
-- **Next required:** {{next_workflow}} ({{next_agent}} agent)
-- **Optional:** Run validation with \*validate-design, or generate additional UX artifacts
-Check status anytime with: `workflow-status`
-</check>
-
-<check if="tracking_mode != true">
-- Run validation checklist with \*validate-design (recommended)
-- **Solution Architecture workflow** (with UX context) - *Recommended next step after completing PRD and UX Design*
-- Or run `workflow-init` to create a workflow path and get guided next steps
-</check>
-
-**Optional Follow-Up Workflows:**
-
-- Wireframe Generation / Figma Design / Interactive Prototype workflows
-- Component Showcase / AI Frontend Prompt workflows
-  </output>
-
-<action>Save final document</action>
-
-<check if="standalone_mode != true">
-  <action>Update workflow status with file path and determine next workflow</action>
-</check>
-
-</step>
-
-</workflow>

src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01-init.md

@@ -0,0 +1,159 @@
+# Step 1: UX Design Workflow Initialization
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder
+- 📋 YOU ARE A UX 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 UX design workflow by detecting continuation state and setting up the design specification document.
+
+## INITIALIZATION SEQUENCE:
+
+### 1. Check for Existing Workflow
+
+First, check if the output document already exists:
+
+- Look for file at `{output_folder}/ux-design-specification.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:
+
+**PRD (Priority: Analysis → Main → Sharded → Whole):**
+
+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: Analysis → Main → Sharded → Whole):**
+
+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: Analysis → Main → Sharded → Whole):**
+
+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:**
+
+- Load ALL discovered files completely (no offset/limit)
+- For sharded folders, load ALL files to get complete picture
+- Track all successfully loaded files in frontmatter `inputDocuments` array
+
+#### B. Create Initial Document
+
+Copy the template from `{installed_path}/ux-design-template.md` to `{output_folder}/ux-design-specification.md`
+Initialize frontmatter with:
+
+```yaml
+---
+stepsCompleted: []
+inputDocuments: []
+workflowType: 'ux-design'
+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: `{output_folder}/ux-design-specification.md` from template
+- Initialized frontmatter with workflow state
+
+**Input Documents Discovered:**
+Report what was found:
+"Welcome {{user_name}}! I've set up your UX design workspace for {{project_name}}.
+
+**Documents Found:**
+
+- PRD: {number of PRD files loaded or "None found"}
+- Product brief: {number of brief files loaded or "None found"}
+- Other context: {number of other 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 UX 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`
+✅ User confirmed document setup and can proceed
+
+## 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
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## NEXT STEP:
+
+After user selects [C] to continue, load `./step-02-discovery.md` to begin the UX discovery phase.
+
+Remember: Do NOT proceed to step-02 until user explicitly selects [C] to continue!

src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01b-continue.md

@@ -0,0 +1,126 @@
+# Step 1B: UX Design Workflow Continuation
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder
+- 📋 YOU ARE A UX 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 UX design 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 UX design collaboration for {{project_name}}.
+
+**Current Progress:**
+
+- Steps completed: {stepsCompleted}
+- Last worked on: Step {lastStep}
+- Context documents available: {len(inputDocuments)} files
+- Current UX design specification is ready with all completed sections
+
+**Document Status:**
+
+- Current UX design document 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-discovery.md`
+- If `lastStep = 2` → Load `./step-03-core-experience.md`
+- If `lastStep = 3` → Load `./step-04-emotional-response.md`
+- Continue this pattern for all steps
+- If `lastStep` indicates final step → 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
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## WORKFLOW ALREADY COMPLETE?
+
+If `lastStep` indicates the final step is completed:
+"Great news! It looks like we've already completed the UX design workflow for {{project_name}}.
+
+The final UX design specification is ready at {output_folder}/ux-design-specification.md with all sections completed through step {finalStepNumber}.
+
+The complete UX design includes visual foundations, user flows, and design specifications ready for implementation.
+
+Would you like me to:
+
+- Review the completed UX design specification with you
+- Suggest next workflow steps (like wireframe generation or architecture)
+- Start a new UX design revision
+
+What would be most helpful?"
+
+## NEXT STEP:
+
+After user confirms they're ready 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!

src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md

@@ -0,0 +1,209 @@
+# Step 2: Project Understanding
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder
+- 📋 YOU ARE A UX FACILITATOR, not a content generator
+- 💬 FOCUS on understanding project context and user needs
+- 🎯 COLLABORATIVE discovery, not assumption-based design
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis before taking any action
+- ⚠️ Present A/P/C menu after generating project understanding 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 project insights
+- **P (Party Mode)**: Bring multiple perspectives to understand project context
+- **C (Continue)**: Save the content to the document and proceed to next step
+
+## PROTOCOL INTEGRATION:
+
+- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- PROTOCOLS always return to this step's A/P/C menu
+- User accepts/rejects protocol changes before proceeding
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from step 1 are available
+- Input documents (PRD, briefs, epics) already loaded are in memory
+- No additional data files needed for this step
+- Focus on project and user understanding
+
+## YOUR TASK:
+
+Understand the project context, target users, and what makes this product special from a UX perspective.
+
+## PROJECT DISCOVERY SEQUENCE:
+
+### 1. Review Loaded Context
+
+Start by analyzing what we know from the loaded documents:
+"Based on the project documentation we have loaded, let me confirm what I'm understanding about {{project_name}}.
+
+**From the documents:**
+{summary of key insights from loaded PRD, briefs, and other context documents}
+
+**Target Users:**
+{summary of user information from loaded documents}
+
+**Key Features/Goals:**
+{summary of main features and goals from loaded documents}
+
+Does this match your understanding? Are there any corrections or additions you'd like to make?"
+
+### 2. Fill Context Gaps (If no documents or gaps exist)
+
+If no documents were loaded or key information is missing:
+"Since we don't have complete documentation, let's start with the essentials:
+
+**What are you building?** (Describe your product in 1-2 sentences)
+
+**Who is this for?** (Describe your ideal user or target audience)
+
+**What makes this special or different?** (What's the unique value proposition?)
+
+**What's the main thing users will do with this?** (Core user action or goal)"
+
+### 3. Explore User Context Deeper
+
+Dive into user understanding:
+"Let me understand your users better to inform the UX design:
+
+**User Context Questions:**
+
+- What problem are users trying to solve?
+- What frustrates them with current solutions?
+- What would make them say 'this is exactly what I needed'?
+- How tech-savvy are your target users?
+- What devices will they use most?
+- When/where will they use this product?"
+
+### 4. Identify UX Design Challenges
+
+Surface the key UX challenges to address:
+"From what we've discussed, I'm seeing some key UX design considerations:
+
+**Design Challenges:**
+
+- [Identify 2-3 key UX challenges based on project type and user needs]
+- [Note any platform-specific considerations]
+- [Highlight any complex user flows or interactions]
+
+**Design Opportunities:**
+
+- [Identify 2-3 areas where great UX could create competitive advantage]
+- [Note any opportunities for innovative UX patterns]
+
+Does this capture the key UX considerations we need to address?"
+
+### 5. Generate Project Understanding 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
+
+### Project Vision
+
+[Project vision summary based on conversation]
+
+### Target Users
+
+[Target user descriptions based on conversation]
+
+### Key Design Challenges
+
+[Key UX challenges identified based on conversation]
+
+### Design Opportunities
+
+[Design opportunities identified based on conversation]
+```
+
+### 6. Present Content and Menu
+
+Show the generated project understanding content and present choices:
+"I've documented our understanding of {{project_name}} from a UX perspective. This will guide all our design decisions moving forward.
+
+**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 project understanding
+[P] Party Mode - Bring different perspectives on user needs and challenges
+[C] Continue - Save this to the document and move to core experience definition"
+
+### 7. Handle Menu Selection
+
+#### If 'A' (Advanced Elicitation):
+
+- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current project understanding content
+- Process the enhanced project insights that come back
+- Ask user: "Accept these improvements to the project understanding? (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 {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current project understanding
+- Process the collaborative insights and different perspectives that come back
+- Ask user: "Accept these changes to the project understanding? (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 `{output_folder}/ux-design-specification.md`
+- Update frontmatter: `stepsCompleted: [1, 2]`
+- Load `./step-03-core-experience.md`
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the document using the structure from step 5.
+
+## SUCCESS METRICS:
+
+✅ All available context documents reviewed and synthesized
+✅ Project vision clearly articulated
+✅ Target users well understood
+✅ Key UX challenges identified
+✅ Design opportunities surfaced
+✅ A/P/C menu presented and handled correctly
+✅ Content properly appended to document when C selected
+
+## FAILURE MODES:
+
+❌ Not reviewing loaded context documents thoroughly
+❌ Making assumptions about users without asking
+❌ Missing key UX challenges that will impact design
+❌ Not identifying design opportunities
+❌ Generating generic content without real project insight
+❌ Not presenting A/P/C menu after content generation
+❌ Appending content without user selecting 'C'
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## NEXT STEP:
+
+After user selects 'C' and content is saved to document, load `./step-03-core-experience.md` to define the core user experience.
+
+Remember: Do NOT proceed to step-03 until user explicitly selects 'C' from the A/P/C menu and content is saved!

src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md

@@ -0,0 +1,215 @@
+# Step 3: Core Experience Definition
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder
+- 📋 YOU ARE A UX FACILITATOR, not a content generator
+- 💬 FOCUS on defining the core user experience and platform
+- 🎯 COLLABORATIVE discovery, not assumption-based design
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis before taking any action
+- ⚠️ Present A/P/C menu after generating core experience 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 experience insights
+- **P (Party Mode)**: Bring multiple perspectives to define optimal user experience
+- **C (Continue)**: Save the content to the document and proceed to next step
+
+## PROTOCOL INTEGRATION:
+
+- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- PROTOCOLS always return to this step's A/P/C menu
+- User accepts/rejects protocol changes before proceeding
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- Project understanding from step 2 informs this step
+- No additional data files needed for this step
+- Focus on core experience and platform decisions
+
+## YOUR TASK:
+
+Define the core user experience, platform requirements, and what makes the interaction effortless.
+
+## CORE EXPERIENCE DISCOVERY SEQUENCE:
+
+### 1. Define Core User Action
+
+Start by identifying the most important user interaction:
+"Now let's dig into the heart of the user experience for {{project_name}}.
+
+**Core Experience Questions:**
+
+- What's the ONE thing users will do most frequently?
+- What user action is absolutely critical to get right?
+- What should be completely effortless for users?
+- If we nail one interaction, everything else follows - what is it?
+
+Think about the core loop or primary action that defines your product's value."
+
+### 2. Explore Platform Requirements
+
+Determine where and how users will interact:
+"Let's define the platform context for {{project_name}}:
+
+**Platform Questions:**
+
+- Web, mobile app, desktop, or multiple platforms?
+- Will this be primarily touch-based or mouse/keyboard?
+- Any specific platform requirements or constraints?
+- Do we need to consider offline functionality?
+- Any device-specific capabilities we should leverage?"
+
+### 3. Identify Effortless Interactions
+
+Surface what should feel magical or completely seamless:
+"**Effortless Experience Design:**
+
+- What user actions should feel completely natural and require zero thought?
+- Where do users currently struggle with similar products?
+- What interaction, if made effortless, would create delight?
+- What should happen automatically without user intervention?
+- Where can we eliminate steps that competitors require?"
+
+### 4. Define Critical Success Moments
+
+Identify the moments that determine success or failure:
+"**Critical Success Moments:**
+
+- What's the moment where users realize 'this is better'?
+- When does the user feel successful or accomplished?
+- What interaction, if failed, would ruin the experience?
+- What are the make-or-break user flows?
+- Where does first-time user success happen?"
+
+### 5. Synthesize Experience Principles
+
+Extract guiding principles from the conversation:
+"Based on our discussion, I'm hearing these core experience principles for {{project_name}}:
+
+**Experience Principles:**
+
+- [Principle 1 based on core action focus]
+- [Principle 2 based on effortless interactions]
+- [Principle 3 based on platform considerations]
+- [Principle 4 based on critical success moments]
+
+These principles will guide all our UX decisions. Do these capture what's most important?"
+
+### 6. Generate Core Experience Content
+
+Prepare the content to append to the document:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Core User Experience
+
+### Defining Experience
+
+[Core experience definition based on conversation]
+
+### Platform Strategy
+
+[Platform requirements and decisions based on conversation]
+
+### Effortless Interactions
+
+[Effortless interaction areas identified based on conversation]
+
+### Critical Success Moments
+
+[Critical success moments defined based on conversation]
+
+### Experience Principles
+
+[Guiding principles for UX decisions based on conversation]
+```
+
+### 7. Present Content and Menu
+
+Show the generated core experience content and present choices:
+"I've defined the core user experience for {{project_name}} based on our conversation. This establishes the foundation for all our UX design decisions.
+
+**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 refine the core experience definition
+[P] Party Mode - Bring different perspectives on the user experience
+[C] Continue - Save this to the document and move to emotional response definition"
+
+### 8. Handle Menu Selection
+
+#### If 'A' (Advanced Elicitation):
+
+- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current core experience content
+- Process the enhanced experience insights that come back
+- Ask user: "Accept these improvements to the core experience definition? (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 {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current core experience definition
+- Process the collaborative experience improvements that come back
+- Ask user: "Accept these changes to the core experience definition? (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 `{output_folder}/ux-design-specification.md`
+- Update frontmatter: `stepsCompleted: [1, 2, 3]`
+- Load `./step-04-emotional-response.md`
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the document using the structure from step 6.
+
+## SUCCESS METRICS:
+
+✅ Core user action clearly identified and defined
+✅ Platform requirements thoroughly explored
+✅ Effortless interaction areas identified
+✅ Critical success moments mapped out
+✅ Experience principles established as guiding framework
+✅ A/P/C menu presented and handled correctly
+✅ Content properly appended to document when C selected
+
+## FAILURE MODES:
+
+❌ Missing the core user action that defines the product
+❌ Not properly considering platform requirements
+❌ Overlooking what should be effortless for users
+❌ Not identifying critical make-or-break interactions
+❌ Experience principles too generic or not actionable
+❌ Not presenting A/P/C menu after content generation
+❌ Appending content without user selecting 'C'
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## NEXT STEP:
+
+After user selects 'C' and content is saved to document, load `./step-04-emotional-response.md` to define desired emotional responses.
+
+Remember: Do NOT proceed to step-04 until user explicitly selects 'C' from the A/P/C menu and content is saved!

src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md

@@ -0,0 +1,218 @@
+# Step 4: Desired Emotional Response
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder
+- 📋 YOU ARE A UX FACILITATOR, not a content generator
+- 💬 FOCUS on defining desired emotional responses and user feelings
+- 🎯 COLLABORATIVE discovery, not assumption-based design
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis before taking any action
+- ⚠️ Present A/P/C menu after generating emotional response 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 emotional insights
+- **P (Party Mode)**: Bring multiple perspectives to define optimal emotional responses
+- **C (Continue)**: Save the content to the document and proceed to next step
+
+## PROTOCOL INTEGRATION:
+
+- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- PROTOCOLS always return to this step's A/P/C menu
+- User accepts/rejects protocol changes before proceeding
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- Core experience definition from step 3 informs emotional response
+- No additional data files needed for this step
+- Focus on user feelings and emotional design goals
+
+## YOUR TASK:
+
+Define the desired emotional responses users should feel when using the product.
+
+## EMOTIONAL RESPONSE DISCOVERY SEQUENCE:
+
+### 1. Explore Core Emotional Goals
+
+Start by understanding the emotional objectives:
+"Now let's think about how {{project_name}} should make users feel.
+
+**Emotional Response Questions:**
+
+- What should users FEEL when using this product?
+- What emotion would make them tell a friend about this?
+- How should users feel after accomplishing their primary goal?
+- What feeling differentiates this from competitors?
+
+Common emotional goals: Empowered and in control? Delighted and surprised? Efficient and productive? Creative and inspired? Calm and focused? Connected and engaged?"
+
+### 2. Identify Emotional Journey Mapping
+
+Explore feelings at different stages:
+"**Emotional Journey Considerations:**
+
+- How should users feel when they first discover the product?
+- What emotion during the core experience/action?
+- How should they feel after completing their task?
+- What if something goes wrong - what emotional response do we want?
+- How should they feel when returning to use it again?"
+
+### 3. Define Micro-Emotions
+
+Surface subtle but important emotional states:
+"**Micro-Emotions to Consider:**
+
+- Confidence vs. Confusion
+- Trust vs. Skepticism
+- Excitement vs. Anxiety
+- Accomplishment vs. Frustration
+- Delight vs. Satisfaction
+- Belonging vs. Isolation
+
+Which of these emotional states are most critical for your product's success?"
+
+### 4. Connect Emotions to UX Decisions
+
+Link feelings to design implications:
+"**Design Implications:**
+
+- If we want users to feel [emotional state], what UX choices support this?
+- What interactions might create negative emotions we want to avoid?
+- Where can we add moments of delight or surprise?
+- How do we build trust and confidence through design?
+
+**Emotion-Design Connections:**
+
+- [Emotion 1] → [UX design approach]
+- [Emotion 2] → [UX design approach]
+- [Emotion 3] → [UX design approach]"
+
+### 5. Validate Emotional Goals
+
+Check if emotional goals align with product vision:
+"Let me make sure I understand the emotional vision for {{project_name}}:
+
+**Primary Emotional Goal:** [Summarize main emotional response]
+**Secondary Feelings:** [List supporting emotional states]
+**Emotions to Avoid:** [List negative emotions to prevent]
+
+Does this capture the emotional experience you want to create? Any adjustments needed?"
+
+### 6. Generate Emotional Response Content
+
+Prepare the content to append to the document:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Desired Emotional Response
+
+### Primary Emotional Goals
+
+[Primary emotional goals based on conversation]
+
+### Emotional Journey Mapping
+
+[Emotional journey mapping based on conversation]
+
+### Micro-Emotions
+
+[Micro-emotions identified based on conversation]
+
+### Design Implications
+
+[UX design implications for emotional responses based on conversation]
+
+### Emotional Design Principles
+
+[Guiding principles for emotional design based on conversation]
+```
+
+### 7. Present Content and Menu
+
+Show the generated emotional response content and present choices:
+"I've defined the desired emotional responses for {{project_name}}. These emotional goals will guide our design decisions to create the right user experience.
+
+**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 refine the emotional response definition
+[P] Party Mode - Bring different perspectives on user emotional needs
+[C] Continue - Save this to the document and move to inspiration analysis"
+
+### 8. Handle Menu Selection
+
+#### If 'A' (Advanced Elicitation):
+
+- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current emotional response content
+- Process the enhanced emotional insights that come back
+- Ask user: "Accept these improvements to the emotional response definition? (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 {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current emotional response definition
+- Process the collaborative emotional insights that come back
+- Ask user: "Accept these changes to the emotional response definition? (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 `{output_folder}/ux-design-specification.md`
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
+- Load `./step-05-inspiration.md`
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the document using the structure from step 6.
+
+## SUCCESS METRICS:
+
+✅ Primary emotional goals clearly defined
+✅ Emotional journey mapped across user experience
+✅ Micro-emotions identified and addressed
+✅ Design implications connected to emotional responses
+✅ Emotional design principles established
+✅ A/P/C menu presented and handled correctly
+✅ Content properly appended to document when C selected
+
+## FAILURE MODES:
+
+❌ Missing core emotional goals or being too generic
+❌ Not considering emotional journey across different stages
+❌ Overlooking micro-emotions that impact user satisfaction
+❌ Not connecting emotional goals to specific UX design choices
+❌ Emotional principles too vague or not actionable
+❌ Not presenting A/P/C menu after content generation
+❌ Appending content without user selecting 'C'
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## NEXT STEP:
+
+After user selects 'C' and content is saved to document, load `./step-05-inspiration.md` to analyze UX patterns from inspiring products.
+
+Remember: Do NOT proceed to step-05 until user explicitly selects 'C' from the A/P/C menu and content is saved!

src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md

@@ -0,0 +1,233 @@
+# Step 5: UX Pattern Analysis & Inspiration
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder
+- 📋 YOU ARE A UX FACILITATOR, not a content generator
+- 💬 FOCUS on analyzing existing UX patterns and extracting inspiration
+- 🎯 COLLABORATIVE discovery, not assumption-based design
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis before taking any action
+- ⚠️ Present A/P/C menu after generating inspiration analysis 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 develop deeper pattern insights
+- **P ( Party Mode)**: Bring multiple perspectives to analyze UX patterns
+- **C (Continue)**: Save the content to the document and proceed to next step
+
+## PROTOCOL INTEGRATION:
+
+- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- PROTOCOLS always return to this step's A/P/C menu
+- User accepts/rejects protocol changes before proceeding
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- Emotional response goals from step 4 inform pattern analysis
+- No additional data files needed for this step
+- Focus on analyzing existing UX patterns and extracting lessons
+
+## YOUR TASK:
+
+Analyze inspiring products and UX patterns to inform design decisions for the current project.
+
+## INSPIRATION ANALYSIS SEQUENCE:
+
+### 1. Identify User's Favorite Apps
+
+Start by gathering inspiration sources:
+"Let's learn from products your users already love and use regularly.
+
+**Inspiration Questions:**
+
+- Name 2-3 apps your target users already love and USE frequently
+- For each one, what do they do well from a UX perspective?
+- What makes the experience compelling or delightful?
+- What keeps users coming back to these apps?
+
+Think about apps in your category or even unrelated products that have great UX."
+
+### 2. Analyze UX Patterns and Principles
+
+Break down what makes these apps successful:
+"For each inspiring app, let's analyze their UX success:
+
+**For [App Name]:**
+
+- What core problem does it solve elegantly?
+- What makes the onboarding experience effective?
+- How do they handle navigation and information hierarchy?
+- What are their most innovative or delightful interactions?
+- What visual design choices support the user experience?
+- How do they handle errors or edge cases?"
+
+### 3. Extract Transferable Patterns
+
+Identify patterns that could apply to your project:
+"**Transferable UX Patterns:**
+Looking across these inspiring apps, I see patterns we could adapt:
+
+**Navigation Patterns:**
+
+- [Pattern 1] - could work for your [specific use case]
+- [Pattern 2] - might solve your [specific challenge]
+
+**Interaction Patterns:**
+
+- [Pattern 1] - excellent for [your user goal]
+- [Pattern 2] - addresses [your user pain point]
+
+**Visual Patterns:**
+
+- [Pattern 1] - supports your [emotional goal]
+- [Pattern 2] - aligns with your [platform requirements]
+
+Which of these patterns resonate most for your product?"
+
+### 4. Identify Anti-Patterns to Avoid
+
+Surface what not to do based on analysis:
+"**UX Anti-Patterns to Avoid:**
+From analyzing both successes and failures in your space, here are patterns to avoid:
+
+- [Anti-pattern 1] - users find this confusing/frustrating
+- [Anti-pattern 2] - this creates unnecessary friction
+- [Anti-pattern 3] - doesn't align with your [emotional goals]
+
+Learning from others' mistakes is as important as learning from their successes."
+
+### 5. Define Design Inspiration Strategy
+
+Create a clear strategy for using this inspiration:
+"**Design Inspiration Strategy:**
+
+**What to Adopt:**
+
+- [Specific pattern] - because it supports [your core experience]
+- [Specific pattern] - because it aligns with [user needs]
+
+**What to Adapt:**
+
+- [Specific pattern] - modify for [your unique requirements]
+- [Specific pattern] - simplify for [your user skill level]
+
+**What to Avoid:**
+
+- [Specific anti-pattern] - conflicts with [your goals]
+- [Specific anti-pattern] - doesn't fit [your platform]
+
+This strategy will guide our design decisions while keeping {{project_name}} unique."
+
+### 6. Generate Inspiration Analysis Content
+
+Prepare the content to append to the document:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## UX Pattern Analysis & Inspiration
+
+### Inspiring Products Analysis
+
+[Analysis of inspiring products based on conversation]
+
+### Transferable UX Patterns
+
+[Transferable patterns identified based on conversation]
+
+### Anti-Patterns to Avoid
+
+[Anti-patterns to avoid based on conversation]
+
+### Design Inspiration Strategy
+
+[Strategy for using inspiration based on conversation]
+```
+
+### 7. Present Content and Menu
+
+Show the generated inspiration analysis content and present choices:
+"I've analyzed inspiring UX patterns and products to inform our design strategy for {{project_name}}. This gives us a solid foundation of proven patterns to build upon.
+
+**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 deepen our UX pattern analysis
+[P] Party Mode - Bring different perspectives on inspiration sources
+[C] Continue - Save this to the document and move to design system choice"
+
+### 8. Handle Menu Selection
+
+#### If 'A' (Advanced Elicitation):
+
+- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current inspiration analysis content
+- Process the enhanced pattern insights that come back
+- Ask user: "Accept these improvements to the inspiration analysis? (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 {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current inspiration analysis
+- Process the collaborative pattern insights that come back
+- Ask user: "Accept these changes to the inspiration analysis? (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 `{output_folder}/ux-design-specification.md`
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
+- Load `./step-06-design-system.md`
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the document using the structure from step 6.
+
+## SUCCESS METRICS:
+
+✅ Inspiring products identified and analyzed thoroughly
+✅ UX patterns extracted and categorized effectively
+✅ Transferable patterns identified for current project
+✅ Anti-patterns identified to avoid common mistakes
+✅ Clear design inspiration strategy established
+✅ A/P/C menu presented and handled correctly
+✅ Content properly appended to document when C selected
+
+## FAILURE MODES:
+
+❌ Not getting specific examples of inspiring products
+❌ Surface-level analysis without deep pattern extraction
+❌ Missing opportunities for pattern adaptation
+❌ Not identifying relevant anti-patterns to avoid
+❌ Strategy too generic or not actionable
+❌ Not presenting A/P/C menu after content generation
+❌ Appending content without user selecting 'C'
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## NEXT STEP:
+
+After user selects 'C' and content is saved to document, load `./step-06-design-system.md` to choose the appropriate design system approach.
+
+Remember: Do NOT proceed to step-06 until user explicitly selects 'C' from the A/P/C menu and content is saved!

src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md

@@ -0,0 +1,251 @@
+# Step 6: Design System Choice
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder
+- 📋 YOU ARE A UX FACILITATOR, not a content generator
+- 💬 FOCUS on choosing appropriate design system approach
+- 🎯 COLLABORATIVE decision-making, not recommendation-only
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis before taking any action
+- ⚠️ Present A/P/C menu after generating design system decision content
+- 💾 ONLY save when user chooses C (Continue)
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6]` 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 design system insights
+- **P (Party Mode)**: Bring multiple perspectives to evaluate design system options
+- **C (Continue)**: Save the content to the document and proceed to next step
+
+## PROTOCOL INTEGRATION:
+
+- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- PROTOCOLS always return to this step's A/P/C menu
+- User accepts/rejects protocol changes before proceeding
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- Platform requirements from step 3 inform design system choice
+- Inspiration patterns from step 5 guide design system selection
+- Focus on choosing foundation for consistent design
+
+## YOUR TASK:
+
+Choose appropriate design system approach based on project requirements and constraints.
+
+## DESIGN SYSTEM CHOICE SEQUENCE:
+
+### 1. Present Design System Options
+
+Educate about design system approaches:
+"For {{project_name}}, we need to choose a design system foundation. Think of design systems like LEGO blocks for UI - they provide proven components and patterns, ensuring consistency and speeding development.
+
+**Design System Approaches:**
+
+**1. Custom Design System**
+
+- Complete visual uniqueness
+- Full control over every component
+- Higher initial investment
+- Perfect for established brands with unique needs
+
+**2. Established System (Material Design, Ant Design, etc.)**
+
+- Fast development with proven patterns
+- Great defaults and accessibility built-in
+- Less visual differentiation
+- Ideal for startups or internal tools
+
+**3. Themeable System (MUI, Chakra UI, Tailwind UI)**
+
+- Customizable with strong foundation
+- Brand flexibility with proven components
+- Moderate learning curve
+- Good balance of speed and uniqueness
+
+Which direction feels right for your project?"
+
+### 2. Analyze Project Requirements
+
+Guide decision based on project context:
+"**Let's consider your specific needs:**
+
+**Based on our previous conversations:**
+
+- Platform: [platform from step 3]
+- Timeline: [inferred from user conversation]
+- Team Size: [inferred from user conversation]
+- Brand Requirements: [inferred from user conversation]
+- Technical Constraints: [inferred from user conversation]
+
+**Decision Factors:**
+
+- Need for speed vs. need for uniqueness
+- Brand guidelines or existing visual identity
+- Team's design expertise
+- Long-term maintenance considerations
+- Integration requirements with existing systems"
+
+### 3. Explore Specific Design System Options
+
+Dive deeper into relevant options:
+"**Recommended Options Based on Your Needs:**
+
+**For [Your Platform Type]:**
+
+- [Option 1] - [Key benefit] - [Best for scenario]
+- [Option 2] - [Key benefit] - [Best for scenario]
+- [Option 3] - [Key benefit] - [Best for scenario]
+
+**Considerations:**
+
+- Component library size and quality
+- Documentation and community support
+- Customization capabilities
+- Accessibility compliance
+- Performance characteristics
+- Learning curve for your team"
+
+### 4. Facilitate Decision Process
+
+Help user make informed choice:
+"**Decision Framework:**
+
+1. What's most important: Speed, uniqueness, or balance?
+2. How much design expertise does your team have?
+3. Are there existing brand guidelines to follow?
+4. What's your timeline and budget?
+5. Long-term maintenance needs?
+
+Let's evaluate options based on your answers to these questions."
+
+### 5. Finalize Design System Choice
+
+Confirm and document the decision:
+"Based on our analysis, I recommend [Design System Choice] for {{project_name}}.
+
+**Rationale:**
+
+- [Reason 1 based on project needs]
+- [Reason 2 based on constraints]
+- [Reason 3 based on team considerations]
+
+**Next Steps:**
+
+- We'll customize this system to match your brand and needs
+- Define component strategy for custom components needed
+- Establish design tokens and patterns
+
+Does this design system choice feel right to you?"
+
+### 6. Generate Design System Content
+
+Prepare the content to append to the document:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Design System Foundation
+
+### 1.1 Design System Choice
+
+[Design system choice based on conversation]
+
+### Rationale for Selection
+
+[Rationale for design system selection based on conversation]
+
+### Implementation Approach
+
+[Implementation approach based on chosen system]
+
+### Customization Strategy
+
+[Customization strategy based on project needs]
+```
+
+### 7. Present Content and Menu
+
+Show the generated design system content and present choices:
+"I've documented our design system choice for {{project_name}}. This foundation will ensure consistency and speed up development.
+
+**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 refine our design system decision
+[P] Party Mode - Bring technical perspectives on design systems
+[C] Continue - Save this to the document and move to defining experience
+
+### 8. Handle Menu Selection
+
+#### If 'A' (Advanced Elicitation):
+
+- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current design system content
+- Process the enhanced design system insights that come back
+- Ask user: "Accept these improvements to the design system decision? (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 {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current design system choice
+- Process the collaborative design system insights that come back
+- Ask user: "Accept these changes to the design system decision? (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 `{output_folder}/ux-design-specification.md`
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6]`
+- Load `./step-07-defining-experience.md`
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the document using the structure from step 6.
+
+## SUCCESS METRICS:
+
+✅ Design system options clearly presented and explained
+✅ Decision framework applied to project requirements
+✅ Specific design system chosen with clear rationale
+✅ Implementation approach planned
+✅ Customization strategy defined
+✅ A/P/C menu presented and handled correctly
+✅ Content properly appended to document when C selected
+
+## FAILURE MODES:
+
+❌ Not explaining design system concepts clearly
+❌ Rushing to recommendation without understanding requirements
+❌ Not considering technical constraints or team capabilities
+❌ Choosing design system without clear rationale
+❌ Not planning implementation approach
+❌ Not presenting A/P/C menu after content generation
+❌ Appending content without user selecting 'C'
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## NEXT STEP:
+
+After user selects 'C' and content is saved to document, load `./step-07-defining-experience.md` to define the core user interaction.
+
+Remember: Do NOT proceed to step-07 until user explicitly selects 'C' from the A/P/C menu and content is saved!