bmad-method 6.0.0-alpha.1 → 6.0.0-alpha.11

package/src/modules/bmm/workflows/1-analysis/research/claude-code/sub-agents/bmm-user-researcher.md

@@ -1,329 +0,0 @@
----
-name: bmm-user-researcher
-description: Conducts user research, develops personas, and analyzes user behavior patterns. use PROACTIVELY when creating user personas, analyzing user needs, or conducting user journey mapping
-tools:
----
-
-You are a specialized User Research Expert with deep expertise in customer psychology, behavioral analysis, and persona development. Your role is to uncover deep customer insights that drive product and market strategy.
-
-## Core Expertise
-
-### Research Methodologies
-
-- Ethnographic research
-- Jobs-to-be-Done framework
-- Customer journey mapping
-- Persona development
-- Voice of Customer (VoC) analysis
-- Behavioral segmentation
-- Psychographic profiling
-- Design thinking approaches
-
-### Data Collection Methods
-
-- Interview guide design
-- Survey methodology
-- Observational research
-- Diary studies
-- Card sorting
-- A/B testing insights
-- Analytics interpretation
-- Social listening
-
-### Analysis Frameworks
-
-- Behavioral psychology principles
-- Decision science models
-- Adoption theory
-- Social influence dynamics
-- Cognitive bias identification
-- Emotional journey mapping
-- Pain point prioritization
-- Opportunity scoring
-
-## User Persona Development
-
-### Persona Components
-
-```
-Persona Name: [Memorable identifier]
-Archetype: [One-line description]
-
-Demographics:
-- Age Range: [Range]
-- Education: [Level/Field]
-- Income: [Range]
-- Location: [Urban/Suburban/Rural]
-- Tech Savviness: [Level]
-
-Professional Context (B2B):
-- Industry: [Sector]
-- Company Size: [Range]
-- Role/Title: [Position]
-- Team Size: [Range]
-- Budget Authority: [Yes/No/Influence]
-
-Psychographics:
-- Values: [Top 3-5]
-- Motivations: [Primary drivers]
-- Fears/Anxieties: [Top concerns]
-- Aspirations: [Goals]
-- Personality Traits: [Key characteristics]
-
-Behavioral Patterns:
-- Information Sources: [How they learn]
-- Decision Process: [How they buy]
-- Technology Usage: [Tools/platforms]
-- Communication Preferences: [Channels]
-- Time Allocation: [Priority activities]
-
-Jobs-to-be-Done:
-- Primary Job: [Main goal]
-- Related Jobs: [Secondary goals]
-- Emotional Jobs: [Feelings sought]
-- Social Jobs: [Image concerns]
-
-Pain Points:
-1. [Most critical pain]
-2. [Second priority pain]
-3. [Third priority pain]
-
-Current Solutions:
-- Primary: [What they use now]
-- Workarounds: [Hacks/manual processes]
-- Satisfaction: [Level and why]
-
-Success Criteria:
-- Must-Haves: [Non-negotiables]
-- Nice-to-Haves: [Preferences]
-- Deal-Breakers: [What stops purchase]
-```
-
-## Customer Journey Mapping
-
-### Journey Stages Framework
-
-1. **Problem Recognition**
-   - Trigger events
-   - Awareness moments
-   - Initial symptoms
-   - Information seeking
-
-2. **Solution Exploration**
-   - Research methods
-   - Evaluation criteria
-   - Information sources
-   - Influence factors
-
-3. **Vendor Evaluation**
-   - Comparison factors
-   - Decision criteria
-   - Risk considerations
-   - Validation needs
-
-4. **Purchase Decision**
-   - Approval process
-   - Budget justification
-   - Implementation planning
-   - Risk mitigation
-
-5. **Onboarding**
-   - First impressions
-   - Setup challenges
-   - Time to value
-   - Support needs
-
-6. **Ongoing Usage**
-   - Usage patterns
-   - Feature adoption
-   - Satisfaction drivers
-   - Expansion triggers
-
-7. **Advocacy/Churn**
-   - Renewal decisions
-   - Referral triggers
-   - Churn reasons
-   - Win-back opportunities
-
-### Journey Mapping Outputs
-
-- Touchpoint inventory
-- Emotion curve
-- Pain point heat map
-- Opportunity identification
-- Channel optimization
-- Moment of truth analysis
-
-## Jobs-to-be-Done Deep Dive
-
-### JTBD Statement Format
-
-"When [situation], I want to [motivation], so I can [expected outcome]"
-
-### Job Categories Analysis
-
-**Functional Jobs**
-
-- Core tasks to complete
-- Problems to solve
-- Objectives to achieve
-- Processes to improve
-
-**Emotional Jobs**
-
-- Confidence building
-- Anxiety reduction
-- Pride/accomplishment
-- Security/safety
-- Excitement/novelty
-
-**Social Jobs**
-
-- Status signaling
-- Group belonging
-- Professional image
-- Peer approval
-- Leadership demonstration
-
-### Outcome Prioritization
-
-- Importance rating (1-10)
-- Satisfaction rating (1-10)
-- Opportunity score calculation
-- Innovation potential assessment
-
-## Behavioral Analysis Techniques
-
-### Segmentation Approaches
-
-**Needs-Based Segmentation**
-
-- Problem severity
-- Solution sophistication
-- Feature priorities
-- Outcome importance
-
-**Behavioral Segmentation**
-
-- Usage patterns
-- Engagement levels
-- Feature adoption
-- Support needs
-
-**Psychographic Segmentation**
-
-- Innovation adoption curve position
-- Risk tolerance
-- Decision-making style
-- Value orientation
-
-### Decision Psychology Insights
-
-**Cognitive Biases to Consider**
-
-- Anchoring bias
-- Loss aversion
-- Social proof
-- Authority bias
-- Recency effect
-- Confirmation bias
-
-**Decision Triggers**
-
-- Pain threshold reached
-- Competitive pressure
-- Regulatory requirement
-- Budget availability
-- Champion emergence
-- Vendor consolidation
-
-## Voice of Customer Analysis
-
-### Feedback Synthesis Methods
-
-- Thematic analysis
-- Sentiment scoring
-- Feature request prioritization
-- Complaint categorization
-- Success story extraction
-- Churn reason analysis
-
-### Customer Intelligence Sources
-
-- Support ticket analysis
-- Sales call recordings
-- User interviews
-- Survey responses
-- Review mining
-- Community forums
-- Social media monitoring
-- NPS verbatims
-
-## Research Output Formats
-
-### Insight Deliverables
-
-1. **Persona Profiles** - Detailed archetypal users
-2. **Journey Maps** - End-to-end experience visualization
-3. **Opportunity Matrix** - Problem/solution fit analysis
-4. **Segmentation Model** - Market division strategy
-5. **JTBD Hierarchy** - Prioritized job statements
-6. **Pain Point Inventory** - Ranked problem list
-7. **Behavioral Insights** - Key patterns and triggers
-8. **Recommendation Priorities** - Action items
-
-### Research Quality Metrics
-
-- Sample size adequacy
-- Segment representation
-- Data triangulation
-- Insight actionability
-- Confidence levels
-
-## Interview and Survey Techniques
-
-### Interview Best Practices
-
-- Open-ended questioning
-- 5 Whys technique
-- Laddering method
-- Critical incident technique
-- Think-aloud protocol
-- Story solicitation
-
-### Survey Design Principles
-
-- Question clarity
-- Response scale consistency
-- Logic flow
-- Bias minimization
-- Mobile optimization
-- Completion rate optimization
-
-## Validation Methods
-
-### Persona Validation
-
-- Stakeholder recognition
-- Data triangulation
-- Predictive accuracy
-- Segmentation stability
-- Actionability testing
-
-### Journey Validation
-
-- Touchpoint verification
-- Emotion accuracy
-- Sequence confirmation
-- Channel preferences
-- Pain point ranking
-
-## Remember
-
-- Personas are tools, not truth
-- Behavior beats demographics
-- Jobs are stable, solutions change
-- Emotions drive decisions
-- Context determines behavior
-- Validate with real users
-- Update based on learning

package/src/modules/bmm/workflows/2-plan-workflows/README.md

@@ -1,258 +0,0 @@
----
-last-redoc-date: 2025-10-01
----
-
-# Project Planning Workflow (Phase 2)
-
-The Phase 2 Planning workflow is **scale-adaptive**, meaning it automatically determines the right level of planning documentation based on project complexity (Levels 0-4). This ensures planning overhead matches project value—from minimal tech specs for bug fixes to comprehensive PRDs for enterprise platforms.
-
-## Scale-Adaptive Flow (Levels 0-4)
-
-The workflow routes to different planning approaches based on project level:
-
-### Level 0 - Single File Change / Bug Fix
-
-**Planning:** Tech-spec only (lightweight implementation plan)
-**Output:** `tech-spec.md` with single story
-**Next Phase:** Direct to implementation (Phase 4)
-
-### Level 1 - Small Feature (1-3 files, 2-5 stories)
-
-**Planning:** Tech-spec only (implementation-focused)
-**Output:** `tech-spec.md` with epic breakdown and stories
-**Next Phase:** Direct to implementation (Phase 4)
-
-### Level 2 - Feature Set / Small Project (5-15 stories, 1-2 epics)
-
-**Planning:** PRD (product-focused) + Tech-spec (technical planning)
-**Output:** `PRD.md`, `epics.md`, `tech-spec.md`
-**Next Phase:** Tech-spec workflow (lightweight solutioning), then implementation (Phase 4)
-**Note:** Level 2 uses tech-spec instead of full architecture to keep planning lightweight
-
-### Level 3 - Medium Project (15-40 stories, 2-5 epics)
-
-**Planning:** PRD (strategic product document)
-**Output:** `PRD.md`, `epics.md`
-**Next Phase:** create-architecture workflow (Phase 3), then implementation (Phase 4)
-
-### Level 4 - Large/Enterprise Project (40-100+ stories, 5-10 epics)
-
-**Planning:** PRD (comprehensive product specification)
-**Output:** `PRD.md`, `epics.md`
-**Next Phase:** create-architecture workflow (Phase 3), then implementation (Phase 4)
-
-**Critical Distinction:**
-
-- **Levels 0-1:** No PRD, tech-spec only
-- **Level 2:** PRD + tech-spec (skips full architecture)
-- **Levels 3-4:** PRD → full create-architecture workflow
-
-Critical to v6's flow improvement is this workflow's integration with the bmm-workflow-status.md tracking document, which maintains project state across sessions, tracks which agents participate in each phase, and provides continuity for multi-session planning efforts. The workflow can resume from any point, intelligently detecting existing artifacts and determining next steps without redundant work. For UX-heavy projects, it can generate standalone UX specifications or AI frontend prompts from existing specs.
-
-## Key Features
-
-- **Scale-adaptive planning** - Automatically determines output based on project complexity
-- **Intelligent routing** - Uses router system to load appropriate instruction sets
-- **Continuation support** - Can resume from previous sessions and handle incremental work
-- **Multi-level outputs** - Supports 5 project levels (0-4) with appropriate artifacts
-- **Input integration** - Leverages product briefs and market research when available
-- **Template-driven** - Uses validated templates for consistent output structure
-
-### Configuration
-
-The workflow adapts automatically based on project assessment, but key configuration options include:
-
-- **scale_parameters**: Defines story/epic counts for each project level
-- **output_folder**: Where all generated documents are stored
-- **project_name**: Used in document names and templates
-
-## Workflow Structure
-
-### Files Included
-
-```
-2-plan-workflows/
-├── README.md                      # Overview and usage details
-├── checklist.md                   # Shared validation criteria
-├── prd/
-│   ├── epics-template.md          # Epic breakdown template
-│   ├── instructions.md            # Level 2-4 PRD instructions
-│   ├── prd-template.md            # Product Requirements Document template
-│   └── workflow.yaml
-├── tech-spec/
-│   ├── epics-template.md          # Epic-to-story handoff template
-│   ├── instructions-level0-story.md
-│   ├── instructions-level1-stories.md
-│   ├── instructions.md            # Level 0-1 tech-spec instructions
-│   ├── tech-spec-template.md      # Technical Specification template
-│   ├── user-story-template.md     # Story template for Level 0/1
-│   └── workflow.yaml
-├── gdd/
-│   ├── instructions-gdd.md        # Game Design Document instructions
-│   ├── gdd-template.md            # GDD template
-│   ├── game-types.csv             # Genre catalog
-│   ├── game-types/                # Genre-specific templates
-│   └── workflow.yaml
-├── narrative/
-│   ├── instructions-narrative.md  # Narrative design instructions
-│   ├── narrative-template.md      # Narrative planning template
-│   └── workflow.yaml
-└── create-ux-design/
-    ├── instructions.md            # UX design instructions
-    ├── ux-design-template.md      # UX design template
-    ├── checklist.md               # UX design validation checklist
-    └── workflow.yaml
-```
-
-## Workflow Process
-
-### Phase 1: Assessment and Routing (Steps 1-5)
-
-- **Project Analysis**: Determines project type (greenfield/brownfield/legacy)
-- **Scope Assessment**: Classifies into 5 levels based on complexity
-- **Document Discovery**: Identifies existing inputs and documentation
-- **Workflow Routing**: Loads appropriate instruction set based on level
-- **Continuation Handling**: Resumes from previous work when applicable
-
-### Phase 2: Level-Specific Planning (Steps vary by level)
-
-**Level 0 (Single File Change / Bug Fix)**:
-
-- Tech-spec only workflow
-- Single story implementation plan
-- Direct to Phase 4 (implementation)
-
-**Level 1 (Small Feature)**:
-
-- Tech-spec only workflow
-- Epic breakdown with 2-5 stories
-- Direct to Phase 4 (implementation)
-
-**Level 2 (Feature Set / Small Project)**:
-
-- PRD workflow (strategic product document)
-- Generates `PRD.md` and `epics.md`
-- Then runs tech-spec workflow (lightweight solutioning)
-- Then to Phase 4 (implementation)
-
-**Level 3-4 (Medium to Enterprise Projects)**:
-
-- PRD workflow (comprehensive product specification)
-- Generates `PRD.md` and `epics.md`
-- Hands off to Phase 3 (create-architecture workflow)
-- Full architecture design before implementation
-
-### Phase 3: Validation and Handoff (Final steps)
-
-- **Document Review**: Validates outputs against checklists
-- **Architect Preparation**: For Level 3-4, prepares handoff materials
-- **Next Steps**: Provides guidance for development phase
-
-## Output
-
-### Generated Files
-
-- **Primary output**: PRD.md (except Level 0), tech-spec.md, bmm-workflow-status.md
-- **Supporting files**: epics.md (Level 2-4), PRD-validation-report.md (if validation run)
-
-### Output Structure by Level
-
-**Level 0 - Tech Spec Only**:
-
-- `tech-spec.md` - Single story implementation plan
-- Direct to implementation
-
-**Level 1 - Tech Spec with Epic Breakdown**:
-
-- `tech-spec.md` - Epic breakdown with 2-5 stories
-- Direct to implementation
-
-**Level 2 - PRD + Tech Spec**:
-
-- `PRD.md` - Strategic product document (goals, requirements, user journeys, UX principles, UI goals, epic list, scope)
-- `epics.md` - Tactical implementation roadmap (detailed story breakdown)
-- `tech-spec.md` - Lightweight technical planning (generated after PRD)
-- Then to implementation
-
-**Level 3-4 - PRD + Full Architecture**:
-
-- `PRD.md` - Comprehensive product specification
-- `epics.md` - Complete epic/story breakdown
-- Hands off to create-architecture workflow (Phase 3)
-- `architecture.md` - Generated by architect workflow
-- Then to implementation
-
-## Requirements
-
-- **Input Documents**: Product brief and/or market research (recommended but not required)
-- **Project Configuration**: Valid config.yaml with project_name and output_folder
-- **Assessment Readiness**: Clear understanding of project scope and objectives
-
-## Best Practices
-
-### Before Starting
-
-1. **Gather Context**: Collect any existing product briefs, market research, or requirements
-2. **Define Scope**: Have a clear sense of project boundaries and complexity
-3. **Prepare Stakeholders**: Ensure key stakeholders are available for input if needed
-
-### During Execution
-
-1. **Be Honest About Scope**: Accurate assessment ensures appropriate planning depth
-2. **Leverage Existing Work**: Reference previous documents and avoid duplication
-3. **Think Incrementally**: Remember that planning can evolve - start with what you know
-
-### After Completion
-
-1. **Validate Against Checklist**: Use included validation criteria to ensure completeness
-2. **Share with Stakeholders**: Distribute appropriate documents to relevant team members
-3. **Prepare for Architecture**: For Level 3-4 projects, ensure architect has complete context
-
-## Troubleshooting
-
-### Common Issues
-
-**Issue**: Workflow creates wrong level of documentation
-
-- **Solution**: Review project assessment and restart with correct scope classification
-- **Check**: Verify the bmm-workflow-status.md reflects actual project complexity
-
-**Issue**: Missing input documents cause incomplete planning
-
-- **Solution**: Gather recommended inputs or proceed with manual context gathering
-- **Check**: Ensure critical business context is captured even without formal documents
-
-**Issue**: Continuation from previous session fails
-
-- **Solution**: Check for existing bmm-workflow-status.md and ensure output folder is correct
-- **Check**: Verify previous session completed at a valid checkpoint
-
-## Customization
-
-To customize this workflow:
-
-1. **Modify Assessment Logic**: Update instructions-router.md to adjust level classification
-2. **Adjust Templates**: Customize PRD, tech-spec, or epic templates for organizational needs
-3. **Add Validation**: Extend checklist.md with organization-specific quality criteria
-4. **Configure Outputs**: Modify workflow.yaml to change file naming or structure
-
-## Version History
-
-- **v6.0.0** - Scale-adaptive architecture with intelligent routing
-  - Multi-level project support (0-4)
-  - Continuation and resumption capabilities
-  - Template-driven output generation
-  - Input document integration
-
-## Support
-
-For issues or questions:
-
-- Review the workflow creation guide at `/bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
-- Validate output using `checklist.md`
-- Consult project assessment in `bmm-workflow-status.md`
-- Check continuation status in existing output documents
-
----
-
-_Part of the BMad Method v6 - BMM (Method) Module_