bmalph 1.0.0 → 2.2.1

package/bmad/bmm/workflows/1-analysis/research/market-steps/step-02-customer-insights.md

@@ -1,200 +0,0 @@
-# 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
-- ✅ Search the web to verify and supplement your knowledge with current facts
-- 📋 YOU ARE A CUSTOMER INSIGHTS ANALYST, not content generator
-- 💬 FOCUS on customer behavior and needs analysis
-- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-## 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 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** 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:**
-
-Search the web: "[product/service/market] customer behavior patterns"
-Search the web: "[product/service/market] customer pain points challenges"
-Search the web: "[product/service/market] customer decision process"
-
-**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]_
-
-### Pain Points and Challenges
-
-[Pain points analysis with source citations]
-_Source: [URL]_
-
-### Decision-Making Processes
-
-[Decision-making analysis with source citations]
-_Source: [URL]_
-
-### Customer Journey Mapping
-
-[Customer journey analysis with source citations]
-_Source: [URL]_
-
-### Customer Satisfaction Drivers
-
-[Satisfaction drivers analysis with source citations]
-_Source: [URL]_
-
-### Demographic Profiles
-
-[Demographic profiles analysis with source citations]
-_Source: [URL]_
-
-### Psychographic Profiles
-
-[Psychographic profiles analysis with source citations]
-_Source: [URL]_
-```
-
-### 5. Present Analysis and Continue Option
-
-Show the generated customer insights and present continue option:
-"I've completed the **customer insights analysis** for 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-05-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 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:
-
-❌ Relying solely on training data without web verification for current facts
-
-❌ 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-05-competitive-analysis.md` to focus on competitive landscape analysis.
-
-Remember: Always emphasize current customer data and rigorous source verification!

package/bmad/bmm/workflows/1-analysis/research/workflow.md

@@ -1,173 +0,0 @@
----
-name: research
-description: Conduct comprehensive research across multiple domains using current web data and verified sources - Market, Technical, Domain and other research types.
-web_bundle: true
----
-
-# 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 backed by web sources with URL citations
-- **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 output frontmatter
-
-## INITIALIZATION
-
-### Configuration Loading
-
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
-
-- `project_name`, `output_folder`, , `planning_artifacts`, `user_name`
-- `communication_language`, `document_output_language`, `user_skill_level`
-- `date` as a system-generated value
-
-### Paths
-
-- `installed_path` = `{project-root}/_bmad/bmm/workflows/1-analysis/research`
-- `template_path` = `{installed_path}/research.template.md`
-- `default_output_file` = `{planning_artifacts}/research/{{research_type}}-{{topic}}-research-{{date}}.md` (dynamic based on research type)
-
-## PREREQUISITE
-
-**⛔ Web search required.** If unavailable, abort and tell the user.
-
-## RESEARCH BEHAVIOR
-
-### Web Research Standards
-
-- **Current Data Only**: Search the web to verify and supplement your knowledge with current facts
-- **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
-
-## Implementation Instructions
-
-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**: Search the web to verify and supplement your knowledge with current facts
-- **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 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
-
-<critical>Based on user selection, route to appropriate sub-workflow with the discovered topic using the following IF block sets of instructions. YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`</critical>
-
-#### If Market Research:
-
-- Set `research_type = "market"`
-- Set `research_topic = [discovered topic from discussion]`
-- Create the starter output file: `{planning_artifacts}/research/market-{{research_topic}}-research-{{date}}.md` with exact copy of the ./research.template.md contents
-- Load: `./market-steps/step-01-init.md` with topic context
-
-#### If Domain Research:
-
-- Set `research_type = "domain"`
-- Set `research_topic = [discovered topic from discussion]`
-- Create the starter output file: `{planning_artifacts}/research/domain-{{research_topic}}-research-{{date}}.md` with exact copy of the ./research.template.md contents
-- Load: `./domain-steps/step-01-init.md` with topic context
-
-#### If Technical Research:
-
-- Set `research_type = "technical"`
-- Set `research_topic = [discovered topic from discussion]`
-- Create the starter output file: `{planning_artifacts}/research/technical-{{research_topic}}-research-{{date}}.md` with exact copy of the ./research.template.md contents
-- 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.
-
-**Note:** All research workflows require web search for current data and source verification.