bmad-method 6.0.0-alpha.3 → 6.0.0-alpha.5

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

@@ -2,40 +2,60 @@
 
 <critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
-<critical>This is an INTERACTIVE workflow with web research capabilities. Engage the user at key decision points.</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>
 
 <!-- IDE-INJECT-POINT: market-research-subagents -->
 
 <workflow>
 
-<step n="1" goal="Research Discovery and Scoping">
-<action>Welcome the user and explain the market research journey ahead</action>
+<step n="1" goal="Discover research needs and scope collaboratively">
 
-Ask the user these critical questions to shape the research:
+<action>Welcome {user_name} warmly. Position yourself as their collaborative research partner who will:
 
-1. **What is the product/service you're researching?**
-   - Name and brief description
-   - Current stage (idea, MVP, launched, scaling)
+- Gather live {{current_year}} market data
+- Share findings progressively throughout
+- Help make sense of what we discover together
 
-2. **What are your primary research objectives?**
-   - Market sizing and opportunity assessment?
-   - Competitive intelligence gathering?
-   - Customer segment validation?
-   - Go-to-market strategy development?
-   - Investment/fundraising support?
-   - Product-market fit validation?
+Ask what they're building and what market questions they need answered.
+</action>
 
-3. **Research depth preference:**
-   - Quick scan (2-3 hours) - High-level insights
-   - Standard analysis (4-6 hours) - Comprehensive coverage
-   - Deep dive (8+ hours) - Exhaustive research with modeling
+<action>Through natural conversation, discover:
 
-4. **Do you have any existing research or documents to build upon?**
+- 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_depth</template-output>
+<template-output>research_scope</template-output>
 </step>
 
 <step n="2" goal="Market Definition and Boundaries">
@@ -65,49 +85,64 @@ Work with the user to establish:
 <template-output>segment_boundaries</template-output>
 </step>
 
-<step n="3" goal="Live Market Intelligence Gathering" if="enable_web_research == true">
-<action>Conduct real-time web research to gather current market data</action>
+<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>
 
-<critical>This step performs ACTUAL web searches to gather live market intelligence</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>
 
-Conduct systematic research across multiple sources:
+<step n="3a" title="Search for market size and industry data">
+<action>Conduct systematic web searches using WebSearch tool:
 
-<step n="3a" title="Industry Reports and Statistics">
-<action>Search for latest industry reports, market size data, and growth projections</action>
-Search queries to execute:
-- "[market_category] market size [geographic_scope] [current_year]"
-- "[market_category] industry report Gartner Forrester IDC McKinsey"
-- "[market_category] market growth rate CAGR forecast"
-- "[market_category] market trends [current_year]"
+<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>
 
 <invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
-</step>
 
-<step n="3b" title="Regulatory and Government Data">
-<action>Search government databases and regulatory sources</action>
-Search for:
-- Government statistics bureaus
-- Industry associations
-- Regulatory body reports
-- Census and economic data
+<template-output>sources_market_size</template-output>
 </step>
 
-<step n="3c" title="News and Recent Developments">
-<action>Gather recent news, funding announcements, and market events</action>
-Search for articles from the last 6-12 months about:
-- Major deals and acquisitions
-- Funding rounds in the space
-- New market entrants
-- Regulatory changes
-- Technology disruptions
+<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="3d" title="Academic and Research Papers">
-<action>Search for academic research and white papers</action>
-Look for peer-reviewed studies on:
-- Market dynamics
-- Technology adoption patterns
-- Customer behavior research
+<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>
@@ -250,38 +285,36 @@ Analyze:
 </step>
 </step>
 
-<step n="6" goal="Competitive Intelligence" if="enable_competitor_analysis == true">
-<action>Conduct comprehensive competitive analysis</action>
+<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="Competitor Identification">
-<action>Create comprehensive competitor list</action>
+<step n="6a" title="Discover competitors together">
+<action if="user doesn't know competitors">Search for competitors:
 
-Search for and categorize:
+<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>
 
-1. **Direct Competitors** - Same solution, same market
-2. **Indirect Competitors** - Different solution, same problem
-3. **Potential Competitors** - Could enter market
-4. **Substitute Products** - Alternative approaches
-
-<ask>Do you have a specific list of competitors to analyze, or should I discover them through research?</ask>
+<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="Competitor Deep Dive" repeat="5">
-<action>For top 5 competitors, research and analyze</action>
+<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>
 
-Gather intelligence on:
+<action>Share findings with sources. Ask what jumps out and if it matches expectations.</action>
 
-- Company overview and history
-- Product features and positioning
-- Pricing strategy and models
-- Target customer focus
-- Recent news and developments
-- Funding and financial health
-- Team and leadership
-- Customer reviews and sentiment
+<action if="user has follow-up questions">Dig deeper based on their interests</action>
 
 <invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
-<template-output>competitor*analysis*{{competitor_number}}</template-output>
+<template-output>competitor*analysis*{{competitor_name}}</template-output>
 </step>
 
 <step n="6c" title="Competitive Positioning Map">
@@ -485,55 +518,99 @@ Provide mitigation strategies.
 
 </step>
 
-<step n="11" goal="Executive Summary Creation">
-<action>Synthesize all findings into executive summary</action>
+<step n="11" goal="Synthesize findings together into executive summary">
 
-<critical>Write this AFTER all other sections are complete</critical>
+<critical>This is the last major content section - make it collaborative</critical>
 
-Create compelling executive summary with:
+<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>
 
-**Market Opportunity:**
+<action>Collaboratively craft the narrative:
 
-- TAM/SAM/SOM summary
-- Growth trajectory
+- What's the headline? (The ONE thing someone should know)
+- What are the 3-5 critical insights?
+- Recommended path forward?
+- Key risks?
 
-**Key Insights:**
+This should read like a strategic brief, not a data dump.
+</action>
 
-- Top 3-5 findings
-- Surprising discoveries
-- Critical success factors
+<action>Draft executive summary and share. Ask if it captures the essence and if anything is missing or overemphasized.</action>
 
-**Competitive Landscape:**
+<template-output>executive_summary</template-output>
+</step>
 
-- Market structure
-- Positioning opportunity
+<step n="12" goal="Validate sources and compile report">
 
-**Strategic Recommendations:**
+<critical>MANDATORY SOURCE VALIDATION - Do NOT skip this step!</critical>
 
-- Priority actions
-- Go-to-market approach
-- Investment requirements
+<action>Before finalizing, conduct source audit:
 
-**Risk Summary:**
+Review every major claim in the report and verify:
 
-- Major risks
-- Mitigation approach
+**For Market Size Claims:**
 
-<template-output>executive_summary</template-output>
-</step>
+- [ ] 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:
 
-<step n="12" goal="Report Compilation and Review">
-<action>Compile full report and review with user</action>
+- {{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
 
-<action>Generate the complete market research report using the template</action>
-<action>Review all sections for completeness and consistency</action>
-<action>Ensure all data sources are properly cited</action>
+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">

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

@@ -2,7 +2,17 @@
 
 <critical>The workflow execution engine is governed by: {project_root}/bmad/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>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>
 
 <!-- IDE-INJECT-POINT: research-subagents -->
 
@@ -49,43 +59,25 @@
 </check>
 </step>
 
-<step n="2" goal="Welcome and Research Type Selection">
-<action>Welcome the user to the Research Workflow</action>
+<step n="2" goal="Discover research needs through conversation">
 
-**The Research Workflow supports multiple research types:**
+<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>
 
-Present the user with research type options:
+<action>Listen and collaboratively identify the research type based on what they describe:
 
-**What type of research do you need?**
+- 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
 
-1. **Market Research** - Comprehensive market analysis with TAM/SAM/SOM calculations, competitive intelligence, customer segments, and go-to-market strategy
-   - Use for: Market opportunity assessment, competitive landscape analysis, market sizing
-   - Output: Detailed market research report with financials
+Confirm your understanding of what type would be most helpful and what it will produce.
+</action>
 
-2. **Deep Research Prompt Generator** - Create structured, multi-step research prompts optimized for AI platforms (ChatGPT, Gemini, Grok, Claude)
-   - Use for: Generating comprehensive research prompts, structuring complex investigations
-   - Output: Optimized research prompt with framework, scope, and validation criteria
-
-3. **Technical/Architecture Research** - Evaluate technology stacks, architecture patterns, frameworks, and technical approaches
-   - Use for: Tech stack decisions, architecture pattern selection, framework evaluation
-   - Output: Technical research report with recommendations and trade-off analysis
-
-4. **Competitive Intelligence** - Deep dive into specific competitors, their strategies, products, and market positioning
-   - Use for: Competitor deep dives, competitive strategy analysis
-   - Output: Competitive intelligence report
-
-5. **User Research** - Customer insights, personas, jobs-to-be-done, and user behavior analysis
-   - Use for: Customer discovery, persona development, user journey mapping
-   - Output: User research report with personas and insights
-
-6. **Domain/Industry Research** - Deep dive into specific industries, domains, or subject matter areas
-   - Use for: Industry analysis, domain expertise building, trend analysis
-   - Output: Domain research report
-
-<ask>Select a research type (1-6) or describe your research needs:</ask>
-
-<action>Capture user selection as {{research_type}}</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">

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

@@ -2,38 +2,65 @@
 
 <critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
-<critical>This workflow conducts technical research for architecture and technology decisions</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>
 
 <workflow>
 
-<step n="1" goal="Technical Research Discovery">
-<action>Understand the technical research requirements</action>
+<step n="1" goal="Discover technical research needs through conversation">
 
-**Welcome to Technical/Architecture Research!**
+<action>Engage conversationally based on skill level:
 
-<ask>What technical decision or research do you need?
+<check if="{user_skill_level} == 'expert'">
+  "Let's research the technical options for your decision.
 
-Common scenarios:
+I'll gather current data from {{current_year}}, compare approaches, and help you think through trade-offs.
 
-- Evaluate technology stack for a new project
-- Compare frameworks or libraries (React vs Vue, Postgres vs MongoDB)
-- Research architecture patterns (microservices, event-driven, CQRS)
-- Investigate specific technologies or tools
-- Best practices for specific use cases
-- Performance and scalability considerations
-- Security and compliance research</ask>
+What technical question are you wrestling with?"
+</check>
 
-<template-output>technical_question</template-output>
+<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.
 
-<ask>What's the context for this decision?
+I'll explain what different technologies do, why you might choose one over another, and help you make an informed decision.
 
-- New greenfield project
-- Adding to existing system (brownfield)
-- Refactoring/modernizing legacy system
-- Proof of concept / prototype
-- Production-ready implementation
-- Academic/learning purpose</ask>
+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>
@@ -82,49 +109,70 @@ Consider:
 
 </step>
 
-<step n="3" goal="Identify Alternatives and Options">
-<action>Research and identify technology options to evaluate</action>
+<step n="3" goal="Discover and evaluate technology options together">
 
-<ask>Do you have specific technologies in mind to compare, or should I discover options?
+<critical>MUST use WebSearch to find current options from {{current_year}}</critical>
 
-If you have specific options, list them. Otherwise, I'll research current leading solutions based on your requirements.</ask>
+<action>Ask if they have candidates in mind:
 
-<template-output if="user provides options">user_provided_options</template-output>
+"Do you already have specific technologies you want to compare, or should I search for the current options?"
+</action>
 
-<check if="discovering options">
-  <action>Conduct web research to identify current leading solutions</action>
-  <action>Search for:
+<action if="user has candidates">Great! Let's research: {{user_candidates}}</action>
 
-- "[technical_category] best tools 2025"
-- "[technical_category] comparison [use_case]"
-- "[technical_category] production experiences reddit"
-- "State of [technical_category] 2025"
-  </action>
+<action if="discovering options">Search for current leading technologies:
 
-  <invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<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>Present discovered options (typically 3-5 main candidates)</action>
-<template-output>technology_options</template-output>
+<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>
+
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+
+<template-output>technology_options</template-output>
 
 </step>
 
-<step n="4" goal="Deep Dive Research on Each Option">
-<action>Research each technology option in depth</action>
+<step n="4" goal="Research each technology together in depth">
 
-<critical>For each technology option, research thoroughly</critical>
+<critical>For each option, use WebSearch to gather CURRENT {{current_year}} information</critical>
 
-<step n="4a" title="Technology Profile" repeat="for-each-option">
+<step n="4a" title="Deep dive on each technology" repeat="for-each-option">
 
-Research and document:
+<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}}
 
-- What is it and what problem does it solve?
-- Maturity level (experimental, stable, mature, legacy)
-- Community size and activity
-- Maintenance status and release cadence
+**Current Status ({{current_year}}):**
+{{maturity_community_release_cadence}}
 
 **Technical Characteristics:**