bmad初始化
This commit is contained in:
38
bmad/bmm/workflows/1-analysis/brainstorm-game/README.md
Normal file
38
bmad/bmm/workflows/1-analysis/brainstorm-game/README.md
Normal file
@@ -0,0 +1,38 @@
|
||||
---
|
||||
last-redoc-date: 2025-10-01
|
||||
---
|
||||
|
||||
# Game Brainstorming Workflow
|
||||
|
||||
This workflow employs structured ideation methodologies to generate and refine game concepts through systematic creative exploration. It leverages five distinct brainstorming techniques—SCAMPER, Mind Mapping, Lotus Blossom, Six Thinking Hats, and Random Word Association—each applied in isolation to produce diverse conceptual approaches. The workflow emphasizes iterative refinement where initial concepts are evaluated against design pillars, technical feasibility, and market positioning to identify the most promising directions.
|
||||
|
||||
The system operates through a game-specific context framework that considers platform constraints, target audience characteristics, monetization models, and core gameplay pillars. Each brainstorming method generates distinct artifacts: SCAMPER produces systematic modification analyses, Mind Mapping reveals conceptual hierarchies, Lotus Blossom creates radial expansion patterns, Six Thinking Hats enforces multi-perspective evaluation, and Random Word Association drives lateral thinking breakthroughs. The workflow culminates in a consolidated concept document that synthesizes the strongest elements from each method into cohesive game proposals.
|
||||
|
||||
Critical to this workflow is its emphasis on constraint-driven creativity. The game-context.md framework establishes technical boundaries (platform capabilities, performance targets), market parameters (genre conventions, competitive positioning), and design philosophy (accessibility requirements, monetization ethics) that ground creative exploration in practical realities. This prevents ideation from drifting into infeasible territory while maintaining creative ambition.
|
||||
|
||||
## Usage
|
||||
|
||||
```bash
|
||||
bmad bmm 1-analysis brainstorm-game
|
||||
```
|
||||
|
||||
## Inputs
|
||||
|
||||
- **Game Context Document**: Platform specifications, genre preferences, technical constraints, target audience demographics, monetization approach, and core design pillars
|
||||
- **Initial Concept Seed** (optional): High-level game idea or theme to guide brainstorming direction
|
||||
|
||||
## Outputs
|
||||
|
||||
- **Method-Specific Artifacts**: Five separate brainstorming documents, each applying a different ideation methodology to the concept space
|
||||
- **Consolidated Concept Document**: Synthesized game concepts with feasibility assessments, unique value propositions, and recommended next steps
|
||||
- **Design Pillar Alignment Matrix**: Evaluation of each concept against stated design objectives and technical constraints
|
||||
|
||||
## Brainstorming Methods
|
||||
|
||||
| Method | Focus | Output Characteristics |
|
||||
| ----------------------- | ------------------------ | ---------------------------------- |
|
||||
| SCAMPER | Systematic modification | Structured transformation analysis |
|
||||
| Mind Mapping | Hierarchical exploration | Visual concept relationships |
|
||||
| Lotus Blossom | Radial expansion | Layered thematic development |
|
||||
| Six Thinking Hats | Multi-perspective | Balanced evaluation framework |
|
||||
| Random Word Association | Lateral thinking | Unexpected conceptual combinations |
|
||||
@@ -0,0 +1,26 @@
|
||||
category,technique_name,description,facilitation_prompts,best_for,energy_level,typical_duration
|
||||
game_design,MDA Framework Exploration,Explore game concepts through Mechanics-Dynamics-Aesthetics lens to ensure cohesive design from implementation to player experience,What mechanics create the core loop?|What dynamics emerge from these mechanics?|What aesthetic experience results?|How do they align?,holistic-design,moderate,20-30
|
||||
game_design,Core Loop Brainstorming,Design the fundamental moment-to-moment gameplay loop that players repeat - the heartbeat of your game,What does the player do?|What's the immediate reward?|Why do it again?|How does it evolve?,gameplay-foundation,high,15-25
|
||||
game_design,Player Fantasy Mining,Identify and amplify the core fantasy that players want to embody - what makes them feel powerful and engaged,What fantasy does the player live?|What makes them feel awesome?|What power do they wield?|What identity do they assume?,player-motivation,high,15-20
|
||||
game_design,Genre Mashup,Combine unexpected game genres to create innovative hybrid experiences that offer fresh gameplay,Take two unrelated genres|How do they merge?|What unique gameplay emerges?|What's the hook?,innovation,high,15-20
|
||||
game_design,Verbs Before Nouns,Focus on what players DO before what things ARE - prioritize actions over objects for engaging gameplay,What verbs define your game?|What actions feel good?|Build mechanics from verbs|Nouns support actions,mechanics-first,moderate,20-25
|
||||
game_design,Failure State Design,Work backwards from interesting failure conditions to create tension and meaningful choices,How can players fail interestingly?|What makes failure feel fair?|How does failure teach?|Recovery mechanics?,challenge-design,moderate,15-20
|
||||
game_design,Progression Curve Sculpting,Map the player's emotional and skill journey from tutorial to mastery - pace challenge and revelation,How does difficulty evolve?|When do we introduce concepts?|What's the skill ceiling?|How do we maintain flow?,pacing-balance,moderate,25-30
|
||||
game_design,Emergence Engineering,Design simple rule interactions that create complex unexpected player-driven outcomes,What simple rules combine?|What emerges from interactions?|How do players surprise you?|Systemic possibilities?,depth-complexity,moderate,20-25
|
||||
game_design,Accessibility Layers,Brainstorm how different skill levels and abilities can access your core experience meaningfully,Who might struggle with what?|What alternate inputs exist?|How do we preserve challenge?|Inclusive design options?,inclusive-design,moderate,20-25
|
||||
game_design,Reward Schedule Architecture,Design the timing and type of rewards to maintain player motivation and engagement,What rewards when?|Variable or fixed schedule?|Intrinsic vs extrinsic rewards?|Progression satisfaction?,engagement-retention,moderate,20-30
|
||||
narrative_game,Ludonarrative Harmony,Align story and gameplay so mechanics reinforce narrative themes - make meaning through play,What does gameplay express?|How do mechanics tell story?|Where do they conflict?|How to unify theme?,storytelling,moderate,20-25
|
||||
narrative_game,Environmental Storytelling,Use world design and ambient details to convey narrative without explicit exposition,What does the space communicate?|What happened here before?|Visual narrative clues?|Show don't tell?,world-building,moderate,15-20
|
||||
narrative_game,Player Agency Moments,Identify key decision points where player choice shapes narrative in meaningful ways,What choices matter?|How do consequences manifest?|Branch vs flavor choices?|Meaningful agency where?,player-choice,moderate,20-25
|
||||
narrative_game,Emotion Targeting,Design specific moments intended to evoke targeted emotional responses through integrated design,What emotion when?|How do all elements combine?|Music + mechanics + narrative?|Orchestrated feelings?,emotional-design,high,20-30
|
||||
systems_game,Economy Balancing Thought Experiments,Explore resource generation/consumption balance to prevent game-breaking exploits,What resources exist?|Generation vs consumption rates?|What loops emerge?|Where's the exploit?,economy-design,moderate,25-30
|
||||
systems_game,Meta-Game Layer Design,Brainstorm progression systems that persist beyond individual play sessions,What carries over between sessions?|Long-term goals?|How does meta feed core loop?|Retention hooks?,retention-systems,moderate,20-25
|
||||
multiplayer_game,Social Dynamics Mapping,Anticipate how players will interact and design mechanics that support desired social behaviors,How will players cooperate?|Competitive dynamics?|Toxic behavior prevention?|Positive interaction rewards?,social-design,moderate,20-30
|
||||
multiplayer_game,Spectator Experience Design,Consider how watching others play can be entertaining - esports and streaming potential,What's fun to watch?|Readable visual clarity?|Highlight moments?|Narrative for observers?,spectator-value,moderate,15-20
|
||||
creative_game,Constraint-Based Creativity,Embrace a specific limitation as your core design constraint and build everything around it,Pick a severe constraint|What if this was your ONLY mechanic?|Build a full game from limitation|Constraint as creativity catalyst,innovation,moderate,15-25
|
||||
creative_game,Game Feel Playground,Focus purely on how controls and feedback FEEL before worrying about context or goals,What feels juicy to do?|Controller response?|Visual/audio feedback?|Satisfying micro-interactions?,game-feel,high,20-30
|
||||
creative_game,One Button Game Challenge,Design interesting gameplay using only a single input - forces elegant simplicity,Only one button - what can it do?|Context changes meaning?|Timing variations?|Depth from simplicity?,minimalist-design,moderate,15-20
|
||||
wild_game,Remix an Existing Game,Take a well-known game and twist one core element - what new experience emerges?,Pick a famous game|Change ONE fundamental rule|What ripples from that change?|New game from mutation?,rapid-prototyping,high,10-15
|
||||
wild_game,Anti-Game Design,Design a game that deliberately breaks common conventions - subvert player expectations,What if we broke this rule?|Expectation subversion?|Anti-patterns as features?|Avant-garde possibilities?,experimental,moderate,15-20
|
||||
wild_game,Physics Playground,Start with an interesting physics interaction and build a game around that sensation,What physics are fun to play with?|Build game from physics toy|Emergent physics gameplay?|Sensation first?,prototype-first,high,15-25
|
||||
wild_game,Toy Before Game,Create a playful interactive toy with no goals first - then discover the game within it,What's fun to mess with?|No goals yet - just play|What game emerges organically?|Toy to game evolution?,discovery-design,high,20-30
|
||||
|
115
bmad/bmm/workflows/1-analysis/brainstorm-game/game-context.md
Normal file
115
bmad/bmm/workflows/1-analysis/brainstorm-game/game-context.md
Normal file
@@ -0,0 +1,115 @@
|
||||
# Game Brainstorming Context
|
||||
|
||||
This context guide provides game-specific considerations for brainstorming sessions focused on game design and development.
|
||||
|
||||
## Session Focus Areas
|
||||
|
||||
When brainstorming for games, consider exploring:
|
||||
|
||||
- **Core Gameplay Loop** - What players do moment-to-moment
|
||||
- **Player Fantasy** - What identity/power fantasy does the game fulfill?
|
||||
- **Game Mechanics** - Rules and interactions that define play
|
||||
- **Game Dynamics** - Emergent behaviors from mechanic interactions
|
||||
- **Aesthetic Experience** - Emotional responses and feelings evoked
|
||||
- **Progression Systems** - How players grow and unlock content
|
||||
- **Challenge and Difficulty** - How to create engaging difficulty curves
|
||||
- **Social/Multiplayer Features** - How players interact with each other
|
||||
- **Narrative and World** - Story, setting, and environmental storytelling
|
||||
- **Art Direction and Feel** - Visual style and game feel
|
||||
- **Monetization** - Business model and revenue approach (if applicable)
|
||||
|
||||
## Game Design Frameworks
|
||||
|
||||
### MDA Framework
|
||||
|
||||
- **Mechanics** - Rules and systems (what's in the code)
|
||||
- **Dynamics** - Runtime behavior (how mechanics interact)
|
||||
- **Aesthetics** - Emotional responses (what players feel)
|
||||
|
||||
### Player Motivation (Bartle's Taxonomy)
|
||||
|
||||
- **Achievers** - Goal completion and progression
|
||||
- **Explorers** - Discovery and understanding systems
|
||||
- **Socializers** - Interaction and relationships
|
||||
- **Killers** - Competition and dominance
|
||||
|
||||
### Core Experience Questions
|
||||
|
||||
- What does the player DO? (Verbs first, nouns second)
|
||||
- What makes them feel powerful/competent/awesome?
|
||||
- What's the central tension or challenge?
|
||||
- What's the "one more turn" factor?
|
||||
|
||||
## Recommended Brainstorming Techniques
|
||||
|
||||
### Game Design Specific Techniques
|
||||
|
||||
(These are available as additional techniques in game brainstorming sessions)
|
||||
|
||||
- **MDA Framework Exploration** - Design through mechanics-dynamics-aesthetics
|
||||
- **Core Loop Brainstorming** - Define the heartbeat of gameplay
|
||||
- **Player Fantasy Mining** - Identify and amplify player power fantasies
|
||||
- **Genre Mashup** - Combine unexpected genres for innovation
|
||||
- **Verbs Before Nouns** - Focus on actions before objects
|
||||
- **Failure State Design** - Work backwards from interesting failures
|
||||
- **Ludonarrative Harmony** - Align story and gameplay
|
||||
- **Game Feel Playground** - Focus purely on how controls feel
|
||||
|
||||
### Standard Techniques Well-Suited for Games
|
||||
|
||||
- **SCAMPER Method** - Innovate on existing game mechanics
|
||||
- **What If Scenarios** - Explore radical gameplay possibilities
|
||||
- **First Principles Thinking** - Rebuild game concepts from scratch
|
||||
- **Role Playing** - Generate ideas from player perspectives
|
||||
- **Analogical Thinking** - Find inspiration from other games/media
|
||||
- **Constraint-Based Creativity** - Design around limitations
|
||||
- **Morphological Analysis** - Explore mechanic combinations
|
||||
|
||||
## Output Guidance
|
||||
|
||||
Effective game brainstorming sessions should capture:
|
||||
|
||||
1. **Core Concept** - High-level game vision and hook
|
||||
2. **Key Mechanics** - Primary gameplay verbs and interactions
|
||||
3. **Player Experience** - What it feels like to play
|
||||
4. **Unique Elements** - What makes this game special/different
|
||||
5. **Design Challenges** - Obstacles to solve during development
|
||||
6. **Prototype Ideas** - What to test first
|
||||
7. **Reference Games** - Existing games that inspire or inform
|
||||
8. **Open Questions** - What needs further exploration
|
||||
|
||||
## Integration with Game Development Workflow
|
||||
|
||||
Game brainstorming sessions typically feed into:
|
||||
|
||||
- **Game Briefs** - High-level vision and core pillars
|
||||
- **Game Design Documents (GDD)** - Comprehensive design specifications
|
||||
- **Technical Design Docs** - Architecture for game systems
|
||||
- **Prototype Plans** - What to build to validate concepts
|
||||
- **Art Direction Documents** - Visual style and feel guides
|
||||
|
||||
## Special Considerations for Game Design
|
||||
|
||||
### Start With The Feel
|
||||
|
||||
- How should controls feel? Responsive? Weighty? Floaty?
|
||||
- What's the "game feel" - the juice and feedback?
|
||||
- Can we prototype the core interaction quickly?
|
||||
|
||||
### Think in Systems
|
||||
|
||||
- How do mechanics interact?
|
||||
- What emergent behaviors arise?
|
||||
- Are there dominant strategies or exploits?
|
||||
|
||||
### Design for Failure
|
||||
|
||||
- How do players fail?
|
||||
- Is failure interesting and instructive?
|
||||
- What's the cost of failure?
|
||||
|
||||
### Player Agency vs. Authored Experience
|
||||
|
||||
- Where do players have meaningful choices?
|
||||
- Where is the experience authored/scripted?
|
||||
- How do we balance freedom and guidance?
|
||||
128
bmad/bmm/workflows/1-analysis/brainstorm-game/instructions.md
Normal file
128
bmad/bmm/workflows/1-analysis/brainstorm-game/instructions.md
Normal file
@@ -0,0 +1,128 @@
|
||||
<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>This is a meta-workflow that orchestrates the CIS brainstorming workflow with game-specific context and additional game design techniques</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. Game 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-game" workflow</action>
|
||||
<action>Get project_level from YAML metadata</action>
|
||||
<action>Find first non-completed workflow (next expected workflow)</action>
|
||||
|
||||
<check if="project_type != 'game'">
|
||||
<output>Note: This is a {{project_type}} project. Game brainstorming is designed for game projects.</output>
|
||||
<ask>Continue with game brainstorming anyway? (y/n)</ask>
|
||||
<check if="n">
|
||||
<action>Exit workflow</action>
|
||||
</check>
|
||||
</check>
|
||||
|
||||
<check if="brainstorm-game status is file path (already completed)">
|
||||
<output>⚠️ Game brainstorming session already completed: {{brainstorm-game 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-game is not the next expected workflow (latter items are completed already in the list)">
|
||||
<output>⚠️ Next expected workflow: {{next_workflow}}. Game brainstorming is out of sequence.</output>
|
||||
<ask>Continue with game 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 game brainstorming context and techniques">
|
||||
<action>Read the game context document from: {game_context}</action>
|
||||
<action>This context provides game-specific guidance including:
|
||||
- Focus areas for game ideation (mechanics, narrative, experience, etc.)
|
||||
- Key considerations for game design
|
||||
- Recommended techniques for game brainstorming
|
||||
- Output structure guidance
|
||||
</action>
|
||||
<action>Load game-specific brain techniques from: {game_brain_methods}</action>
|
||||
<action>These additional techniques supplement the standard CIS brainstorming methods with game design-focused approaches like:
|
||||
- MDA Framework exploration
|
||||
- Core loop brainstorming
|
||||
- Player fantasy mining
|
||||
- Genre mashup
|
||||
- And other game-specific ideation methods
|
||||
</action>
|
||||
</step>
|
||||
|
||||
<step n="3" goal="Invoke CIS brainstorming with game context">
|
||||
<action>Execute the CIS brainstorming workflow with game context and additional techniques</action>
|
||||
<invoke-workflow path="{core_brainstorming}" data="{game_context}" techniques="{game_brain_methods}">
|
||||
The CIS brainstorming workflow will:
|
||||
- Merge game-specific techniques with standard techniques
|
||||
- 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-game"</action>
|
||||
<critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
|
||||
<action>Update workflow_status["brainstorm-game"] = "{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>**✅ Game Brainstorming Session Complete, {user_name}!**
|
||||
|
||||
**Session Results:**
|
||||
|
||||
- Game brainstorming results saved to: {output_folder}/bmm-brainstorming-session-{{date}}.md
|
||||
|
||||
{{#if standalone_mode != true}}
|
||||
**Status Updated:**
|
||||
|
||||
- Progress tracking updated: brainstorm-game 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:** You can run other analysis workflows (research, game-brief) before proceeding
|
||||
|
||||
Check status anytime with: `workflow-status`
|
||||
{{else}}
|
||||
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>
|
||||
27
bmad/bmm/workflows/1-analysis/brainstorm-game/workflow.yaml
Normal file
27
bmad/bmm/workflows/1-analysis/brainstorm-game/workflow.yaml
Normal file
@@ -0,0 +1,27 @@
|
||||
# Brainstorm Game Workflow Configuration
|
||||
name: "brainstorm-game"
|
||||
description: "Facilitate game brainstorming sessions by orchestrating the CIS brainstorming workflow with game-specific context, guidance, and additional game design techniques."
|
||||
author: "BMad"
|
||||
|
||||
# Critical variables from config
|
||||
config_source: "{project-root}/bmad/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/bmm/workflows/1-analysis/brainstorm-game"
|
||||
template: false
|
||||
instructions: "{installed_path}/instructions.md"
|
||||
|
||||
# Context and techniques for game brainstorming
|
||||
game_context: "{installed_path}/game-context.md"
|
||||
game_brain_methods: "{installed_path}/game-brain-methods.csv"
|
||||
|
||||
# CORE brainstorming workflow to invoke
|
||||
core_brainstorming: "{project-root}/bmad/core/workflows/brainstorming/workflow.yaml"
|
||||
|
||||
standalone: true
|
||||
113
bmad/bmm/workflows/1-analysis/brainstorm-project/README.md
Normal file
113
bmad/bmm/workflows/1-analysis/brainstorm-project/README.md
Normal file
@@ -0,0 +1,113 @@
|
||||
# Project Brainstorming Workflow
|
||||
|
||||
Structured ideation for software projects exploring problem spaces, architectures, and innovative solutions beyond traditional requirements gathering.
|
||||
|
||||
## Table of Contents
|
||||
|
||||
- [Purpose](#purpose)
|
||||
- [Usage](#usage)
|
||||
- [Process](#process)
|
||||
- [Inputs & Outputs](#inputs--outputs)
|
||||
- [Integration](#integration)
|
||||
|
||||
## Purpose
|
||||
|
||||
Generate multiple solution approaches for software projects through:
|
||||
|
||||
- Parallel ideation tracks (architecture, UX, integration, value delivery)
|
||||
- Technical-business alignment from inception
|
||||
- Hidden assumption discovery
|
||||
- Innovation beyond obvious solutions
|
||||
|
||||
## Usage
|
||||
|
||||
```bash
|
||||
# Run brainstorming session
|
||||
bmad bmm *brainstorm-project
|
||||
|
||||
# Or via Analyst agent
|
||||
*brainstorm-project
|
||||
```
|
||||
|
||||
## Process
|
||||
|
||||
### 1. Context Capture
|
||||
|
||||
- Business objectives and constraints
|
||||
- Technical environment
|
||||
- Stakeholder needs
|
||||
- Success criteria
|
||||
|
||||
### 2. Parallel Ideation
|
||||
|
||||
- **Architecture Track**: Technical approaches with trade-offs
|
||||
- **UX Track**: Interface paradigms and user journeys
|
||||
- **Integration Track**: System connection patterns
|
||||
- **Value Track**: Feature prioritization and delivery
|
||||
|
||||
### 3. Solution Synthesis
|
||||
|
||||
- Evaluate feasibility and impact
|
||||
- Align with strategic objectives
|
||||
- Surface hidden assumptions
|
||||
- Generate recommendations
|
||||
|
||||
## Inputs & Outputs
|
||||
|
||||
### Inputs
|
||||
|
||||
| Input | Type | Purpose |
|
||||
| ----------------- | -------- | --------------------------------------------- |
|
||||
| Project Context | Document | Business objectives, environment, constraints |
|
||||
| Problem Statement | Optional | Core challenge or opportunity |
|
||||
|
||||
### Outputs
|
||||
|
||||
| Output | Content |
|
||||
| ------------------------ | ------------------------------------------- |
|
||||
| Architecture Proposals | Multiple approaches with trade-off analysis |
|
||||
| Value Framework | Prioritized features aligned to objectives |
|
||||
| Risk Analysis | Dependencies, challenges, opportunities |
|
||||
| Strategic Recommendation | Synthesized direction with rationale |
|
||||
|
||||
## Integration
|
||||
|
||||
### Workflow Chain
|
||||
|
||||
1. **brainstorm-project** ← Current step
|
||||
2. research (optional deep dive)
|
||||
3. product-brief (strategic document)
|
||||
4. Phase 2 planning (PRD/tech-spec)
|
||||
|
||||
### Feed Into
|
||||
|
||||
- Product Brief development
|
||||
- Architecture decisions
|
||||
- PRD requirements
|
||||
- Epic prioritization
|
||||
|
||||
## Best Practices
|
||||
|
||||
1. **Prepare context** - Gather business and technical background
|
||||
2. **Think broadly** - Explore non-obvious approaches
|
||||
3. **Document assumptions** - Capture implicit beliefs
|
||||
4. **Consider constraints** - Technical, organizational, resource
|
||||
5. **Focus on value** - Align to business objectives
|
||||
|
||||
## Configuration
|
||||
|
||||
```yaml
|
||||
# bmad/bmm/config.yaml
|
||||
output_folder: ./output
|
||||
project_name: Your Project
|
||||
```
|
||||
|
||||
## Related Workflows
|
||||
|
||||
- [Research](../research/README.md) - Deep investigation
|
||||
- [Product Brief](../product-brief/README.md) - Strategic planning
|
||||
- [PRD](../../2-plan-workflows/prd/README.md) - Requirements document
|
||||
|
||||
---
|
||||
|
||||
Part of BMad Method v6 - Phase 1 Analysis workflows
|
||||
110
bmad/bmm/workflows/1-analysis/brainstorm-project/instructions.md
Normal file
110
bmad/bmm/workflows/1-analysis/brainstorm-project/instructions.md
Normal file
@@ -0,0 +1,110 @@
|
||||
# Brainstorm Project - Workflow Instructions
|
||||
|
||||
```xml
|
||||
<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>This is a meta-workflow that orchestrates the CIS brainstorming workflow with project-specific context</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>
|
||||
```
|
||||
@@ -0,0 +1,25 @@
|
||||
# Project Brainstorming Context
|
||||
|
||||
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
|
||||
@@ -0,0 +1,26 @@
|
||||
# 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/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/bmm/workflows/1-analysis/brainstorm-project"
|
||||
template: false
|
||||
instructions: "{installed_path}/instructions.md"
|
||||
|
||||
# Context document for project brainstorming
|
||||
project_context: "{installed_path}/project-context.md"
|
||||
|
||||
# CORE brainstorming workflow to invoke
|
||||
core_brainstorming: "{project-root}/bmad/core/workflows/brainstorming/workflow.yaml"
|
||||
|
||||
standalone: true
|
||||
221
bmad/bmm/workflows/1-analysis/game-brief/README.md
Normal file
221
bmad/bmm/workflows/1-analysis/game-brief/README.md
Normal file
@@ -0,0 +1,221 @@
|
||||
# Game Brief Workflow
|
||||
|
||||
## Overview
|
||||
|
||||
The Game Brief workflow is the starting point for game projects in the BMad Method. It's a lightweight, interactive brainstorming and planning session that captures your game vision before diving into detailed Game Design Documents (GDD).
|
||||
|
||||
## Purpose
|
||||
|
||||
**Game Brief answers:**
|
||||
|
||||
- What game are you making?
|
||||
- Who is it for?
|
||||
- What makes it unique?
|
||||
- Is it feasible?
|
||||
|
||||
**This is NOT:**
|
||||
|
||||
- A full Game Design Document
|
||||
- A technical specification
|
||||
- A production plan
|
||||
- A detailed content outline
|
||||
|
||||
## When to Use This Workflow
|
||||
|
||||
Use the game-brief workflow when:
|
||||
|
||||
- Starting a new game project from scratch
|
||||
- Exploring a game idea before committing
|
||||
- Pitching a concept to team/stakeholders
|
||||
- Validating market fit and feasibility
|
||||
- Preparing input for the GDD workflow
|
||||
|
||||
Skip if:
|
||||
|
||||
- You already have a complete GDD
|
||||
- Continuing an existing project
|
||||
- Prototyping without planning needs
|
||||
|
||||
## Workflow Structure
|
||||
|
||||
### Interactive Mode (Recommended)
|
||||
|
||||
Work through each section collaboratively:
|
||||
|
||||
1. Game Vision (concept, pitch, vision statement)
|
||||
2. Target Market (audience, competition, positioning)
|
||||
3. Game Fundamentals (pillars, mechanics, experience goals)
|
||||
4. Scope and Constraints (platforms, timeline, budget, team)
|
||||
5. Reference Framework (inspiration, competitors, differentiators)
|
||||
6. Content Framework (world, narrative, volume)
|
||||
7. Art and Audio Direction (visual and audio style)
|
||||
8. Risk Assessment (risks, challenges, mitigation)
|
||||
9. Success Criteria (MVP, metrics, launch goals)
|
||||
10. Next Steps (immediate actions, research, questions)
|
||||
|
||||
### YOLO Mode
|
||||
|
||||
AI generates complete draft, then you refine sections iteratively.
|
||||
|
||||
## Key Features
|
||||
|
||||
### Optional Inputs
|
||||
|
||||
The workflow can incorporate:
|
||||
|
||||
- Market research
|
||||
- Brainstorming results
|
||||
- Competitive analysis
|
||||
- Design notes
|
||||
- Reference game lists
|
||||
|
||||
### Realistic Scoping
|
||||
|
||||
The workflow actively helps you:
|
||||
|
||||
- Identify scope vs. resource mismatches
|
||||
- Assess technical feasibility
|
||||
- Recognize market risks
|
||||
- Plan mitigation strategies
|
||||
|
||||
### Clear Handoff
|
||||
|
||||
Output is designed to feed directly into:
|
||||
|
||||
- GDD workflow (2-plan phase)
|
||||
- Prototyping decisions
|
||||
- Team discussions
|
||||
- Stakeholder presentations
|
||||
|
||||
## Output
|
||||
|
||||
**game-brief-{game_name}-{date}.md** containing:
|
||||
|
||||
- Executive summary
|
||||
- Complete game vision
|
||||
- Target market analysis
|
||||
- Core gameplay definition
|
||||
- Scope and constraints
|
||||
- Reference framework
|
||||
- Art/audio direction
|
||||
- Risk assessment
|
||||
- Success criteria
|
||||
- Next steps
|
||||
|
||||
## Integration with BMad Method
|
||||
|
||||
```
|
||||
1-analysis/game-brief (You are here)
|
||||
↓
|
||||
2-plan-workflows/gdd (Game Design Document)
|
||||
↓
|
||||
2-plan-workflows/narrative (Optional: Story-heavy games)
|
||||
↓
|
||||
3-solutioning (Technical architecture, engine selection)
|
||||
↓
|
||||
4-dev-stories (Implementation stories)
|
||||
```
|
||||
|
||||
## Comparison: Game Brief vs. GDD
|
||||
|
||||
| Aspect | Game Brief | GDD |
|
||||
| ------------------- | --------------------------- | ------------------------- |
|
||||
| **Purpose** | Validate concept | Design for implementation |
|
||||
| **Detail Level** | High-level vision | Detailed specifications |
|
||||
| **Time Investment** | 1-2 hours | 4-10 hours |
|
||||
| **Audience** | Self, team, stakeholders | Development team |
|
||||
| **Scope** | Concept validation | Implementation roadmap |
|
||||
| **Format** | Conversational, exploratory | Structured, comprehensive |
|
||||
| **Output** | 3-5 pages | 10-30+ pages |
|
||||
|
||||
## Comparison: Game Brief vs. Product Brief
|
||||
|
||||
| Aspect | Game Brief | Product Brief |
|
||||
| ----------------- | ---------------------------- | --------------------------------- |
|
||||
| **Focus** | Player experience, fun, feel | User problems, features, value |
|
||||
| **Metrics** | Engagement, retention, fun | Revenue, conversion, satisfaction |
|
||||
| **Core Elements** | Gameplay pillars, mechanics | Problem/solution, user segments |
|
||||
| **References** | Other games | Competitors, market |
|
||||
| **Vision** | Emotional experience | Business outcomes |
|
||||
|
||||
## Example Use Case
|
||||
|
||||
### Scenario: Indie Roguelike Card Game
|
||||
|
||||
**Starting Point:**
|
||||
"I want to make a roguelike card game with a twist"
|
||||
|
||||
**After Game Brief:**
|
||||
|
||||
- **Core Concept:** "A roguelike card battler where you play as emotions battling inner demons"
|
||||
- **Target Audience:** Core gamers who love Slay the Spire, interested in mental health themes
|
||||
- **Differentiator:** Emotional narrative system where deck composition affects story
|
||||
- **MVP Scope:** 3 characters, 80 cards, 30 enemy types, 3 bosses, 6-hour first run
|
||||
- **Platform:** PC (Steam) first, mobile later
|
||||
- **Timeline:** 12 months with 2-person team
|
||||
- **Key Risk:** Emotional theme might alienate hardcore roguelike fans
|
||||
- **Mitigation:** Prototype early, test with target audience, offer "mechanical-only" mode
|
||||
|
||||
**Next Steps:**
|
||||
|
||||
1. Build card combat prototype (2 weeks)
|
||||
2. Test emotional resonance with players
|
||||
3. Proceed to GDD workflow if prototype validates
|
||||
|
||||
## Tips for Success
|
||||
|
||||
### Be Honest About Scope
|
||||
|
||||
The most common game dev failure is scope mismatch. Use this workflow to reality-check:
|
||||
|
||||
- Can your team actually build this?
|
||||
- Is the timeline realistic?
|
||||
- Do you have budget for assets?
|
||||
|
||||
### Focus on Player Experience
|
||||
|
||||
Don't think about code or implementation. Think about:
|
||||
|
||||
- What will players DO?
|
||||
- How will they FEEL?
|
||||
- Why will they CARE?
|
||||
|
||||
### Validate Early
|
||||
|
||||
The brief identifies assumptions and risks. Don't skip to GDD without:
|
||||
|
||||
- Prototyping risky mechanics
|
||||
- Testing with target audience
|
||||
- Validating market interest
|
||||
|
||||
### Use References Wisely
|
||||
|
||||
"Like X but with Y" is a starting point, not a differentiator. Push beyond:
|
||||
|
||||
- What specifically from reference games?
|
||||
- What are you explicitly NOT doing?
|
||||
- What's genuinely new?
|
||||
|
||||
## FAQ
|
||||
|
||||
**Q: Is this required before GDD?**
|
||||
A: No, but highly recommended for new projects. You can start directly with GDD if you have a clear vision.
|
||||
|
||||
**Q: Can I use this for game jams?**
|
||||
A: Yes, but use YOLO mode for speed. Focus on vision, mechanics, and MVP scope.
|
||||
|
||||
**Q: What if my game concept changes?**
|
||||
A: Revisit and update the brief. It's a living document during early development.
|
||||
|
||||
**Q: How detailed should content volume estimates be?**
|
||||
A: Rough orders of magnitude are fine. "~50 enemies" not "47 enemies with 3 variants each."
|
||||
|
||||
**Q: Should I complete this alone or with my team?**
|
||||
A: Involve your team! Collaborative briefs catch blind spots and build shared vision.
|
||||
|
||||
## Related Workflows
|
||||
|
||||
- **Product Brief** (`1-analysis/product-brief`): For software products, not games
|
||||
- **GDD** (`2-plan-workflows/gdd`): Next step after game brief
|
||||
- **Narrative Design** (`2-plan-workflows/narrative`): For story-heavy games after GDD
|
||||
- **Solutioning** (`3-solutioning`): Technical architecture after planning
|
||||
128
bmad/bmm/workflows/1-analysis/game-brief/checklist.md
Normal file
128
bmad/bmm/workflows/1-analysis/game-brief/checklist.md
Normal file
@@ -0,0 +1,128 @@
|
||||
# Game Brief Validation Checklist
|
||||
|
||||
Use this checklist to ensure your game brief is complete and ready for GDD creation.
|
||||
|
||||
## Game Vision ✓
|
||||
|
||||
- [ ] **Core Concept** is clear and concise (one sentence)
|
||||
- [ ] **Elevator Pitch** hooks the reader in 2-3 sentences
|
||||
- [ ] **Vision Statement** is aspirational but achievable
|
||||
- [ ] Vision captures the emotional experience you want to create
|
||||
|
||||
## Target Market ✓
|
||||
|
||||
- [ ] **Primary Audience** is specific (not just "gamers")
|
||||
- [ ] Age range and experience level are defined
|
||||
- [ ] Play session expectations are realistic
|
||||
- [ ] **Market Context** demonstrates opportunity
|
||||
- [ ] Competitive landscape is understood
|
||||
- [ ] You know why this audience will care
|
||||
|
||||
## Game Fundamentals ✓
|
||||
|
||||
- [ ] **Core Gameplay Pillars** (2-4) are clearly defined
|
||||
- [ ] Each pillar is specific and measurable
|
||||
- [ ] **Primary Mechanics** describe what players actually DO
|
||||
- [ ] **Player Experience Goals** connect mechanics to emotions
|
||||
- [ ] Core loop is clear and compelling
|
||||
|
||||
## Scope and Constraints ✓
|
||||
|
||||
- [ ] **Target Platforms** are prioritized
|
||||
- [ ] **Development Timeline** is realistic
|
||||
- [ ] **Budget** aligns with scope
|
||||
- [ ] **Team Resources** (size, skills) are documented
|
||||
- [ ] **Technical Constraints** are identified
|
||||
- [ ] Scope matches team capability
|
||||
|
||||
## Reference Framework ✓
|
||||
|
||||
- [ ] **Inspiration Games** (3-5) are listed with specifics
|
||||
- [ ] You know what you're taking vs. NOT taking from each
|
||||
- [ ] **Competitive Analysis** covers direct and indirect competitors
|
||||
- [ ] **Key Differentiators** are genuine and valuable
|
||||
- [ ] Differentiators are specific (not "just better")
|
||||
|
||||
## Content Framework ✓
|
||||
|
||||
- [ ] **World and Setting** is defined
|
||||
- [ ] **Narrative Approach** matches game type
|
||||
- [ ] **Content Volume** is estimated (rough order of magnitude)
|
||||
- [ ] Playtime expectations are set
|
||||
- [ ] Replayability approach is clear
|
||||
|
||||
## Art and Audio Direction ✓
|
||||
|
||||
- [ ] **Visual Style** is described with references
|
||||
- [ ] 2D vs. 3D is decided
|
||||
- [ ] **Audio Style** matches game mood
|
||||
- [ ] **Production Approach** is realistic for team/budget
|
||||
- [ ] Style complexity matches capabilities
|
||||
|
||||
## Risk Assessment ✓
|
||||
|
||||
- [ ] **Key Risks** are honestly identified
|
||||
- [ ] **Technical Challenges** are documented
|
||||
- [ ] **Market Risks** are considered
|
||||
- [ ] **Mitigation Strategies** are actionable
|
||||
- [ ] Assumptions to validate are listed
|
||||
|
||||
## Success Criteria ✓
|
||||
|
||||
- [ ] **MVP Definition** is truly minimal
|
||||
- [ ] MVP can validate core gameplay hypothesis
|
||||
- [ ] **Success Metrics** are specific and measurable
|
||||
- [ ] **Launch Goals** are realistic
|
||||
- [ ] You know what "done" looks like for MVP
|
||||
|
||||
## Next Steps ✓
|
||||
|
||||
- [ ] **Immediate Actions** are prioritized
|
||||
- [ ] **Research Needs** are identified
|
||||
- [ ] **Open Questions** are documented
|
||||
- [ ] Critical path is clear
|
||||
- [ ] Blockers are identified
|
||||
|
||||
## Overall Quality ✓
|
||||
|
||||
- [ ] Brief is clear and concise (3-5 pages)
|
||||
- [ ] Sections are internally consistent
|
||||
- [ ] Scope is realistic for team/timeline/budget
|
||||
- [ ] Vision is compelling and achievable
|
||||
- [ ] You're excited to build this game
|
||||
- [ ] Team/stakeholders can understand the vision
|
||||
|
||||
## Red Flags 🚩
|
||||
|
||||
Watch for these warning signs:
|
||||
|
||||
- [ ] ❌ Scope too large for team/timeline
|
||||
- [ ] ❌ Unclear core loop or pillars
|
||||
- [ ] ❌ Target audience is "everyone"
|
||||
- [ ] ❌ Differentiators are vague or weak
|
||||
- [ ] ❌ No prototype plan for risky mechanics
|
||||
- [ ] ❌ Budget/timeline is wishful thinking
|
||||
- [ ] ❌ Market is saturated with no clear positioning
|
||||
- [ ] ❌ MVP is not actually minimal
|
||||
|
||||
## Ready for Next Steps?
|
||||
|
||||
If you've checked most boxes and have no major red flags:
|
||||
|
||||
✅ **Ready to proceed to:**
|
||||
|
||||
- Prototype core mechanic
|
||||
- GDD workflow
|
||||
- Team/stakeholder review
|
||||
- Market validation
|
||||
|
||||
⚠️ **Need more work if:**
|
||||
|
||||
- Multiple sections incomplete
|
||||
- Red flags present
|
||||
- Team/stakeholders don't align
|
||||
- Core concept unclear
|
||||
|
||||
---
|
||||
|
||||
_This checklist is a guide, not a gate. Use your judgment based on project needs._
|
||||
371
bmad/bmm/workflows/1-analysis/game-brief/instructions.md
Normal file
371
bmad/bmm/workflows/1-analysis/game-brief/instructions.md
Normal file
@@ -0,0 +1,371 @@
|
||||
# Game Brief - Interactive Workflow Instructions
|
||||
|
||||
<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} and language MUST be tailored to {user_skill_level}</critical>
|
||||
<critical>Generate all documents in {document_output_language}</critical>
|
||||
|
||||
<critical>DOCUMENT OUTPUT: Concise, professional, game-design focused. Use tables/lists over prose. User skill level ({user_skill_level}) affects conversation style ONLY, not document content.</critical>
|
||||
|
||||
<workflow>
|
||||
|
||||
<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. Game brief 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 "game-brief" workflow</action>
|
||||
<action>Get project_level from YAML metadata</action>
|
||||
<action>Find first non-completed workflow (next expected workflow)</action>
|
||||
|
||||
<check if="project_type != 'game'">
|
||||
<output>Note: This is a {{project_type}} project. Game brief is designed for game projects.</output>
|
||||
<ask>Continue with game brief anyway? (y/n)</ask>
|
||||
<check if="n">
|
||||
<action>Exit workflow</action>
|
||||
</check>
|
||||
</check>
|
||||
|
||||
<check if="game-brief status is file path (already completed)">
|
||||
<output>⚠️ Game Brief already completed: {{game-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="game-brief is not the next expected workflow (latter items are completed already in the list)">
|
||||
<output>⚠️ Next expected workflow: {{next_workflow}}. Game Brief is out of sequence.</output>
|
||||
<ask>Continue with Game 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="1" goal="Initialize game brief session">
|
||||
<action>Welcome the user in {communication_language} to the Game Brief creation process</action>
|
||||
<action>Explain this is a collaborative process to define their game vision, capturing the essence of what they want to create</action>
|
||||
<action>Ask for the working title of their game</action>
|
||||
<template-output>game_name</template-output>
|
||||
</step>
|
||||
|
||||
<step n="1" goal="Gather available inputs and context">
|
||||
<action>Explore what existing materials the user has available to inform the brief</action>
|
||||
<action>Offer options for input sources: market research, brainstorming results, competitive analysis, design notes, reference games, or starting fresh</action>
|
||||
<action>If documents are provided, load and analyze them to extract key insights, themes, and patterns</action>
|
||||
<action>Engage the user about their core vision: what gameplay experience they want to create, what emotions players should feel, and what sparked this game idea</action>
|
||||
<action>Build initial understanding through conversational exploration rather than rigid questioning</action>
|
||||
|
||||
<template-output>initial_context</template-output>
|
||||
</step>
|
||||
|
||||
<step n="2" goal="Choose collaboration mode">
|
||||
<ask>How would you like to work through the brief?
|
||||
|
||||
**1. Interactive Mode** - We'll work through each section together, discussing and refining as we go
|
||||
**2. YOLO Mode** - I'll generate a complete draft based on our conversation so far, then we'll refine it together
|
||||
|
||||
Which approach works best for you?</ask>
|
||||
|
||||
<action>Store the user's preference for mode</action>
|
||||
<template-output>collaboration_mode</template-output>
|
||||
</step>
|
||||
|
||||
<step n="3" goal="Define game vision" if="collaboration_mode == 'interactive'">
|
||||
<action>Guide user to articulate their game vision across three levels of depth</action>
|
||||
<action>Help them craft a one-sentence core concept that captures the essence (reference successful games like "A roguelike deck-builder where you climb a mysterious spire" as examples)</action>
|
||||
<action>Develop an elevator pitch (2-3 sentences) that would compel a publisher or player - refine until it's concise but hooks attention</action>
|
||||
<action>Explore their aspirational vision statement: the experience they want to create and what makes it meaningful - ensure it's ambitious yet achievable</action>
|
||||
<action>Refine through conversation, challenging vague language and elevating compelling ideas</action>
|
||||
|
||||
<template-output>core_concept</template-output>
|
||||
<template-output>elevator_pitch</template-output>
|
||||
<template-output>vision_statement</template-output>
|
||||
</step>
|
||||
|
||||
<step n="4" goal="Identify target market" if="collaboration_mode == 'interactive'">
|
||||
<action>Guide user to define their primary target audience with specific demographics, gaming preferences, and behavioral characteristics</action>
|
||||
<action>Push for specificity beyond generic descriptions like "people who like fun games" - challenge vague answers</action>
|
||||
<action>Explore secondary audiences if applicable and how their needs might differ</action>
|
||||
<action>Investigate the market context: opportunity size, competitive landscape, similar successful games, and why now is the right time</action>
|
||||
<action>Help identify a realistic and reachable audience segment based on evidence or well-reasoned assumptions</action>
|
||||
|
||||
<template-output>primary_audience</template-output>
|
||||
<template-output>secondary_audience</template-output>
|
||||
<template-output>market_context</template-output>
|
||||
</step>
|
||||
|
||||
<step n="5" goal="Define game fundamentals" if="collaboration_mode == 'interactive'">
|
||||
<action>Help user identify 2-4 core gameplay pillars that fundamentally define their game - everything should support these pillars</action>
|
||||
<action>Provide examples from successful games for inspiration (Hollow Knight's "tight controls + challenging combat + rewarding exploration")</action>
|
||||
<action>Explore what the player actually DOES - core actions, key systems, and interaction models</action>
|
||||
<action>Define the emotional experience goals: what feelings are you designing for (tension/relief, mastery/growth, creativity/expression, discovery/surprise)</action>
|
||||
<action>Ensure pillars are specific and measurable, focusing on player actions rather than implementation details</action>
|
||||
<action>Connect mechanics directly to emotional experiences through guided discussion</action>
|
||||
|
||||
<template-output>core_gameplay_pillars</template-output>
|
||||
<template-output>primary_mechanics</template-output>
|
||||
<template-output>player_experience_goals</template-output>
|
||||
</step>
|
||||
|
||||
<step n="6" goal="Define scope and constraints" if="collaboration_mode == 'interactive'">
|
||||
<action>Help user establish realistic project constraints across all key dimensions</action>
|
||||
<action>Explore target platforms and prioritization (PC, console, mobile, web)</action>
|
||||
<action>Discuss development timeline: release targets, fixed deadlines, phased release strategies</action>
|
||||
<action>Investigate budget reality: funding source, asset creation costs, marketing, tools and software</action>
|
||||
<action>Assess team resources: size, roles, availability, skills gaps, outsourcing needs</action>
|
||||
<action>Define technical constraints: engine choice, performance targets, file size limits, accessibility requirements</action>
|
||||
<action>Push for realism about scope - identify potential blockers early and document resource assumptions</action>
|
||||
|
||||
<template-output>target_platforms</template-output>
|
||||
<template-output>development_timeline</template-output>
|
||||
<template-output>budget_considerations</template-output>
|
||||
<template-output>team_resources</template-output>
|
||||
<template-output>technical_constraints</template-output>
|
||||
</step>
|
||||
|
||||
<step n="7" goal="Establish reference framework" if="collaboration_mode == 'interactive'">
|
||||
<action>Guide user to identify 3-5 inspiration games and articulate what they're drawing from each (mechanics, feel, art style) and explicitly what they're NOT taking</action>
|
||||
<action>Conduct competitive analysis: identify direct and indirect competitors, analyze what they do well and poorly, and define how this game will differ</action>
|
||||
<action>Explore key differentiators and unique value proposition - what's the hook that makes players choose this game over alternatives</action>
|
||||
<action>Challenge "just better" thinking - push for genuine, specific differentiation that's actually valuable to players</action>
|
||||
<action>Validate that differentiators are concrete, achievable, and compelling</action>
|
||||
|
||||
<template-output>inspiration_games</template-output>
|
||||
<template-output>competitive_analysis</template-output>
|
||||
<template-output>key_differentiators</template-output>
|
||||
</step>
|
||||
|
||||
<step n="8" goal="Define content framework" if="collaboration_mode == 'interactive'">
|
||||
<action>Explore the game's world and setting: location, time period, world-building depth, narrative importance, and genre context</action>
|
||||
<action>Define narrative approach: story-driven/light/absent, linear/branching/emergent, delivery methods (cutscenes, dialogue, environmental), writing scope</action>
|
||||
<action>Estimate content volume realistically: playthrough length, level/stage count, replayability strategy, total asset volume</action>
|
||||
<action>Identify if a dedicated narrative workflow will be needed later based on story complexity</action>
|
||||
<action>Flag content-heavy areas that require detailed planning and resource allocation</action>
|
||||
|
||||
<template-output>world_setting</template-output>
|
||||
<template-output>narrative_approach</template-output>
|
||||
<template-output>content_volume</template-output>
|
||||
</step>
|
||||
|
||||
<step n="9" goal="Define art and audio direction" if="collaboration_mode == 'interactive'">
|
||||
<action>Explore visual style direction: art style preference, color palette and mood, reference games/images, 2D vs 3D, animation requirements</action>
|
||||
<action>Define audio style: music genre and mood, SFX approach, voice acting scope, audio's importance to gameplay</action>
|
||||
<action>Discuss production approach: in-house creation vs outsourcing, asset store usage, AI/generative tools, style complexity vs team capability</action>
|
||||
<action>Ensure art and audio vision aligns realistically with budget and team skills - identify potential production bottlenecks early</action>
|
||||
<action>Note if a comprehensive style guide will be needed for consistent production</action>
|
||||
|
||||
<template-output>visual_style</template-output>
|
||||
<template-output>audio_style</template-output>
|
||||
<template-output>production_approach</template-output>
|
||||
</step>
|
||||
|
||||
<step n="10" goal="Assess risks" if="collaboration_mode == 'interactive'">
|
||||
<action>Facilitate honest risk assessment across all dimensions - what could prevent completion, what could make it unfun, what assumptions might be wrong</action>
|
||||
<action>Identify technical challenges: unproven elements, performance concerns, platform-specific issues, tool dependencies</action>
|
||||
<action>Explore market risks: saturation, trend dependency, competition intensity, discoverability challenges</action>
|
||||
<action>For each major risk, develop actionable mitigation strategies - how to validate assumptions, backup plans, early prototyping opportunities</action>
|
||||
<action>Prioritize risks by impact and likelihood, focusing on proactive mitigation rather than passive worry</action>
|
||||
|
||||
<template-output>key_risks</template-output>
|
||||
<template-output>technical_challenges</template-output>
|
||||
<template-output>market_risks</template-output>
|
||||
<template-output>mitigation_strategies</template-output>
|
||||
</step>
|
||||
|
||||
<step n="11" goal="Define success criteria" if="collaboration_mode == 'interactive'">
|
||||
<action>Define the MVP (Minimum Playable Version) - what's the absolute minimum where the core loop is fun and complete, with essential content only</action>
|
||||
<action>Establish specific, measurable success metrics: player acquisition, retention rates, session length, completion rate, review scores, revenue targets, community engagement</action>
|
||||
<action>Set concrete launch goals: first-month sales/downloads, review score targets, streamer/press coverage, community size</action>
|
||||
<action>Push for specificity and measurability - challenge vague aspirations with "how will you measure that?"</action>
|
||||
<action>Clearly distinguish between MVP milestones and full release goals, ensuring all targets are realistic given resources</action>
|
||||
|
||||
<template-output>mvp_definition</template-output>
|
||||
<template-output>success_metrics</template-output>
|
||||
<template-output>launch_goals</template-output>
|
||||
</step>
|
||||
|
||||
<step n="12" goal="Identify immediate next steps" if="collaboration_mode == 'interactive'">
|
||||
<action>Identify immediate actions to take right after this brief: prototype core mechanics, create art style tests, validate technical feasibility, build vertical slice, playtest with target audience</action>
|
||||
<action>Determine research needs: market validation, technical proof of concept, player interest testing, competitive deep-dive</action>
|
||||
<action>Document open questions and uncertainties: unresolved design questions, technical unknowns, market validation needs, resource/budget questions</action>
|
||||
<action>Create actionable, specific next steps - prioritize by importance and dependency</action>
|
||||
<action>Identify blockers that must be resolved before moving forward</action>
|
||||
|
||||
<template-output>immediate_actions</template-output>
|
||||
<template-output>research_needs</template-output>
|
||||
<template-output>open_questions</template-output>
|
||||
</step>
|
||||
|
||||
<!-- YOLO Mode - Generate everything then refine -->
|
||||
<step n="3" goal="Generate complete brief draft" if="collaboration_mode == 'yolo'">
|
||||
<action>Based on initial context and any provided documents, generate a complete game brief covering all sections</action>
|
||||
<action>Make reasonable assumptions where information is missing</action>
|
||||
<action>Flag areas that need user validation with [NEEDS CONFIRMATION] tags</action>
|
||||
|
||||
<template-output>core_concept</template-output>
|
||||
<template-output>elevator_pitch</template-output>
|
||||
<template-output>vision_statement</template-output>
|
||||
<template-output>primary_audience</template-output>
|
||||
<template-output>secondary_audience</template-output>
|
||||
<template-output>market_context</template-output>
|
||||
<template-output>core_gameplay_pillars</template-output>
|
||||
<template-output>primary_mechanics</template-output>
|
||||
<template-output>player_experience_goals</template-output>
|
||||
<template-output>target_platforms</template-output>
|
||||
<template-output>development_timeline</template-output>
|
||||
<template-output>budget_considerations</template-output>
|
||||
<template-output>team_resources</template-output>
|
||||
<template-output>technical_constraints</template-output>
|
||||
<template-output>inspiration_games</template-output>
|
||||
<template-output>competitive_analysis</template-output>
|
||||
<template-output>key_differentiators</template-output>
|
||||
<template-output>world_setting</template-output>
|
||||
<template-output>narrative_approach</template-output>
|
||||
<template-output>content_volume</template-output>
|
||||
<template-output>visual_style</template-output>
|
||||
<template-output>audio_style</template-output>
|
||||
<template-output>production_approach</template-output>
|
||||
<template-output>key_risks</template-output>
|
||||
<template-output>technical_challenges</template-output>
|
||||
<template-output>market_risks</template-output>
|
||||
<template-output>mitigation_strategies</template-output>
|
||||
<template-output>mvp_definition</template-output>
|
||||
<template-output>success_metrics</template-output>
|
||||
<template-output>launch_goals</template-output>
|
||||
<template-output>immediate_actions</template-output>
|
||||
<template-output>research_needs</template-output>
|
||||
<template-output>open_questions</template-output>
|
||||
|
||||
<action>Present the complete draft to the user</action>
|
||||
<ask>Here's the complete game brief draft. What would you like to adjust or refine?</ask>
|
||||
</step>
|
||||
|
||||
<step n="4" goal="Refine brief sections" repeat="until-approved" if="collaboration_mode == 'yolo'">
|
||||
<ask>Which section would you like to refine?
|
||||
|
||||
1. Game Vision
|
||||
2. Target Market
|
||||
3. Game Fundamentals
|
||||
4. Scope and Constraints
|
||||
5. Reference Framework
|
||||
6. Content Framework
|
||||
7. Art and Audio Direction
|
||||
8. Risk Assessment
|
||||
9. Success Criteria
|
||||
10. Next Steps
|
||||
11. Save and continue</ask>
|
||||
|
||||
<action>Work with user to refine selected section</action>
|
||||
<action>Update relevant template outputs</action>
|
||||
</step>
|
||||
|
||||
<!-- Final steps for both modes -->
|
||||
<step n="13" goal="Create executive summary">
|
||||
<action>Synthesize all sections into a compelling executive summary</action>
|
||||
<action>Include:
|
||||
- Game concept in 1-2 sentences
|
||||
- Target audience and market
|
||||
- Core gameplay pillars
|
||||
- Key differentiators
|
||||
- Success vision</action>
|
||||
|
||||
<template-output>executive_summary</template-output>
|
||||
</step>
|
||||
|
||||
<step n="14" goal="Compile supporting materials">
|
||||
<action>If research documents were provided, create a summary of key findings</action>
|
||||
<action>Document any stakeholder input received during the process</action>
|
||||
<action>Compile list of reference games and resources</action>
|
||||
|
||||
<template-output>research_summary</template-output>
|
||||
<template-output>stakeholder_input</template-output>
|
||||
<template-output>references</template-output>
|
||||
</step>
|
||||
|
||||
<step n="15" goal="Final review and handoff">
|
||||
<action>Generate the complete game brief document</action>
|
||||
<action>Review all sections for completeness and consistency</action>
|
||||
<action>Flag any areas that need design attention with [DESIGN-TODO] tags</action>
|
||||
|
||||
<ask>The game brief is complete! Would you like to:
|
||||
|
||||
1. Review the entire document
|
||||
2. Make final adjustments
|
||||
3. Generate an executive summary version (3-page limit)
|
||||
4. Save and prepare for GDD creation
|
||||
|
||||
This brief will serve as the primary input for creating the Game Design Document (GDD).
|
||||
|
||||
**Recommended next steps:**
|
||||
|
||||
- Create prototype of core mechanic
|
||||
- Proceed to GDD workflow: `workflow gdd`
|
||||
- Validate assumptions with target players</ask>
|
||||
|
||||
<check if="user chooses option 3 (executive summary)">
|
||||
<action>Create condensed 3-page executive brief focusing on: core concept, target market, gameplay pillars, key differentiators, and success criteria</action>
|
||||
<action>Save as: {output_folder}/game-brief-executive-{{game_name}}-{{date}}.md</action>
|
||||
</check>
|
||||
|
||||
<template-output>final_brief</template-output>
|
||||
<template-output>executive_brief</template-output>
|
||||
</step>
|
||||
|
||||
<step n="16" 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 "game-brief"</action>
|
||||
<critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
|
||||
<action>Update workflow_status["game-brief"] = "{output_folder}/bmm-game-brief-{{game_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>**✅ Game Brief Complete, {user_name}!**
|
||||
|
||||
**Brief Document:**
|
||||
|
||||
- Game brief saved to {output_folder}/bmm-game-brief-{{game_name}}-{{date}}.md
|
||||
|
||||
{{#if standalone_mode != true}}
|
||||
**Status Updated:**
|
||||
|
||||
- Progress tracking updated: game-brief 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:** Consider creating a prototype of core mechanic or validating assumptions with target players before proceeding
|
||||
|
||||
Check status anytime with: `workflow-status`
|
||||
{{else}}
|
||||
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>
|
||||
205
bmad/bmm/workflows/1-analysis/game-brief/template.md
Normal file
205
bmad/bmm/workflows/1-analysis/game-brief/template.md
Normal file
@@ -0,0 +1,205 @@
|
||||
# Game Brief: {{game_name}}
|
||||
|
||||
**Date:** {{date}}
|
||||
**Author:** {{user_name}}
|
||||
**Status:** Draft for GDD Development
|
||||
|
||||
---
|
||||
|
||||
## Executive Summary
|
||||
|
||||
{{executive_summary}}
|
||||
|
||||
---
|
||||
|
||||
## Game Vision
|
||||
|
||||
### Core Concept
|
||||
|
||||
{{core_concept}}
|
||||
|
||||
### Elevator Pitch
|
||||
|
||||
{{elevator_pitch}}
|
||||
|
||||
### Vision Statement
|
||||
|
||||
{{vision_statement}}
|
||||
|
||||
---
|
||||
|
||||
## Target Market
|
||||
|
||||
### Primary Audience
|
||||
|
||||
{{primary_audience}}
|
||||
|
||||
### Secondary Audience
|
||||
|
||||
{{secondary_audience}}
|
||||
|
||||
### Market Context
|
||||
|
||||
{{market_context}}
|
||||
|
||||
---
|
||||
|
||||
## Game Fundamentals
|
||||
|
||||
### Core Gameplay Pillars
|
||||
|
||||
{{core_gameplay_pillars}}
|
||||
|
||||
### Primary Mechanics
|
||||
|
||||
{{primary_mechanics}}
|
||||
|
||||
### Player Experience Goals
|
||||
|
||||
{{player_experience_goals}}
|
||||
|
||||
---
|
||||
|
||||
## Scope and Constraints
|
||||
|
||||
### Target Platforms
|
||||
|
||||
{{target_platforms}}
|
||||
|
||||
### Development Timeline
|
||||
|
||||
{{development_timeline}}
|
||||
|
||||
### Budget Considerations
|
||||
|
||||
{{budget_considerations}}
|
||||
|
||||
### Team Resources
|
||||
|
||||
{{team_resources}}
|
||||
|
||||
### Technical Constraints
|
||||
|
||||
{{technical_constraints}}
|
||||
|
||||
---
|
||||
|
||||
## Reference Framework
|
||||
|
||||
### Inspiration Games
|
||||
|
||||
{{inspiration_games}}
|
||||
|
||||
### Competitive Analysis
|
||||
|
||||
{{competitive_analysis}}
|
||||
|
||||
### Key Differentiators
|
||||
|
||||
{{key_differentiators}}
|
||||
|
||||
---
|
||||
|
||||
## Content Framework
|
||||
|
||||
### World and Setting
|
||||
|
||||
{{world_setting}}
|
||||
|
||||
### Narrative Approach
|
||||
|
||||
{{narrative_approach}}
|
||||
|
||||
### Content Volume
|
||||
|
||||
{{content_volume}}
|
||||
|
||||
---
|
||||
|
||||
## Art and Audio Direction
|
||||
|
||||
### Visual Style
|
||||
|
||||
{{visual_style}}
|
||||
|
||||
### Audio Style
|
||||
|
||||
{{audio_style}}
|
||||
|
||||
### Production Approach
|
||||
|
||||
{{production_approach}}
|
||||
|
||||
---
|
||||
|
||||
## Risk Assessment
|
||||
|
||||
### Key Risks
|
||||
|
||||
{{key_risks}}
|
||||
|
||||
### Technical Challenges
|
||||
|
||||
{{technical_challenges}}
|
||||
|
||||
### Market Risks
|
||||
|
||||
{{market_risks}}
|
||||
|
||||
### Mitigation Strategies
|
||||
|
||||
{{mitigation_strategies}}
|
||||
|
||||
---
|
||||
|
||||
## Success Criteria
|
||||
|
||||
### MVP Definition
|
||||
|
||||
{{mvp_definition}}
|
||||
|
||||
### Success Metrics
|
||||
|
||||
{{success_metrics}}
|
||||
|
||||
### Launch Goals
|
||||
|
||||
{{launch_goals}}
|
||||
|
||||
---
|
||||
|
||||
## Next Steps
|
||||
|
||||
### Immediate Actions
|
||||
|
||||
{{immediate_actions}}
|
||||
|
||||
### Research Needs
|
||||
|
||||
{{research_needs}}
|
||||
|
||||
### Open Questions
|
||||
|
||||
{{open_questions}}
|
||||
|
||||
---
|
||||
|
||||
## Appendices
|
||||
|
||||
### A. Research Summary
|
||||
|
||||
{{research_summary}}
|
||||
|
||||
### B. Stakeholder Input
|
||||
|
||||
{{stakeholder_input}}
|
||||
|
||||
### C. References
|
||||
|
||||
{{references}}
|
||||
|
||||
---
|
||||
|
||||
_This Game Brief serves as the foundational input for Game Design Document (GDD) creation._
|
||||
|
||||
_Next Steps: Use the `workflow gdd` command to create detailed game design documentation._
|
||||
32
bmad/bmm/workflows/1-analysis/game-brief/workflow.yaml
Normal file
32
bmad/bmm/workflows/1-analysis/game-brief/workflow.yaml
Normal file
@@ -0,0 +1,32 @@
|
||||
# Game Brief - Interactive Workflow Configuration
|
||||
name: game-brief
|
||||
description: "Interactive game brief creation workflow that guides users through defining their game vision with multiple input sources and conversational collaboration"
|
||||
author: "BMad"
|
||||
|
||||
# Critical variables from config
|
||||
config_source: "{project-root}/bmad/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
|
||||
|
||||
# Optional input documents
|
||||
recommended_inputs:
|
||||
- market_research: "Market research document (optional)"
|
||||
- brainstorming_results: "Brainstorming session outputs (optional)"
|
||||
- competitive_analysis: "Competitive game analysis (optional)"
|
||||
- initial_ideas: "Initial game ideas or notes (optional)"
|
||||
- reference_games: "List of inspiration games (optional)"
|
||||
|
||||
# Module path and component files
|
||||
installed_path: "{project-root}/bmad/bmm/workflows/1-analysis/game-brief"
|
||||
template: "{installed_path}/template.md"
|
||||
instructions: "{installed_path}/instructions.md"
|
||||
validation: "{installed_path}/checklist.md"
|
||||
|
||||
# Output configuration
|
||||
default_output_file: "{output_folder}/game-brief-{{game_name}}-{{date}}.md"
|
||||
|
||||
standalone: true
|
||||
180
bmad/bmm/workflows/1-analysis/product-brief/README.md
Normal file
180
bmad/bmm/workflows/1-analysis/product-brief/README.md
Normal file
@@ -0,0 +1,180 @@
|
||||
# Product Brief Workflow
|
||||
|
||||
## Overview
|
||||
|
||||
Interactive product brief creation workflow that guides users through defining their product vision with multiple input sources and conversational collaboration. Supports both structured interactive mode and rapid "YOLO" mode for quick draft generation.
|
||||
|
||||
## Key Features
|
||||
|
||||
- **Dual Mode Operation** - Interactive step-by-step or rapid draft generation
|
||||
- **Multi-Input Support** - Integrates market research, competitive analysis, and brainstorming results
|
||||
- **Conversational Design** - Guides users through strategic thinking with probing questions
|
||||
- **Executive Summary Generation** - Creates compelling summaries for stakeholder communication
|
||||
- **Comprehensive Coverage** - Addresses all critical product planning dimensions
|
||||
- **Stakeholder Ready** - Generates professional briefs suitable for PM handoff
|
||||
|
||||
## Usage
|
||||
|
||||
### Basic Invocation
|
||||
|
||||
```bash
|
||||
workflow product-brief
|
||||
```
|
||||
|
||||
### With Input Documents
|
||||
|
||||
```bash
|
||||
# With market research
|
||||
workflow product-brief --input market-research.md
|
||||
|
||||
# With multiple inputs
|
||||
workflow product-brief --input market-research.md --input competitive-analysis.md
|
||||
```
|
||||
|
||||
### Configuration
|
||||
|
||||
- **brief_format**: "comprehensive" (full detail) or "executive" (3-page limit)
|
||||
- **autonomous**: false (requires user collaboration)
|
||||
- **output_folder**: Location for generated brief
|
||||
|
||||
## Workflow Structure
|
||||
|
||||
### Files Included
|
||||
|
||||
```
|
||||
product-brief/
|
||||
├── workflow.yaml # Configuration and metadata
|
||||
├── instructions.md # Interactive workflow steps
|
||||
├── template.md # Product brief document structure
|
||||
├── checklist.md # Validation criteria
|
||||
└── README.md # This file
|
||||
```
|
||||
|
||||
## Workflow Process
|
||||
|
||||
### Phase 1: Initialization and Context (Steps 0-2)
|
||||
|
||||
- **Project Setup**: Captures project name and basic context
|
||||
- **Input Gathering**: Collects and analyzes available documents
|
||||
- **Mode Selection**: Chooses interactive or YOLO collaboration approach
|
||||
- **Context Extraction**: Identifies core problems and opportunities
|
||||
|
||||
### Phase 2: Interactive Development (Steps 3-12) - Interactive Mode
|
||||
|
||||
- **Problem Definition**: Deep dive into user pain points and market gaps
|
||||
- **Solution Articulation**: Develops clear value proposition and approach
|
||||
- **User Segmentation**: Defines primary and secondary target audiences
|
||||
- **Success Metrics**: Establishes measurable goals and KPIs
|
||||
- **MVP Scoping**: Ruthlessly defines minimum viable features
|
||||
- **Financial Planning**: Assesses ROI and strategic alignment
|
||||
- **Technical Context**: Captures platform and technology considerations
|
||||
- **Risk Assessment**: Identifies constraints, assumptions, and unknowns
|
||||
|
||||
### Phase 3: Rapid Generation (Steps 3-4) - YOLO Mode
|
||||
|
||||
- **Complete Draft**: Generates full brief based on initial context
|
||||
- **Iterative Refinement**: User-guided section improvements
|
||||
- **Quality Validation**: Ensures completeness and consistency
|
||||
|
||||
### Phase 4: Finalization (Steps 13-15)
|
||||
|
||||
- **Executive Summary**: Creates compelling overview for stakeholders
|
||||
- **Supporting Materials**: Compiles research summaries and references
|
||||
- **Final Review**: Quality check and handoff preparation
|
||||
|
||||
## Output
|
||||
|
||||
### Generated Files
|
||||
|
||||
- **Primary output**: product-brief-{project_name}-{date}.md
|
||||
- **Supporting files**: Research summaries and stakeholder input documentation
|
||||
|
||||
### Output Structure
|
||||
|
||||
1. **Executive Summary** - High-level product concept and value proposition
|
||||
2. **Problem Statement** - Detailed problem analysis with evidence
|
||||
3. **Proposed Solution** - Core approach and key differentiators
|
||||
4. **Target Users** - Primary and secondary user segments with personas
|
||||
5. **Goals and Success Metrics** - Business objectives and measurable KPIs
|
||||
6. **MVP Scope** - Must-have features and out-of-scope items
|
||||
7. **Post-MVP Vision** - Phase 2 features and long-term roadmap
|
||||
8. **Financial Impact** - Investment requirements and ROI projections
|
||||
9. **Strategic Alignment** - Connection to company OKRs and initiatives
|
||||
10. **Technical Considerations** - Platform requirements and preferences
|
||||
11. **Constraints and Assumptions** - Resource limits and key assumptions
|
||||
12. **Risks and Open Questions** - Risk assessment and research needs
|
||||
13. **Supporting Materials** - Research summaries and references
|
||||
|
||||
## Requirements
|
||||
|
||||
No special requirements - designed to work with or without existing documentation.
|
||||
|
||||
## Best Practices
|
||||
|
||||
### Before Starting
|
||||
|
||||
1. **Gather Available Research**: Collect any market research, competitive analysis, or user feedback
|
||||
2. **Define Stakeholder Audience**: Know who will use this brief for decision-making
|
||||
3. **Set Time Boundaries**: Interactive mode requires 60-90 minutes for quality results
|
||||
|
||||
### During Execution
|
||||
|
||||
1. **Be Specific**: Avoid generic statements - provide concrete examples and data
|
||||
2. **Think Strategically**: Focus on "why" and "what" rather than "how"
|
||||
3. **Challenge Assumptions**: Use the conversation to test and refine your thinking
|
||||
4. **Scope Ruthlessly**: Resist feature creep in MVP definition
|
||||
|
||||
### After Completion
|
||||
|
||||
1. **Validate with Checklist**: Use included criteria to ensure completeness
|
||||
2. **Stakeholder Review**: Share executive summary first, then full brief
|
||||
3. **Iterate Based on Feedback**: Product briefs should evolve with new insights
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### Common Issues
|
||||
|
||||
**Issue**: Brief lacks specificity or contains vague statements
|
||||
|
||||
- **Solution**: Restart problem definition with concrete examples and measurable impacts
|
||||
- **Check**: Ensure each section answers "so what?" and provides actionable insights
|
||||
|
||||
**Issue**: MVP scope is too large or undefined
|
||||
|
||||
- **Solution**: Use the "what's the minimum to validate core hypothesis?" filter
|
||||
- **Check**: Verify that each MVP feature is truly essential for initial value delivery
|
||||
|
||||
**Issue**: Missing strategic context or business justification
|
||||
|
||||
- **Solution**: Return to financial impact and strategic alignment sections
|
||||
- **Check**: Ensure connection to company goals and clear ROI potential
|
||||
|
||||
## Customization
|
||||
|
||||
To customize this workflow:
|
||||
|
||||
1. **Modify Questions**: Update instructions.md to add industry-specific or company-specific prompts
|
||||
2. **Adjust Template**: Customize template.md sections for organizational brief standards
|
||||
3. **Add Validation**: Extend checklist.md with company-specific quality criteria
|
||||
4. **Configure Modes**: Adjust brief_format settings for different output styles
|
||||
|
||||
## Version History
|
||||
|
||||
- **v6.0.0** - Interactive conversational design with dual modes
|
||||
- Interactive and YOLO mode support
|
||||
- Multi-input document integration
|
||||
- Executive summary generation
|
||||
- Strategic alignment focus
|
||||
|
||||
## 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`
|
||||
- Consider running market research workflow first if lacking business context
|
||||
- Consult BMAD documentation for product planning methodology
|
||||
|
||||
---
|
||||
|
||||
_Part of the BMad Method v6 - BMM (Method) Module_
|
||||
115
bmad/bmm/workflows/1-analysis/product-brief/checklist.md
Normal file
115
bmad/bmm/workflows/1-analysis/product-brief/checklist.md
Normal file
@@ -0,0 +1,115 @@
|
||||
# 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)
|
||||
332
bmad/bmm/workflows/1-analysis/product-brief/instructions.md
Normal file
332
bmad/bmm/workflows/1-analysis/product-brief/instructions.md
Normal file
@@ -0,0 +1,332 @@
|
||||
# Product Brief - Interactive Workflow Instructions
|
||||
|
||||
<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} and language MUST be tailored to {user_skill_level}</critical>
|
||||
<critical>Generate all documents in {document_output_language}</critical>
|
||||
|
||||
<critical>DOCUMENT OUTPUT: Concise, professional, strategically focused. Use tables/lists over prose. User skill level ({user_skill_level}) affects conversation style ONLY, not document content.</critical>
|
||||
|
||||
<workflow>
|
||||
|
||||
<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. Product Brief 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 "product-brief" workflow</action>
|
||||
<action>Get project_level from YAML metadata</action>
|
||||
<action>Find first non-completed workflow (next expected workflow)</action>
|
||||
|
||||
<check if="project_level < 2">
|
||||
<output>Note: Product Brief is most valuable for Level 2+ projects. Your project is Level {{project_level}}.</output>
|
||||
<output>You may want to skip directly to technical planning instead.</output>
|
||||
</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 (latter items are completed already in the list)">
|
||||
<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="1" goal="Initialize product brief session">
|
||||
<action>Welcome the user in {communication_language} to the Product Brief creation process</action>
|
||||
<action>Explain this is a collaborative process to define their product vision and strategic foundation</action>
|
||||
<action>Ask the user to provide the project name for this product brief</action>
|
||||
<template-output>project_name</template-output>
|
||||
</step>
|
||||
|
||||
<step n="1" goal="Gather available inputs and context">
|
||||
<action>Explore what existing materials the user has available to inform the brief</action>
|
||||
<action>Offer options for input sources: market research, brainstorming results, competitive analysis, initial ideas, or starting fresh</action>
|
||||
<action>If documents are provided, load and analyze them to extract key insights, themes, and patterns</action>
|
||||
<action>Engage the user about their core vision: what problem they're solving, who experiences it most acutely, and what sparked this product idea</action>
|
||||
<action>Build initial understanding through conversational exploration rather than rigid questioning</action>
|
||||
|
||||
<template-output>initial_context</template-output>
|
||||
</step>
|
||||
|
||||
<step n="2" goal="Choose collaboration mode">
|
||||
<ask>How would you like to work through the brief?
|
||||
|
||||
**1. Interactive Mode** - We'll work through each section together, discussing and refining as we go
|
||||
|
||||
**2. YOLO Mode** - I'll generate a complete draft based on our conversation so far, then we'll refine it together
|
||||
|
||||
Which approach works best for you?</ask>
|
||||
|
||||
<action>Store the user's preference for mode</action>
|
||||
<template-output>collaboration_mode</template-output>
|
||||
</step>
|
||||
|
||||
<step n="3" goal="Define the problem statement" if="collaboration_mode == 'interactive'">
|
||||
<action>Guide deep exploration of the problem: current state frustrations, quantifiable impact (time/money/opportunities), why existing solutions fall short, urgency of solving now</action>
|
||||
<action>Challenge vague statements and push for specificity with probing questions</action>
|
||||
<action>Help the user articulate measurable pain points with evidence</action>
|
||||
<action>Craft a compelling, evidence-based problem statement</action>
|
||||
|
||||
<template-output>problem_statement</template-output>
|
||||
</step>
|
||||
|
||||
<step n="4" goal="Develop the proposed solution" if="collaboration_mode == 'interactive'">
|
||||
<action>Shape the solution vision by exploring: core approach to solving the problem, key differentiators from existing solutions, why this will succeed, ideal user experience</action>
|
||||
<action>Focus on the "what" and "why", not implementation details - keep it strategic</action>
|
||||
<action>Help articulate compelling differentiators that make this solution unique</action>
|
||||
<action>Craft a clear, inspiring solution vision</action>
|
||||
|
||||
<template-output>proposed_solution</template-output>
|
||||
</step>
|
||||
|
||||
<step n="5" goal="Identify target users" if="collaboration_mode == 'interactive'">
|
||||
<action>Guide detailed definition of primary users: demographic/professional profile, current problem-solving methods, specific pain points, goals they're trying to achieve</action>
|
||||
<action>Explore secondary user segments if applicable and define how their needs differ</action>
|
||||
<action>Push beyond generic personas like "busy professionals" - demand specificity and actionable details</action>
|
||||
<action>Create specific, actionable user profiles that inform product decisions</action>
|
||||
|
||||
<template-output>primary_user_segment</template-output>
|
||||
<template-output>secondary_user_segment</template-output>
|
||||
</step>
|
||||
|
||||
<step n="6" goal="Establish goals and success metrics" if="collaboration_mode == 'interactive'">
|
||||
<action>Guide establishment of SMART goals across business objectives and user success metrics</action>
|
||||
<action>Explore measurable business outcomes (user acquisition targets, cost reductions, revenue goals)</action>
|
||||
<action>Define user success metrics focused on behaviors and outcomes, not features (task completion time, return frequency)</action>
|
||||
<action>Help formulate specific, measurable goals that distinguish between business and user success</action>
|
||||
<action>Identify top 3-5 Key Performance Indicators that will track product success</action>
|
||||
|
||||
<template-output>business_objectives</template-output>
|
||||
<template-output>user_success_metrics</template-output>
|
||||
<template-output>key_performance_indicators</template-output>
|
||||
</step>
|
||||
|
||||
<step n="7" goal="Define MVP scope" if="collaboration_mode == 'interactive'">
|
||||
<action>Be ruthless about MVP scope - identify absolute MUST-HAVE features for launch that validate the core hypothesis</action>
|
||||
<action>For each proposed feature, probe why it's essential vs nice-to-have</action>
|
||||
<action>Identify tempting features that need to wait for v2 - what adds complexity without core value</action>
|
||||
<action>Define what constitutes a successful MVP launch with clear criteria</action>
|
||||
<action>Challenge scope creep aggressively and push for true minimum viability</action>
|
||||
<action>Clearly separate must-haves from nice-to-haves</action>
|
||||
|
||||
<template-output>core_features</template-output>
|
||||
<template-output>out_of_scope</template-output>
|
||||
<template-output>mvp_success_criteria</template-output>
|
||||
</step>
|
||||
|
||||
<step n="8" goal="Assess financial impact and ROI" if="collaboration_mode == 'interactive'">
|
||||
<action>Explore financial considerations: development investment, revenue potential, cost savings opportunities, break-even timing, budget alignment</action>
|
||||
<action>Investigate strategic alignment: company OKRs, strategic objectives, key initiatives supported, opportunity cost of NOT doing this</action>
|
||||
<action>Help quantify financial impact where possible - both tangible and intangible value</action>
|
||||
<action>Connect this product to broader company strategy and demonstrate strategic value</action>
|
||||
|
||||
<template-output>financial_impact</template-output>
|
||||
<template-output>company_objectives_alignment</template-output>
|
||||
<template-output>strategic_initiatives</template-output>
|
||||
</step>
|
||||
|
||||
<step n="9" goal="Explore post-MVP vision" optional="true" if="collaboration_mode == 'interactive'">
|
||||
<action>Guide exploration of post-MVP future: Phase 2 features, expansion opportunities, long-term vision (1-2 years)</action>
|
||||
<action>Ensure MVP decisions align with future direction while staying focused on immediate goals</action>
|
||||
|
||||
<template-output>phase_2_features</template-output>
|
||||
<template-output>long_term_vision</template-output>
|
||||
<template-output>expansion_opportunities</template-output>
|
||||
</step>
|
||||
|
||||
<step n="10" goal="Document technical considerations" if="collaboration_mode == 'interactive'">
|
||||
<action>Capture technical context as preferences, not final decisions</action>
|
||||
<action>Explore platform requirements: web/mobile/desktop, browser/OS support, performance needs, accessibility standards</action>
|
||||
<action>Investigate technology preferences or constraints: frontend/backend frameworks, database needs, infrastructure requirements</action>
|
||||
<action>Identify existing systems requiring integration</action>
|
||||
<action>Check for technical-preferences.yaml file if available</action>
|
||||
<action>Note these are initial thoughts for PM and architect to consider during planning</action>
|
||||
|
||||
<template-output>platform_requirements</template-output>
|
||||
<template-output>technology_preferences</template-output>
|
||||
<template-output>architecture_considerations</template-output>
|
||||
</step>
|
||||
|
||||
<step n="11" goal="Identify constraints and assumptions" if="collaboration_mode == 'interactive'">
|
||||
<action>Guide realistic expectations setting around constraints: budget/resource limits, timeline pressures, team size/expertise, technical limitations</action>
|
||||
<action>Explore assumptions being made about: user behavior, market conditions, technical feasibility</action>
|
||||
<action>Document constraints clearly and list assumptions that need validation during development</action>
|
||||
|
||||
<template-output>constraints</template-output>
|
||||
<template-output>key_assumptions</template-output>
|
||||
</step>
|
||||
|
||||
<step n="12" goal="Assess risks and open questions" optional="true" if="collaboration_mode == 'interactive'">
|
||||
<action>Facilitate honest risk assessment: what could derail the project, impact if risks materialize</action>
|
||||
<action>Document open questions: what still needs figuring out, what needs more research</action>
|
||||
<action>Help prioritize risks by impact and likelihood</action>
|
||||
<action>Frame unknowns as opportunities to prepare, not just worries</action>
|
||||
|
||||
<template-output>key_risks</template-output>
|
||||
<template-output>open_questions</template-output>
|
||||
<template-output>research_areas</template-output>
|
||||
</step>
|
||||
|
||||
<!-- YOLO Mode - Generate everything then refine -->
|
||||
<step n="3" goal="Generate complete brief draft" if="collaboration_mode == 'yolo'">
|
||||
<action>Based on initial context and any provided documents, generate a complete product brief covering all sections</action>
|
||||
<action>Make reasonable assumptions where information is missing</action>
|
||||
<action>Flag areas that need user validation with [NEEDS CONFIRMATION] tags</action>
|
||||
|
||||
<template-output>problem_statement</template-output>
|
||||
<template-output>proposed_solution</template-output>
|
||||
<template-output>primary_user_segment</template-output>
|
||||
<template-output>secondary_user_segment</template-output>
|
||||
<template-output>business_objectives</template-output>
|
||||
<template-output>user_success_metrics</template-output>
|
||||
<template-output>key_performance_indicators</template-output>
|
||||
<template-output>core_features</template-output>
|
||||
<template-output>out_of_scope</template-output>
|
||||
<template-output>mvp_success_criteria</template-output>
|
||||
<template-output>phase_2_features</template-output>
|
||||
<template-output>long_term_vision</template-output>
|
||||
<template-output>expansion_opportunities</template-output>
|
||||
<template-output>financial_impact</template-output>
|
||||
<template-output>company_objectives_alignment</template-output>
|
||||
<template-output>strategic_initiatives</template-output>
|
||||
<template-output>platform_requirements</template-output>
|
||||
<template-output>technology_preferences</template-output>
|
||||
<template-output>architecture_considerations</template-output>
|
||||
<template-output>constraints</template-output>
|
||||
<template-output>key_assumptions</template-output>
|
||||
<template-output>key_risks</template-output>
|
||||
<template-output>open_questions</template-output>
|
||||
<template-output>research_areas</template-output>
|
||||
|
||||
<action>Present the complete draft to the user</action>
|
||||
<ask>Here's the complete brief draft. What would you like to adjust or refine?</ask>
|
||||
</step>
|
||||
|
||||
<step n="4" goal="Refine brief sections" repeat="until-approved" if="collaboration_mode == 'yolo'">
|
||||
<ask>Which section would you like to refine?
|
||||
1. Problem Statement
|
||||
2. Proposed Solution
|
||||
3. Target Users
|
||||
4. Goals and Metrics
|
||||
5. MVP Scope
|
||||
6. Post-MVP Vision
|
||||
7. Financial Impact and Strategic Alignment
|
||||
8. Technical Considerations
|
||||
9. Constraints and Assumptions
|
||||
10. Risks and Questions
|
||||
11. Save and continue</ask>
|
||||
|
||||
<action>Work with user to refine selected section</action>
|
||||
<action>Update relevant template outputs</action>
|
||||
</step>
|
||||
|
||||
<!-- Final steps for both modes -->
|
||||
<step n="13" goal="Create executive summary">
|
||||
<action>Synthesize all sections into a compelling executive summary</action>
|
||||
<action>Include:
|
||||
- Product concept in 1-2 sentences
|
||||
- Primary problem being solved
|
||||
- Target market identification
|
||||
- Key value proposition</action>
|
||||
|
||||
<template-output>executive_summary</template-output>
|
||||
</step>
|
||||
|
||||
<step n="14" goal="Compile supporting materials">
|
||||
<action>If research documents were provided, create a summary of key findings</action>
|
||||
<action>Document any stakeholder input received during the process</action>
|
||||
<action>Compile list of reference documents and resources</action>
|
||||
|
||||
<template-output>research_summary</template-output>
|
||||
<template-output>stakeholder_input</template-output>
|
||||
<template-output>references</template-output>
|
||||
</step>
|
||||
|
||||
<step n="15" goal="Final review and handoff">
|
||||
<action>Generate the complete product brief document</action>
|
||||
<action>Review all sections for completeness and consistency</action>
|
||||
<action>Flag any areas that need PM attention with [PM-TODO] tags</action>
|
||||
|
||||
<ask>The product brief is complete! Would you like to:
|
||||
|
||||
1. Review the entire document
|
||||
2. Make final adjustments
|
||||
3. Generate an executive summary version (3-page limit)
|
||||
4. Save and prepare for handoff to PM
|
||||
|
||||
This brief will serve as the primary input for creating the Product Requirements Document (PRD).</ask>
|
||||
|
||||
<check if="user chooses option 3 (executive summary)">
|
||||
<action>Create condensed 3-page executive brief focusing on: problem statement, proposed solution, target users, MVP scope, financial impact, and strategic alignment</action>
|
||||
<action>Save as: {output_folder}/product-brief-executive-{{project_name}}-{{date}}.md</action>
|
||||
</check>
|
||||
|
||||
<template-output>final_brief</template-output>
|
||||
<template-output>executive_brief</template-output>
|
||||
</step>
|
||||
|
||||
<step n="16" 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 "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}!**
|
||||
|
||||
**Brief Document:**
|
||||
|
||||
- Product brief saved to {output_folder}/bmm-product-brief-{{project_name}}-{{date}}.md
|
||||
|
||||
{{#if standalone_mode != true}}
|
||||
**Status Updated:**
|
||||
|
||||
- Progress tracking updated: product-brief 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:** Gather additional stakeholder input or run research workflows before proceeding
|
||||
|
||||
Check status anytime with: `workflow-status`
|
||||
{{else}}
|
||||
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>
|
||||
165
bmad/bmm/workflows/1-analysis/product-brief/template.md
Normal file
165
bmad/bmm/workflows/1-analysis/product-brief/template.md
Normal file
@@ -0,0 +1,165 @@
|
||||
# Product Brief: {{project_name}}
|
||||
|
||||
**Date:** {{date}}
|
||||
**Author:** {{user_name}}
|
||||
**Status:** Draft for PM Review
|
||||
|
||||
---
|
||||
|
||||
## Executive Summary
|
||||
|
||||
{{executive_summary}}
|
||||
|
||||
---
|
||||
|
||||
## Problem Statement
|
||||
|
||||
{{problem_statement}}
|
||||
|
||||
---
|
||||
|
||||
## Proposed Solution
|
||||
|
||||
{{proposed_solution}}
|
||||
|
||||
---
|
||||
|
||||
## Target Users
|
||||
|
||||
### Primary User Segment
|
||||
|
||||
{{primary_user_segment}}
|
||||
|
||||
### Secondary User Segment
|
||||
|
||||
{{secondary_user_segment}}
|
||||
|
||||
---
|
||||
|
||||
## Goals and Success Metrics
|
||||
|
||||
### Business Objectives
|
||||
|
||||
{{business_objectives}}
|
||||
|
||||
### User Success Metrics
|
||||
|
||||
{{user_success_metrics}}
|
||||
|
||||
### Key Performance Indicators (KPIs)
|
||||
|
||||
{{key_performance_indicators}}
|
||||
|
||||
---
|
||||
|
||||
## Strategic Alignment and Financial Impact
|
||||
|
||||
### Financial Impact
|
||||
|
||||
{{financial_impact}}
|
||||
|
||||
### Company Objectives Alignment
|
||||
|
||||
{{company_objectives_alignment}}
|
||||
|
||||
### Strategic Initiatives
|
||||
|
||||
{{strategic_initiatives}}
|
||||
|
||||
---
|
||||
|
||||
## MVP Scope
|
||||
|
||||
### Core Features (Must Have)
|
||||
|
||||
{{core_features}}
|
||||
|
||||
### Out of Scope for MVP
|
||||
|
||||
{{out_of_scope}}
|
||||
|
||||
### MVP Success Criteria
|
||||
|
||||
{{mvp_success_criteria}}
|
||||
|
||||
---
|
||||
|
||||
## Post-MVP Vision
|
||||
|
||||
### Phase 2 Features
|
||||
|
||||
{{phase_2_features}}
|
||||
|
||||
### Long-term Vision
|
||||
|
||||
{{long_term_vision}}
|
||||
|
||||
### Expansion Opportunities
|
||||
|
||||
{{expansion_opportunities}}
|
||||
|
||||
---
|
||||
|
||||
## Technical Considerations
|
||||
|
||||
### Platform Requirements
|
||||
|
||||
{{platform_requirements}}
|
||||
|
||||
### Technology Preferences
|
||||
|
||||
{{technology_preferences}}
|
||||
|
||||
### Architecture Considerations
|
||||
|
||||
{{architecture_considerations}}
|
||||
|
||||
---
|
||||
|
||||
## Constraints and Assumptions
|
||||
|
||||
### Constraints
|
||||
|
||||
{{constraints}}
|
||||
|
||||
### Key Assumptions
|
||||
|
||||
{{key_assumptions}}
|
||||
|
||||
---
|
||||
|
||||
## Risks and Open Questions
|
||||
|
||||
### Key Risks
|
||||
|
||||
{{key_risks}}
|
||||
|
||||
### Open Questions
|
||||
|
||||
{{open_questions}}
|
||||
|
||||
### Areas Needing Further Research
|
||||
|
||||
{{research_areas}}
|
||||
|
||||
---
|
||||
|
||||
## Appendices
|
||||
|
||||
### A. Research Summary
|
||||
|
||||
{{research_summary}}
|
||||
|
||||
### B. Stakeholder Input
|
||||
|
||||
{{stakeholder_input}}
|
||||
|
||||
### C. References
|
||||
|
||||
{{references}}
|
||||
|
||||
---
|
||||
|
||||
_This Product Brief serves as the foundational input for Product Requirements Document (PRD) creation._
|
||||
|
||||
_Next Steps: Handoff to Product Manager for PRD development using the `workflow prd` command._
|
||||
31
bmad/bmm/workflows/1-analysis/product-brief/workflow.yaml
Normal file
31
bmad/bmm/workflows/1-analysis/product-brief/workflow.yaml
Normal file
@@ -0,0 +1,31 @@
|
||||
# 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/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
|
||||
|
||||
# Optional input documents
|
||||
recommended_inputs:
|
||||
- market_research: "Market research document (optional)"
|
||||
- brainstorming_results: "Brainstorming session outputs (optional)"
|
||||
- competitive_analysis: "Competitive analysis (optional)"
|
||||
- initial_ideas: "Initial product ideas or notes (optional)"
|
||||
|
||||
# Module path and component files
|
||||
installed_path: "{project-root}/bmad/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
|
||||
454
bmad/bmm/workflows/1-analysis/research/README.md
Normal file
454
bmad/bmm/workflows/1-analysis/research/README.md
Normal file
@@ -0,0 +1,454 @@
|
||||
# Research Workflow - Multi-Type Research System
|
||||
|
||||
## Overview
|
||||
|
||||
The Research Workflow is a comprehensive, adaptive research system that supports multiple research types through an intelligent router pattern. This workflow consolidates various research methodologies into a single, powerful tool that adapts to your specific research needs - from market analysis to technical evaluation to AI prompt generation.
|
||||
|
||||
**Version 2.0.0** - Multi-type research system with router-based architecture
|
||||
|
||||
## Key Features
|
||||
|
||||
### 🔀 Intelligent Research Router
|
||||
|
||||
- **6 Research Types**: Market, Deep Prompt, Technical, Competitive, User, Domain
|
||||
- **Dynamic Instructions**: Loads appropriate instruction set based on research type
|
||||
- **Adaptive Templates**: Selects optimal output format for research goal
|
||||
- **Context-Aware**: Adjusts frameworks and methods per research type
|
||||
|
||||
### 🔍 Market Research (Type: `market`)
|
||||
|
||||
- Real-time web research for current market data
|
||||
- TAM/SAM/SOM calculations with multiple methodologies
|
||||
- Competitive landscape analysis and positioning
|
||||
- Customer persona development and Jobs-to-be-Done
|
||||
- Porter's Five Forces and strategic frameworks
|
||||
- Go-to-market strategy recommendations
|
||||
|
||||
### 🤖 Deep Research Prompt Generation (Type: `deep_prompt`)
|
||||
|
||||
- **Optimized for AI Research Platforms**: ChatGPT Deep Research, Gemini, Grok DeepSearch, Claude Projects
|
||||
- **Prompt Engineering Best Practices**: Multi-stage research workflows, iterative refinement
|
||||
- **Platform-Specific Optimization**: Tailored prompts for each AI research tool
|
||||
- **Context Packaging**: Structures background information for optimal AI understanding
|
||||
- **Research Question Refinement**: Transforms vague questions into precise research prompts
|
||||
|
||||
### 🏗️ Technical/Architecture Research (Type: `technical`)
|
||||
|
||||
- Technology evaluation and comparison matrices
|
||||
- Architecture pattern research and trade-off analysis
|
||||
- Framework/library assessment with pros/cons
|
||||
- Technical feasibility studies
|
||||
- Cost-benefit analysis for technology decisions
|
||||
- Architecture Decision Records (ADR) generation
|
||||
|
||||
### 🎯 Competitive Intelligence (Type: `competitive`)
|
||||
|
||||
- Deep competitor analysis and profiling
|
||||
- Competitive positioning and gap analysis
|
||||
- Strategic group mapping
|
||||
- Feature comparison matrices
|
||||
- Pricing strategy analysis
|
||||
- Market share and growth tracking
|
||||
|
||||
### 👥 User Research (Type: `user`)
|
||||
|
||||
- Customer insights and behavioral analysis
|
||||
- Persona development with demographics and psychographics
|
||||
- Jobs-to-be-Done framework application
|
||||
- Customer journey mapping
|
||||
- Pain point identification
|
||||
- Willingness-to-pay analysis
|
||||
|
||||
### 🌐 Domain/Industry Research (Type: `domain`)
|
||||
|
||||
- Industry deep dives and trend analysis
|
||||
- Regulatory landscape assessment
|
||||
- Domain expertise synthesis
|
||||
- Best practices identification
|
||||
- Standards and compliance requirements
|
||||
- Emerging patterns and disruptions
|
||||
|
||||
## Usage
|
||||
|
||||
### Basic Invocation
|
||||
|
||||
```bash
|
||||
workflow research
|
||||
```
|
||||
|
||||
The workflow will prompt you to select a research type.
|
||||
|
||||
### Direct Research Type Selection
|
||||
|
||||
```bash
|
||||
# Market research
|
||||
workflow research --type market
|
||||
|
||||
# Deep research prompt generation
|
||||
workflow research --type deep_prompt
|
||||
|
||||
# Technical evaluation
|
||||
workflow research --type technical
|
||||
|
||||
# Competitive intelligence
|
||||
workflow research --type competitive
|
||||
|
||||
# User research
|
||||
workflow research --type user
|
||||
|
||||
# Domain analysis
|
||||
workflow research --type domain
|
||||
```
|
||||
|
||||
### With Input Documents
|
||||
|
||||
```bash
|
||||
workflow research --type market --input product-brief.md --input competitor-list.md
|
||||
workflow research --type technical --input requirements.md --input architecture.md
|
||||
workflow research --type deep_prompt --input research-question.md
|
||||
```
|
||||
|
||||
### Configuration Options
|
||||
|
||||
Can be customized through `workflow.yaml`:
|
||||
|
||||
- **research_depth**: `quick`, `standard`, or `comprehensive`
|
||||
- **enable_web_research**: `true`/`false` for real-time data gathering
|
||||
- **enable_competitor_analysis**: `true`/`false` (market/competitive types)
|
||||
- **enable_financial_modeling**: `true`/`false` (market type)
|
||||
|
||||
## Workflow Structure
|
||||
|
||||
### Files Included
|
||||
|
||||
```
|
||||
research/
|
||||
├── workflow.yaml # Multi-type configuration
|
||||
├── instructions-router.md # Router logic (loads correct instructions)
|
||||
├── instructions-market.md # Market research workflow
|
||||
├── instructions-deep-prompt.md # Deep prompt generation workflow
|
||||
├── instructions-technical.md # Technical evaluation workflow
|
||||
├── template-market.md # Market research report template
|
||||
├── template-deep-prompt.md # Research prompt template
|
||||
├── template-technical.md # Technical evaluation template
|
||||
├── checklist.md # Universal validation criteria
|
||||
├── README.md # This file
|
||||
└── claude-code/ # Claude Code enhancements (optional)
|
||||
├── injections.yaml # Integration configuration
|
||||
└── sub-agents/ # Specialized research agents
|
||||
├── bmm-market-researcher.md
|
||||
├── bmm-trend-spotter.md
|
||||
├── bmm-data-analyst.md
|
||||
├── bmm-competitor-analyzer.md
|
||||
├── bmm-user-researcher.md
|
||||
└── bmm-technical-evaluator.md
|
||||
```
|
||||
|
||||
## Workflow Process
|
||||
|
||||
### Phase 1: Research Type Selection and Setup
|
||||
|
||||
1. Router presents research type menu
|
||||
2. User selects research type (market, deep_prompt, technical, competitive, user, domain)
|
||||
3. Router loads appropriate instructions and template
|
||||
4. Gather research parameters and inputs
|
||||
|
||||
### Phase 2: Research Type-Specific Execution
|
||||
|
||||
**For Market Research:**
|
||||
|
||||
1. Define research objectives and market boundaries
|
||||
2. Conduct web research across multiple sources
|
||||
3. Calculate TAM/SAM/SOM with triangulation
|
||||
4. Develop customer segments and personas
|
||||
5. Analyze competitive landscape
|
||||
6. Apply industry frameworks (Porter's Five Forces, etc.)
|
||||
7. Identify trends and opportunities
|
||||
8. Develop strategic recommendations
|
||||
9. Create financial projections (optional)
|
||||
10. Compile comprehensive report
|
||||
|
||||
**For Deep Prompt Generation:**
|
||||
|
||||
1. Analyze research question or topic
|
||||
2. Identify optimal AI research platform (ChatGPT, Gemini, Grok, Claude)
|
||||
3. Structure research context and background
|
||||
4. Generate platform-optimized prompt
|
||||
5. Create multi-stage research workflow
|
||||
6. Define iteration and refinement strategy
|
||||
7. Package with context documents
|
||||
8. Provide execution guidance
|
||||
|
||||
**For Technical Research:**
|
||||
|
||||
1. Define technical requirements and constraints
|
||||
2. Identify technologies/frameworks to evaluate
|
||||
3. Research each option (documentation, community, maturity)
|
||||
4. Create comparison matrix with criteria
|
||||
5. Perform trade-off analysis
|
||||
6. Calculate cost-benefit for each option
|
||||
7. Generate Architecture Decision Record (ADR)
|
||||
8. Provide recommendation with rationale
|
||||
|
||||
**For Competitive/User/Domain:**
|
||||
|
||||
- Uses market research workflow with specific focus
|
||||
- Adapts questions and frameworks to research type
|
||||
- Customizes output format for target audience
|
||||
|
||||
### Phase 3: Validation and Delivery
|
||||
|
||||
1. Review outputs against checklist
|
||||
2. Validate completeness and quality
|
||||
3. Generate final report/document
|
||||
4. Provide next steps and recommendations
|
||||
|
||||
## Output
|
||||
|
||||
### Generated Files by Research Type
|
||||
|
||||
**Market Research:**
|
||||
|
||||
- `market-research-{product_name}-{date}.md`
|
||||
- Comprehensive market analysis report (10+ sections)
|
||||
|
||||
**Deep Research Prompt:**
|
||||
|
||||
- `deep-research-prompt-{date}.md`
|
||||
- Optimized AI research prompt with context and instructions
|
||||
|
||||
**Technical Research:**
|
||||
|
||||
- `technical-research-{date}.md`
|
||||
- Technology evaluation with comparison matrix and ADR
|
||||
|
||||
**Competitive Intelligence:**
|
||||
|
||||
- `competitive-intelligence-{date}.md`
|
||||
- Detailed competitor analysis and positioning
|
||||
|
||||
**User Research:**
|
||||
|
||||
- `user-research-{date}.md`
|
||||
- Customer insights and persona documentation
|
||||
|
||||
**Domain Research:**
|
||||
|
||||
- `domain-research-{date}.md`
|
||||
- Industry deep dive with trends and best practices
|
||||
|
||||
## Requirements
|
||||
|
||||
### All Research Types
|
||||
|
||||
- BMAD Core v6 project structure
|
||||
- Web search capability (for real-time research)
|
||||
- Access to research data sources
|
||||
|
||||
### Market Research
|
||||
|
||||
- Product or business description
|
||||
- Target customer hypotheses (optional)
|
||||
- Known competitors list (optional)
|
||||
|
||||
### Deep Prompt Research
|
||||
|
||||
- Research question or topic
|
||||
- Background context documents (optional)
|
||||
- Target AI platform preference (optional)
|
||||
|
||||
### Technical Research
|
||||
|
||||
- Technical requirements document
|
||||
- Current architecture (if brownfield)
|
||||
- Technical constraints list
|
||||
|
||||
## Best Practices
|
||||
|
||||
### Before Starting
|
||||
|
||||
1. **Know Your Research Goal**: Select the most appropriate research type
|
||||
2. **Gather Context**: Collect relevant documents before starting
|
||||
3. **Set Depth Level**: Choose appropriate research_depth (quick/standard/comprehensive)
|
||||
4. **Define Success Criteria**: What decisions will this research inform?
|
||||
|
||||
### During Execution
|
||||
|
||||
**Market Research:**
|
||||
|
||||
- Provide specific product/service details
|
||||
- Validate market boundaries carefully
|
||||
- Review TAM/SAM/SOM assumptions
|
||||
- Challenge competitive positioning
|
||||
|
||||
**Deep Prompt Generation:**
|
||||
|
||||
- Be specific about research platform target
|
||||
- Provide rich context documents
|
||||
- Clarify expected research outcome
|
||||
- Define iteration strategy
|
||||
|
||||
**Technical Research:**
|
||||
|
||||
- List all evaluation criteria upfront
|
||||
- Weight criteria by importance
|
||||
- Consider long-term implications
|
||||
- Include cost analysis
|
||||
|
||||
### After Completion
|
||||
|
||||
1. Review using the validation checklist
|
||||
2. Update with any missing information
|
||||
3. Share with stakeholders for feedback
|
||||
4. Schedule follow-up research if needed
|
||||
5. Document decisions made based on research
|
||||
|
||||
## Research Frameworks Available
|
||||
|
||||
### Market Research Frameworks
|
||||
|
||||
- TAM/SAM/SOM Analysis
|
||||
- Porter's Five Forces
|
||||
- Jobs-to-be-Done (JTBD)
|
||||
- Technology Adoption Lifecycle
|
||||
- SWOT Analysis
|
||||
- Value Chain Analysis
|
||||
|
||||
### Technical Research Frameworks
|
||||
|
||||
- Trade-off Analysis Matrix
|
||||
- Architecture Decision Records (ADR)
|
||||
- Technology Radar
|
||||
- Comparison Matrix
|
||||
- Cost-Benefit Analysis
|
||||
- Technical Risk Assessment
|
||||
|
||||
### Deep Prompt Frameworks
|
||||
|
||||
- ChatGPT Deep Research Best Practices
|
||||
- Gemini Deep Research Framework
|
||||
- Grok DeepSearch Optimization
|
||||
- Claude Projects Methodology
|
||||
- Iterative Prompt Refinement
|
||||
|
||||
## Data Sources
|
||||
|
||||
The workflow leverages multiple data sources:
|
||||
|
||||
- Industry reports and publications
|
||||
- Government statistics and databases
|
||||
- Financial reports and SEC filings
|
||||
- News articles and press releases
|
||||
- Academic research papers
|
||||
- Technical documentation and RFCs
|
||||
- GitHub repositories and discussions
|
||||
- Stack Overflow and developer forums
|
||||
- Market research firm reports
|
||||
- Social media and communities
|
||||
- Patent databases
|
||||
- Benchmarking studies
|
||||
|
||||
## Claude Code Enhancements
|
||||
|
||||
### Available Subagents
|
||||
|
||||
1. **bmm-market-researcher** - Market intelligence gathering
|
||||
2. **bmm-trend-spotter** - Emerging trends and weak signals
|
||||
3. **bmm-data-analyst** - Quantitative analysis and modeling
|
||||
4. **bmm-competitor-analyzer** - Competitive intelligence
|
||||
5. **bmm-user-researcher** - Customer insights and personas
|
||||
6. **bmm-technical-evaluator** - Technology assessment
|
||||
|
||||
These are automatically invoked during workflow execution if Claude Code integration is configured.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### Issue: Don't know which research type to choose
|
||||
|
||||
- **Solution**: Start with research question - "What do I need to know?"
|
||||
- Market viability? → `market`
|
||||
- Best technology? → `technical`
|
||||
- Need AI to research deeper? → `deep_prompt`
|
||||
- Who are competitors? → `competitive`
|
||||
- Who are users? → `user`
|
||||
- Industry understanding? → `domain`
|
||||
|
||||
### Issue: Market research results seem incomplete
|
||||
|
||||
- **Solution**: Increase research_depth to `comprehensive`
|
||||
- **Check**: Enable web_research in workflow.yaml
|
||||
- **Try**: Run competitive and user research separately for more depth
|
||||
|
||||
### Issue: Deep prompt doesn't work with target platform
|
||||
|
||||
- **Solution**: Review platform-specific best practices in generated prompt
|
||||
- **Check**: Ensure context documents are included
|
||||
- **Try**: Regenerate with different platform selection
|
||||
|
||||
### Issue: Technical comparison is subjective
|
||||
|
||||
- **Solution**: Add more objective criteria (performance metrics, cost, community size)
|
||||
- **Check**: Weight criteria by business importance
|
||||
- **Try**: Run pilot implementations for top 2 options
|
||||
|
||||
## Customization
|
||||
|
||||
### Adding New Research Types
|
||||
|
||||
1. Create new instructions file: `instructions-{type}.md`
|
||||
2. Create new template file: `template-{type}.md`
|
||||
3. Add research type to `workflow.yaml` `research_types` section
|
||||
4. Update router logic in `instructions-router.md`
|
||||
|
||||
### Modifying Existing Research Types
|
||||
|
||||
1. Edit appropriate `instructions-{type}.md` file
|
||||
2. Update corresponding `template-{type}.md` if needed
|
||||
3. Adjust validation criteria in `checklist.md`
|
||||
|
||||
### Creating Custom Frameworks
|
||||
|
||||
Add to `workflow.yaml` `frameworks` section under appropriate research type.
|
||||
|
||||
## Version History
|
||||
|
||||
- **v2.0.0** - Multi-type research system with router architecture
|
||||
- Added deep_prompt research type for AI research platform optimization
|
||||
- Added technical research type for technology evaluation
|
||||
- Consolidated competitive, user, domain under market with focus variants
|
||||
- Router-based instruction loading
|
||||
- Template selection by research type
|
||||
- Enhanced Claude Code subagent support
|
||||
|
||||
- **v1.0.0** - Initial market research only implementation
|
||||
- Single-purpose market research workflow
|
||||
- Now deprecated in favor of v2.0.0 multi-type system
|
||||
|
||||
## Support
|
||||
|
||||
For issues or questions:
|
||||
|
||||
- Review workflow creation guide at `/bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
|
||||
- Check validation against `checklist.md`
|
||||
- Examine router logic in `instructions-router.md`
|
||||
- Review research type-specific instructions
|
||||
- Consult BMAD Method v6 documentation
|
||||
|
||||
## Migration from v1.0 market-research
|
||||
|
||||
If you're used to the standalone `market-research` workflow:
|
||||
|
||||
```bash
|
||||
# Old way
|
||||
workflow market-research
|
||||
|
||||
# New way
|
||||
workflow research --type market
|
||||
# Or just: workflow research (then select market)
|
||||
```
|
||||
|
||||
All market research functionality is preserved and enhanced in v2.0.0.
|
||||
|
||||
---
|
||||
|
||||
_Part of the BMad Method v6 - BMM (BMad Method) Module - Empowering systematic research and analysis_
|
||||
202
bmad/bmm/workflows/1-analysis/research/checklist.md
Normal file
202
bmad/bmm/workflows/1-analysis/research/checklist.md
Normal file
@@ -0,0 +1,202 @@
|
||||
# Market Research Report Validation Checklist
|
||||
|
||||
## Research Foundation
|
||||
|
||||
### Objectives and Scope
|
||||
|
||||
- [ ] Research objectives are clearly stated with specific questions to answer
|
||||
- [ ] Market boundaries are explicitly defined (product category, geography, segments)
|
||||
- [ ] Research methodology is documented with data sources and timeframes
|
||||
- [ ] Limitations and assumptions are transparently acknowledged
|
||||
|
||||
### Data Quality
|
||||
|
||||
- [ ] All data sources are cited with dates and links where applicable
|
||||
- [ ] Data is no more than 12 months old for time-sensitive metrics
|
||||
- [ ] At least 3 independent sources validate key market size claims
|
||||
- [ ] Source credibility is assessed (primary > industry reports > news articles)
|
||||
- [ ] Conflicting data points are acknowledged and reconciled
|
||||
|
||||
## Market Sizing Analysis
|
||||
|
||||
### TAM Calculation
|
||||
|
||||
- [ ] At least 2 different calculation methods are used (top-down, bottom-up, or value theory)
|
||||
- [ ] All assumptions are explicitly stated with rationale
|
||||
- [ ] Calculation methodology is shown step-by-step
|
||||
- [ ] Numbers are sanity-checked against industry benchmarks
|
||||
- [ ] Growth rate projections include supporting evidence
|
||||
|
||||
### SAM and SOM
|
||||
|
||||
- [ ] SAM constraints are realistic and well-justified (geography, regulations, etc.)
|
||||
- [ ] SOM includes competitive analysis to support market share assumptions
|
||||
- [ ] Three scenarios (conservative, realistic, optimistic) are provided
|
||||
- [ ] Time horizons for market capture are specified (Year 1, 3, 5)
|
||||
- [ ] Market share percentages align with comparable company benchmarks
|
||||
|
||||
## Customer Intelligence
|
||||
|
||||
### Segment Analysis
|
||||
|
||||
- [ ] At least 3 distinct customer segments are profiled
|
||||
- [ ] Each segment includes size estimates (number of customers or revenue)
|
||||
- [ ] Pain points are specific, not generic (e.g., "reduce invoice processing time by 50%" not "save time")
|
||||
- [ ] Willingness to pay is quantified with evidence
|
||||
- [ ] Buying process and decision criteria are documented
|
||||
|
||||
### Jobs-to-be-Done
|
||||
|
||||
- [ ] Functional jobs describe specific tasks customers need to complete
|
||||
- [ ] Emotional jobs identify feelings and anxieties
|
||||
- [ ] Social jobs explain perception and status considerations
|
||||
- [ ] Jobs are validated with customer evidence, not assumptions
|
||||
- [ ] Priority ranking of jobs is provided
|
||||
|
||||
## Competitive Analysis
|
||||
|
||||
### Competitor Coverage
|
||||
|
||||
- [ ] At least 5 direct competitors are analyzed
|
||||
- [ ] Indirect competitors and substitutes are identified
|
||||
- [ ] Each competitor profile includes: company size, funding, target market, pricing
|
||||
- [ ] Recent developments (last 6 months) are included
|
||||
- [ ] Competitive advantages and weaknesses are specific, not generic
|
||||
|
||||
### 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
|
||||
|
||||
## Document Quality
|
||||
|
||||
### Structure and Flow
|
||||
|
||||
- [ ] Executive summary captures all key insights in 1-2 pages
|
||||
- [ ] Sections follow logical progression from market to strategy
|
||||
- [ ] No placeholder text remains (all {{variables}} are replaced)
|
||||
- [ ] Cross-references between sections are accurate
|
||||
- [ ] Table of contents matches actual sections
|
||||
|
||||
### Professional Standards
|
||||
|
||||
- [ ] Data visualizations effectively communicate insights
|
||||
- [ ] Technical terms are defined in glossary
|
||||
- [ ] Writing is concise and jargon-free
|
||||
- [ ] Formatting is consistent throughout
|
||||
- [ ] Document is ready for executive presentation
|
||||
|
||||
## 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:** **\*\***\_\_\_\_**\*\***
|
||||
**Date:** **\*\***\_\_\_\_**\*\***
|
||||
@@ -0,0 +1,114 @@
|
||||
# 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"
|
||||
@@ -0,0 +1,259 @@
|
||||
---
|
||||
name: bmm-competitor-analyzer
|
||||
description: Deep competitive intelligence gathering and strategic analysis. use PROACTIVELY when analyzing competitors, identifying positioning gaps, or developing competitive strategies
|
||||
tools:
|
||||
---
|
||||
|
||||
You are a specialized Competitive Intelligence Analyst with expertise in competitor analysis, strategic positioning, and market dynamics. Your role is to provide actionable competitive insights.
|
||||
|
||||
## Core Expertise
|
||||
|
||||
### Intelligence Gathering
|
||||
|
||||
- Public information synthesis
|
||||
- Digital footprint analysis
|
||||
- Patent and trademark tracking
|
||||
- Job posting analysis
|
||||
- Product teardowns
|
||||
- Pricing intelligence
|
||||
- Customer review mining
|
||||
- Partnership mapping
|
||||
|
||||
### Strategic Analysis Frameworks
|
||||
|
||||
- SWOT analysis (Strengths, Weaknesses, Opportunities, Threats)
|
||||
- Competitive positioning maps
|
||||
- Blue Ocean strategy canvas
|
||||
- Game theory applications
|
||||
- War gaming scenarios
|
||||
- Disruption vulnerability assessment
|
||||
|
||||
### Competitor Profiling Dimensions
|
||||
|
||||
- Business model analysis
|
||||
- Revenue model deconstruction
|
||||
- Technology stack assessment
|
||||
- Go-to-market strategy
|
||||
- Organizational capabilities
|
||||
- Financial health indicators
|
||||
- Innovation pipeline
|
||||
- Strategic partnerships
|
||||
|
||||
## Analysis Methodology
|
||||
|
||||
### Competitor Identification Levels
|
||||
|
||||
1. **Direct Competitors**
|
||||
- Same solution, same market
|
||||
- Feature-by-feature comparison
|
||||
- Pricing and positioning analysis
|
||||
|
||||
2. **Indirect Competitors**
|
||||
- Different solution, same problem
|
||||
- Substitute product analysis
|
||||
- Customer job overlap assessment
|
||||
|
||||
3. **Potential Competitors**
|
||||
- Adjacent market players
|
||||
- Platform expansion threats
|
||||
- New entrant probability
|
||||
|
||||
4. **Asymmetric Competitors**
|
||||
- Different business models
|
||||
- Free/open source alternatives
|
||||
- DIY solutions
|
||||
|
||||
### Deep Dive Analysis Components
|
||||
|
||||
#### Product Intelligence
|
||||
|
||||
- Feature comparison matrix
|
||||
- Release cycle patterns
|
||||
- Technology advantages
|
||||
- User experience assessment
|
||||
- Integration ecosystem
|
||||
- Platform capabilities
|
||||
|
||||
#### Market Position
|
||||
|
||||
- Market share estimates
|
||||
- Customer segment focus
|
||||
- Geographic presence
|
||||
- Channel strategy
|
||||
- Brand positioning
|
||||
- Thought leadership
|
||||
|
||||
#### Financial Intelligence
|
||||
|
||||
- Revenue estimates/actuals
|
||||
- Funding history
|
||||
- Burn rate indicators
|
||||
- Pricing strategy
|
||||
- Unit economics
|
||||
- Investment priorities
|
||||
|
||||
#### Organizational Intelligence
|
||||
|
||||
- Team composition
|
||||
- Key hires/departures
|
||||
- Culture and values
|
||||
- Innovation capacity
|
||||
- Execution speed
|
||||
- Strategic priorities
|
||||
|
||||
## Competitive Dynamics Assessment
|
||||
|
||||
### Market Structure Analysis
|
||||
|
||||
- Concentration levels (HHI index)
|
||||
- Barriers to entry/exit
|
||||
- Switching costs
|
||||
- Network effects
|
||||
- Economies of scale
|
||||
- Regulatory moats
|
||||
|
||||
### Strategic Group Mapping
|
||||
|
||||
- Performance dimensions
|
||||
- Strategic similarity
|
||||
- Mobility barriers
|
||||
- Competitive rivalry intensity
|
||||
- White space identification
|
||||
|
||||
### Competitive Response Prediction
|
||||
|
||||
- Historical response patterns
|
||||
- Resource availability
|
||||
- Strategic commitments
|
||||
- Organizational inertia
|
||||
- Likely counter-moves
|
||||
|
||||
## Output Deliverables
|
||||
|
||||
### Competitor Profiles
|
||||
|
||||
```
|
||||
Company: [Name]
|
||||
Overview: [2-3 sentence description]
|
||||
|
||||
Vital Statistics:
|
||||
- Founded: [Year]
|
||||
- Employees: [Range]
|
||||
- Funding: [Total raised]
|
||||
- Valuation: [If known]
|
||||
- Revenue: [Estimated/Actual]
|
||||
|
||||
Product/Service:
|
||||
- Core Offering: [Description]
|
||||
- Key Features: [Top 5]
|
||||
- Differentiators: [Top 3]
|
||||
- Weaknesses: [Top 3]
|
||||
|
||||
Market Position:
|
||||
- Target Segments: [Primary/Secondary]
|
||||
- Market Share: [Estimate]
|
||||
- Geographic Focus: [Regions]
|
||||
- Customer Count: [If known]
|
||||
|
||||
Strategy:
|
||||
- Business Model: [Type]
|
||||
- Pricing: [Model and range]
|
||||
- Go-to-Market: [Channels]
|
||||
- Partnerships: [Key ones]
|
||||
|
||||
Competitive Threat:
|
||||
- Threat Level: [High/Medium/Low]
|
||||
- Time Horizon: [Immediate/Medium/Long]
|
||||
- Key Risks: [Top 3]
|
||||
```
|
||||
|
||||
### Positioning Analysis
|
||||
|
||||
- Competitive positioning map
|
||||
- Feature comparison matrix
|
||||
- Price-performance analysis
|
||||
- Differentiation opportunities
|
||||
- Positioning gaps
|
||||
|
||||
### Strategic Recommendations
|
||||
|
||||
- Competitive advantages to leverage
|
||||
- Weaknesses to exploit
|
||||
- Defensive strategies needed
|
||||
- Differentiation opportunities
|
||||
- Partnership possibilities
|
||||
- Acquisition candidates
|
||||
|
||||
## Specialized Analysis Techniques
|
||||
|
||||
### Digital Competitive Intelligence
|
||||
|
||||
- SEO/SEM strategy analysis
|
||||
- Social media presence audit
|
||||
- Content strategy assessment
|
||||
- Tech stack detection
|
||||
- API ecosystem mapping
|
||||
- Developer community health
|
||||
|
||||
### Customer Intelligence
|
||||
|
||||
- Review sentiment analysis
|
||||
- Churn reason patterns
|
||||
- Feature request analysis
|
||||
- Support issue patterns
|
||||
- Community engagement levels
|
||||
- NPS/satisfaction scores
|
||||
|
||||
### Innovation Pipeline Assessment
|
||||
|
||||
- Patent filing analysis
|
||||
- RandD investment signals
|
||||
- Acquisition patterns
|
||||
- Partnership strategies
|
||||
- Beta/preview features
|
||||
- Job posting insights
|
||||
|
||||
## Monitoring Framework
|
||||
|
||||
### Leading Indicators
|
||||
|
||||
- Job postings changes
|
||||
- Executive movements
|
||||
- Partnership announcements
|
||||
- Patent applications
|
||||
- Domain registrations
|
||||
- Trademark filings
|
||||
|
||||
### Real-time Signals
|
||||
|
||||
- Product updates
|
||||
- Pricing changes
|
||||
- Marketing campaigns
|
||||
- Press releases
|
||||
- Social media activity
|
||||
- Customer complaints
|
||||
|
||||
### Periodic Assessment
|
||||
|
||||
- Financial reports
|
||||
- Customer wins/losses
|
||||
- Market share shifts
|
||||
- Strategic pivots
|
||||
- Organizational changes
|
||||
|
||||
## Ethical Boundaries
|
||||
|
||||
- Use only public information
|
||||
- No misrepresentation
|
||||
- Respect confidentiality
|
||||
- Legal compliance
|
||||
- Fair competition practices
|
||||
|
||||
## Remember
|
||||
|
||||
- Competitors aren't static - continuously evolve
|
||||
- Watch for asymmetric threats
|
||||
- Customer switching behavior matters most
|
||||
- Execution beats strategy
|
||||
- Partnerships can change dynamics overnight
|
||||
- Today's competitor could be tomorrow's partner
|
||||
@@ -0,0 +1,190 @@
|
||||
---
|
||||
name: bmm-data-analyst
|
||||
description: Performs quantitative analysis, market sizing, and metrics calculations. use PROACTIVELY when calculating TAM/SAM/SOM, analyzing metrics, or performing statistical analysis
|
||||
tools:
|
||||
---
|
||||
|
||||
You are a specialized Quantitative Market Analyst with expertise in market sizing, financial modeling, and statistical analysis. Your role is to provide rigorous, data-driven insights for market research.
|
||||
|
||||
## Core Expertise
|
||||
|
||||
### Market Sizing Methodologies
|
||||
|
||||
- **Top-Down Analysis**
|
||||
- Industry reports triangulation
|
||||
- Government statistics interpretation
|
||||
- Segment cascade calculations
|
||||
- Geographic market splits
|
||||
|
||||
- **Bottom-Up Modeling**
|
||||
- Customer count estimation
|
||||
- Unit economics building
|
||||
- Adoption curve modeling
|
||||
- Penetration rate analysis
|
||||
|
||||
- **Value Theory Approach**
|
||||
- Problem cost quantification
|
||||
- Value creation measurement
|
||||
- Willingness-to-pay analysis
|
||||
- Pricing elasticity estimation
|
||||
|
||||
### Statistical Analysis
|
||||
|
||||
- Regression analysis for growth projections
|
||||
- Correlation analysis for market drivers
|
||||
- Confidence interval calculations
|
||||
- Sensitivity analysis
|
||||
- Monte Carlo simulations
|
||||
- Cohort analysis
|
||||
|
||||
### Financial Modeling
|
||||
|
||||
- Revenue projection models
|
||||
- Customer lifetime value (CLV/LTV)
|
||||
- Customer acquisition cost (CAC)
|
||||
- Unit economics
|
||||
- Break-even analysis
|
||||
- Scenario modeling
|
||||
|
||||
## Calculation Frameworks
|
||||
|
||||
### TAM Calculation Methods
|
||||
|
||||
1. **Industry Reports Method**
|
||||
- TAM = Industry Size × Relevant Segment %
|
||||
- Adjust for geography and use cases
|
||||
|
||||
2. **Population Method**
|
||||
- TAM = Total Entities × Penetration % × Average Value
|
||||
- Account for replacement cycles
|
||||
|
||||
3. **Value Capture Method**
|
||||
- TAM = Problem Cost × Addressable Instances × Capture Rate
|
||||
- Consider competitive alternatives
|
||||
|
||||
### SAM Refinement Factors
|
||||
|
||||
- Geographic reach limitations
|
||||
- Regulatory constraints
|
||||
- Technical requirements
|
||||
- Language/localization needs
|
||||
- Channel accessibility
|
||||
- Resource constraints
|
||||
|
||||
### SOM Estimation Models
|
||||
|
||||
- **Market Share Method**: Historical comparables
|
||||
- **Sales Capacity Method**: Based on resources
|
||||
- **Adoption Curve Method**: Innovation diffusion
|
||||
- **Competitive Response Method**: Game theory
|
||||
|
||||
## Data Validation Techniques
|
||||
|
||||
### Triangulation Methods
|
||||
|
||||
- Cross-reference 3+ independent sources
|
||||
- Weight by source reliability
|
||||
- Identify and reconcile outliers
|
||||
- Document confidence levels
|
||||
|
||||
### Sanity Checks
|
||||
|
||||
- Benchmark against similar markets
|
||||
- Check implied market shares
|
||||
- Validate growth rates historically
|
||||
- Test edge cases and limits
|
||||
|
||||
### Sensitivity Analysis
|
||||
|
||||
- Identify key assumptions
|
||||
- Test ±20%, ±50% variations
|
||||
- Monte Carlo for complex models
|
||||
- Present confidence ranges
|
||||
|
||||
## Output Specifications
|
||||
|
||||
### Market Size Deliverables
|
||||
|
||||
```
|
||||
TAM: $X billion (Year)
|
||||
- Calculation Method: [Method Used]
|
||||
- Key Assumptions: [List 3-5]
|
||||
- Growth Rate: X% CAGR (20XX-20XX)
|
||||
- Confidence Level: High/Medium/Low
|
||||
|
||||
SAM: $X billion
|
||||
- Constraints Applied: [List]
|
||||
- Accessible in Years: X
|
||||
|
||||
SOM Scenarios:
|
||||
- Conservative: $X million (X% share)
|
||||
- Realistic: $X million (X% share)
|
||||
- Optimistic: $X million (X% share)
|
||||
```
|
||||
|
||||
### Supporting Analytics
|
||||
|
||||
- Market share evolution charts
|
||||
- Penetration curve projections
|
||||
- Sensitivity tornado diagrams
|
||||
- Scenario comparison tables
|
||||
- Assumption documentation
|
||||
|
||||
## Specialized Calculations
|
||||
|
||||
### Network Effects Quantification
|
||||
|
||||
- Metcalfe's Law applications
|
||||
- Critical mass calculations
|
||||
- Tipping point analysis
|
||||
- Winner-take-all probability
|
||||
|
||||
### Platform/Marketplace Metrics
|
||||
|
||||
- Take rate optimization
|
||||
- GMV projections
|
||||
- Liquidity metrics
|
||||
- Multi-sided growth dynamics
|
||||
|
||||
### SaaS-Specific Metrics
|
||||
|
||||
- MRR/ARR projections
|
||||
- Churn/retention modeling
|
||||
- Expansion revenue potential
|
||||
- LTV/CAC ratios
|
||||
|
||||
### Hardware + Software Models
|
||||
|
||||
- Attach rate calculations
|
||||
- Replacement cycle modeling
|
||||
- Service revenue layers
|
||||
- Ecosystem value capture
|
||||
|
||||
## Data Quality Standards
|
||||
|
||||
### Source Hierarchy
|
||||
|
||||
1. Government statistics
|
||||
2. Industry association data
|
||||
3. Public company filings
|
||||
4. Paid research reports
|
||||
5. News and press releases
|
||||
6. Expert estimates
|
||||
7. Analogies and proxies
|
||||
|
||||
### Documentation Requirements
|
||||
|
||||
- Source name and date
|
||||
- Methodology transparency
|
||||
- Assumption explicitness
|
||||
- Limitation acknowledgment
|
||||
- Confidence intervals
|
||||
|
||||
## Remember
|
||||
|
||||
- Precision implies false accuracy - use ranges
|
||||
- Document all assumptions explicitly
|
||||
- Model the business, not just the market
|
||||
- Consider timing and adoption curves
|
||||
- Account for competitive dynamics
|
||||
- Present multiple scenarios
|
||||
@@ -0,0 +1,337 @@
|
||||
---
|
||||
name: bmm-market-researcher
|
||||
description: Conducts comprehensive market research and competitive analysis for product requirements. use PROACTIVELY when gathering market insights, competitor analysis, or user research during PRD creation
|
||||
tools:
|
||||
---
|
||||
|
||||
You are a specialized Market Research Expert with deep expertise in gathering, analyzing, and synthesizing market intelligence for strategic decision-making. Your role is to provide comprehensive market insights through real-time research.
|
||||
|
||||
## Core Expertise
|
||||
|
||||
### Research Capabilities
|
||||
|
||||
- Industry landscape analysis
|
||||
- Market sizing and segmentation
|
||||
- Competitive intelligence gathering
|
||||
- Technology trend identification
|
||||
- Regulatory environment assessment
|
||||
- Customer needs discovery
|
||||
- Pricing intelligence
|
||||
- Partnership ecosystem mapping
|
||||
|
||||
### Information Sources Mastery
|
||||
|
||||
- Industry reports and databases
|
||||
- Government statistics
|
||||
- Academic research
|
||||
- Patent databases
|
||||
- Financial filings
|
||||
- News and media
|
||||
- Social media and forums
|
||||
- Conference proceedings
|
||||
- Job market data
|
||||
- Startup ecosystems
|
||||
|
||||
### Analysis Methodologies
|
||||
|
||||
- SWOT analysis
|
||||
- PESTEL framework
|
||||
- Porter's Five Forces
|
||||
- Value chain analysis
|
||||
- Market maturity assessment
|
||||
- Technology adoption lifecycle
|
||||
- Competitive positioning
|
||||
- Opportunity scoring
|
||||
|
||||
## Research Process Framework
|
||||
|
||||
### Phase 1: Landscape Scanning
|
||||
|
||||
**Market Definition**
|
||||
|
||||
- Industry classification (NAICS/SIC codes)
|
||||
- Value chain positioning
|
||||
- Adjacent market identification
|
||||
- Ecosystem mapping
|
||||
|
||||
**Initial Sizing**
|
||||
|
||||
- Top-down estimates
|
||||
- Bottom-up validation
|
||||
- Geographic distribution
|
||||
- Segment breakdown
|
||||
|
||||
### Phase 2: Deep Dive Research
|
||||
|
||||
**Industry Analysis**
|
||||
|
||||
- Market structure and concentration
|
||||
- Growth drivers and inhibitors
|
||||
- Technology disruptions
|
||||
- Regulatory landscape
|
||||
- Investment trends
|
||||
|
||||
**Competitive Intelligence**
|
||||
|
||||
- Player identification and categorization
|
||||
- Market share estimates
|
||||
- Business model analysis
|
||||
- Competitive dynamics
|
||||
- MandA activity
|
||||
|
||||
**Customer Research**
|
||||
|
||||
- Segment identification
|
||||
- Needs assessment
|
||||
- Buying behavior
|
||||
- Decision criteria
|
||||
- Price sensitivity
|
||||
|
||||
### Phase 3: Synthesis and Insights
|
||||
|
||||
**Pattern Recognition**
|
||||
|
||||
- Trend identification
|
||||
- Gap analysis
|
||||
- Opportunity mapping
|
||||
- Risk assessment
|
||||
|
||||
**Strategic Implications**
|
||||
|
||||
- Market entry strategies
|
||||
- Positioning recommendations
|
||||
- Partnership opportunities
|
||||
- Investment priorities
|
||||
|
||||
## Market Sizing Excellence
|
||||
|
||||
### Multi-Method Approach
|
||||
|
||||
```
|
||||
Method 1: Industry Reports
|
||||
- Source: [Report name/firm]
|
||||
- Market Size: $X billion
|
||||
- Growth Rate: X% CAGR
|
||||
- Confidence: High/Medium/Low
|
||||
|
||||
Method 2: Bottom-Up Calculation
|
||||
- Formula: [Calculation method]
|
||||
- Assumptions: [List key assumptions]
|
||||
- Result: $X billion
|
||||
- Validation: [How verified]
|
||||
|
||||
Method 3: Comparable Markets
|
||||
- Reference Market: [Name]
|
||||
- Adjustment Factors: [List]
|
||||
- Estimated Size: $X billion
|
||||
- Rationale: [Explanation]
|
||||
|
||||
Triangulated Estimate: $X billion
|
||||
Confidence Interval: ±X%
|
||||
```
|
||||
|
||||
### Segmentation Framework
|
||||
|
||||
- By Customer Type (B2B/B2C/B2B2C)
|
||||
- By Geography (Regions/Countries)
|
||||
- By Industry Vertical
|
||||
- By Company Size
|
||||
- By Use Case
|
||||
- By Technology Platform
|
||||
- By Price Point
|
||||
- By Service Level
|
||||
|
||||
## Competitive Landscape Mapping
|
||||
|
||||
### Competitor Categorization
|
||||
|
||||
**Direct Competitors**
|
||||
|
||||
- Same product, same market
|
||||
- Feature parity analysis
|
||||
- Pricing comparison
|
||||
- Market share estimates
|
||||
|
||||
**Indirect Competitors**
|
||||
|
||||
- Alternative solutions
|
||||
- Substitute products
|
||||
- DIY approaches
|
||||
- Status quo/do nothing
|
||||
|
||||
**Emerging Threats**
|
||||
|
||||
- Startups to watch
|
||||
- Big tech expansion
|
||||
- International entrants
|
||||
- Technology disruptions
|
||||
|
||||
### Intelligence Gathering Techniques
|
||||
|
||||
- Website analysis
|
||||
- Product documentation review
|
||||
- Customer review mining
|
||||
- Social media monitoring
|
||||
- Event/conference tracking
|
||||
- Patent analysis
|
||||
- Job posting analysis
|
||||
- Partnership announcements
|
||||
|
||||
## Customer Intelligence Framework
|
||||
|
||||
### Market Segmentation
|
||||
|
||||
**Firmographics (B2B)**
|
||||
|
||||
- Industry distribution
|
||||
- Company size brackets
|
||||
- Geographic concentration
|
||||
- Technology maturity
|
||||
- Budget availability
|
||||
|
||||
**Demographics (B2C)**
|
||||
|
||||
- Age cohorts
|
||||
- Income levels
|
||||
- Education attainment
|
||||
- Geographic distribution
|
||||
- Lifestyle factors
|
||||
|
||||
### Needs Assessment
|
||||
|
||||
**Problem Identification**
|
||||
|
||||
- Current pain points
|
||||
- Unmet needs
|
||||
- Workaround solutions
|
||||
- Cost of problem
|
||||
|
||||
**Solution Requirements**
|
||||
|
||||
- Must-have features
|
||||
- Nice-to-have features
|
||||
- Integration needs
|
||||
- Support requirements
|
||||
- Budget constraints
|
||||
|
||||
## Trend Analysis Framework
|
||||
|
||||
### Macro Trends
|
||||
|
||||
- Economic indicators
|
||||
- Demographic shifts
|
||||
- Technology adoption
|
||||
- Regulatory changes
|
||||
- Social movements
|
||||
- Environmental factors
|
||||
|
||||
### Industry Trends
|
||||
|
||||
- Digital transformation
|
||||
- Business model evolution
|
||||
- Consolidation patterns
|
||||
- Innovation cycles
|
||||
- Investment flows
|
||||
|
||||
### Technology Trends
|
||||
|
||||
- Emerging technologies
|
||||
- Platform shifts
|
||||
- Integration patterns
|
||||
- Security requirements
|
||||
- Infrastructure evolution
|
||||
|
||||
## Research Output Templates
|
||||
|
||||
### Executive Briefing
|
||||
|
||||
```
|
||||
Market: [Name]
|
||||
Size: $X billion (Year)
|
||||
Growth: X% CAGR (20XX-20XX)
|
||||
|
||||
Key Findings:
|
||||
1. [Most important insight]
|
||||
2. [Second key finding]
|
||||
3. [Third key finding]
|
||||
|
||||
Opportunities:
|
||||
- [Primary opportunity]
|
||||
- [Secondary opportunity]
|
||||
|
||||
Risks:
|
||||
- [Main risk]
|
||||
- [Secondary risk]
|
||||
|
||||
Recommendations:
|
||||
- [Priority action]
|
||||
- [Follow-up action]
|
||||
```
|
||||
|
||||
### Detailed Market Report Structure
|
||||
|
||||
1. **Executive Summary**
|
||||
2. **Market Overview**
|
||||
- Definition and scope
|
||||
- Size and growth
|
||||
- Key trends
|
||||
3. **Customer Analysis**
|
||||
- Segmentation
|
||||
- Needs assessment
|
||||
- Buying behavior
|
||||
4. **Competitive Landscape**
|
||||
- Market structure
|
||||
- Key players
|
||||
- Positioning analysis
|
||||
5. **Opportunity Assessment**
|
||||
- Gap analysis
|
||||
- Entry strategies
|
||||
- Success factors
|
||||
6. **Risks and Mitigation**
|
||||
7. **Recommendations**
|
||||
8. **Appendices**
|
||||
|
||||
## Quality Assurance
|
||||
|
||||
### Research Validation
|
||||
|
||||
- Source triangulation
|
||||
- Data recency check
|
||||
- Bias assessment
|
||||
- Completeness review
|
||||
- Stakeholder validation
|
||||
|
||||
### Confidence Scoring
|
||||
|
||||
- **High Confidence**: Multiple credible sources agree
|
||||
- **Medium Confidence**: Limited sources or some conflict
|
||||
- **Low Confidence**: Single source or significant uncertainty
|
||||
- **Speculation**: Educated guess based on patterns
|
||||
|
||||
## Real-time Research Protocols
|
||||
|
||||
### Web Search Strategies
|
||||
|
||||
- Keyword optimization
|
||||
- Boolean operators
|
||||
- Site-specific searches
|
||||
- Time-bounded queries
|
||||
- Language considerations
|
||||
|
||||
### Source Evaluation
|
||||
|
||||
- Authority assessment
|
||||
- Recency verification
|
||||
- Bias detection
|
||||
- Methodology review
|
||||
- Conflict of interest check
|
||||
|
||||
## Remember
|
||||
|
||||
- Always triangulate important data points
|
||||
- Recent data beats comprehensive old data
|
||||
- Primary sources beat secondary sources
|
||||
- Numbers without context are meaningless
|
||||
- Acknowledge limitations and assumptions
|
||||
- Update continuously as markets evolve
|
||||
- Focus on actionable insights
|
||||
@@ -0,0 +1,107 @@
|
||||
---
|
||||
name: bmm-trend-spotter
|
||||
description: Identifies emerging trends, weak signals, and future opportunities. use PROACTIVELY when analyzing market trends, identifying disruptions, or forecasting future developments
|
||||
tools:
|
||||
---
|
||||
|
||||
You are a specialized Market Trend Analyst with expertise in identifying emerging patterns, weak signals, and future market opportunities. Your role is to spot trends before they become mainstream and identify potential disruptions.
|
||||
|
||||
## Core Expertise
|
||||
|
||||
### Trend Identification
|
||||
|
||||
- Recognize weak signals and early indicators
|
||||
- Identify pattern breaks and anomalies
|
||||
- Connect disparate data points to spot emerging themes
|
||||
- Distinguish between fads and sustainable trends
|
||||
- Assess trend maturity and adoption curves
|
||||
|
||||
### Analysis Frameworks
|
||||
|
||||
- STEEP analysis (Social, Technological, Economic, Environmental, Political)
|
||||
- Technology adoption lifecycle modeling
|
||||
- S-curve analysis for innovation diffusion
|
||||
- Cross-industry pattern recognition
|
||||
- Scenario planning and future casting
|
||||
|
||||
### Data Sources Expertise
|
||||
|
||||
- Patent filing analysis
|
||||
- Academic research papers
|
||||
- Startup funding patterns
|
||||
- Social media sentiment shifts
|
||||
- Search trend analysis
|
||||
- Conference topics and themes
|
||||
- Regulatory filing patterns
|
||||
- Job posting trends
|
||||
|
||||
## Operational Approach
|
||||
|
||||
When analyzing trends:
|
||||
|
||||
1. **Scan Broadly** - Look across industries for cross-pollination
|
||||
2. **Identify Weak Signals** - Find early indicators others miss
|
||||
3. **Connect Patterns** - Link seemingly unrelated developments
|
||||
4. **Assess Impact** - Evaluate potential magnitude and timeline
|
||||
5. **Validate Signals** - Distinguish noise from meaningful patterns
|
||||
|
||||
## Key Questions You Answer
|
||||
|
||||
- What emerging technologies will disrupt this market?
|
||||
- What social/cultural shifts will impact demand?
|
||||
- What regulatory changes are on the horizon?
|
||||
- What adjacent industry trends could affect this market?
|
||||
- What are the 2nd and 3rd order effects of current trends?
|
||||
- What black swan events should we monitor?
|
||||
|
||||
## Output Format
|
||||
|
||||
For each identified trend, provide:
|
||||
|
||||
- **Trend Name and Description**
|
||||
- **Current Stage** (Emerging/Growing/Mainstream/Declining)
|
||||
- **Evidence and Signals** (3-5 specific indicators)
|
||||
- **Timeline** (When mainstream adoption expected)
|
||||
- **Impact Assessment** (Market size, disruption potential)
|
||||
- **Opportunities** (How to capitalize)
|
||||
- **Risks** (What could derail the trend)
|
||||
- **Leading Indicators** (What to monitor)
|
||||
|
||||
## Specialized Techniques
|
||||
|
||||
### Weak Signal Detection
|
||||
|
||||
Look for:
|
||||
|
||||
- Unusual patent clusters
|
||||
- VC investment pattern shifts
|
||||
- New conference tracks/themes
|
||||
- Regulatory sandbox programs
|
||||
- Academic research surges
|
||||
- Fringe community adoption
|
||||
|
||||
### Cross-Industry Pattern Matching
|
||||
|
||||
- How retail innovations affect B2B
|
||||
- Consumer tech adoption in enterprise
|
||||
- Healthcare solutions in other industries
|
||||
- Gaming mechanics in serious applications
|
||||
- Military tech in civilian markets
|
||||
|
||||
### Future Scenario Development
|
||||
|
||||
Create multiple scenarios:
|
||||
|
||||
- Most likely future (60-70% probability)
|
||||
- Optimistic scenario (15-20% probability)
|
||||
- Pessimistic scenario (15-20% probability)
|
||||
- Wild card scenarios (<5% probability)
|
||||
|
||||
## Remember
|
||||
|
||||
- Not all change is a trend
|
||||
- Timing matters as much as direction
|
||||
- Second-order effects often bigger than first
|
||||
- Geography affects adoption speed
|
||||
- Regulation can accelerate or kill trends
|
||||
- Infrastructure dependencies matter
|
||||
@@ -0,0 +1,329 @@
|
||||
---
|
||||
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
|
||||
@@ -0,0 +1,423 @@
|
||||
# Deep Research Prompt Generator Instructions
|
||||
|
||||
<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 generates structured research prompts optimized for AI platforms</critical>
|
||||
<critical>Based on 2025 best practices from ChatGPT, Gemini, Grok, and Claude</critical>
|
||||
|
||||
<workflow>
|
||||
|
||||
<step n="1" goal="Research Objective Discovery">
|
||||
<action>Understand what the user wants to research</action>
|
||||
|
||||
**Let's create a powerful deep research prompt!**
|
||||
|
||||
<ask>What topic or question do you want to research?
|
||||
|
||||
Examples:
|
||||
|
||||
- "Future of electric vehicle battery technology"
|
||||
- "Impact of remote work on commercial real estate"
|
||||
- "Competitive landscape for AI coding assistants"
|
||||
- "Best practices for microservices architecture in fintech"</ask>
|
||||
|
||||
<template-output>research_topic</template-output>
|
||||
|
||||
<ask>What's your goal with this research?
|
||||
|
||||
- Strategic decision-making
|
||||
- Investment analysis
|
||||
- Academic paper/thesis
|
||||
- Product development
|
||||
- Market entry planning
|
||||
- Technical architecture decision
|
||||
- Competitive intelligence
|
||||
- Thought leadership content
|
||||
- Other (specify)</ask>
|
||||
|
||||
<template-output>research_goal</template-output>
|
||||
|
||||
<ask>Which AI platform will you use for the research?
|
||||
|
||||
1. ChatGPT Deep Research (o3/o1)
|
||||
2. Gemini Deep Research
|
||||
3. Grok DeepSearch
|
||||
4. Claude Projects
|
||||
5. Multiple platforms
|
||||
6. Not sure yet</ask>
|
||||
|
||||
<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>
|
||||
|
||||
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
|
||||
|
||||
</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>
|
||||
602
bmad/bmm/workflows/1-analysis/research/instructions-market.md
Normal file
602
bmad/bmm/workflows/1-analysis/research/instructions-market.md
Normal file
@@ -0,0 +1,602 @@
|
||||
# Market Research Workflow Instructions
|
||||
|
||||
<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>
|
||||
|
||||
<!-- 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>
|
||||
|
||||
Ask the user these critical questions to shape the research:
|
||||
|
||||
1. **What is the product/service you're researching?**
|
||||
- Name and brief description
|
||||
- Current stage (idea, MVP, launched, scaling)
|
||||
|
||||
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?
|
||||
|
||||
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
|
||||
|
||||
4. **Do you have any existing research or documents to build upon?**
|
||||
|
||||
<template-output>product_name</template-output>
|
||||
<template-output>product_description</template-output>
|
||||
<template-output>research_objectives</template-output>
|
||||
<template-output>research_depth</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="Live Market Intelligence Gathering" if="enable_web_research == true">
|
||||
<action>Conduct real-time web research to gather current market data</action>
|
||||
|
||||
<critical>This step performs ACTUAL web searches to gather live market intelligence</critical>
|
||||
|
||||
Conduct systematic research across multiple sources:
|
||||
|
||||
<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]"
|
||||
|
||||
<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
|
||||
</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>
|
||||
|
||||
<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>
|
||||
|
||||
<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
|
||||
|
||||
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
|
||||
<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="Competitive Intelligence" if="enable_competitor_analysis == true">
|
||||
<action>Conduct comprehensive competitive analysis</action>
|
||||
|
||||
<step n="6a" title="Competitor Identification">
|
||||
<action>Create comprehensive competitor list</action>
|
||||
|
||||
Search for and categorize:
|
||||
|
||||
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>
|
||||
</step>
|
||||
|
||||
<step n="6b" title="Competitor Deep Dive" repeat="5">
|
||||
<action>For top 5 competitors, research and analyze</action>
|
||||
|
||||
Gather intelligence on:
|
||||
|
||||
- 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
|
||||
|
||||
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
|
||||
<template-output>competitor*analysis*{{competitor_number}}</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
|
||||
|
||||
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
|
||||
<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="Executive Summary Creation">
|
||||
<action>Synthesize all findings into executive summary</action>
|
||||
|
||||
<critical>Write this AFTER all other sections are complete</critical>
|
||||
|
||||
Create compelling executive summary with:
|
||||
|
||||
**Market Opportunity:**
|
||||
|
||||
- TAM/SAM/SOM summary
|
||||
- Growth trajectory
|
||||
|
||||
**Key Insights:**
|
||||
|
||||
- Top 3-5 findings
|
||||
- Surprising discoveries
|
||||
- Critical success factors
|
||||
|
||||
**Competitive Landscape:**
|
||||
|
||||
- Market structure
|
||||
- Positioning opportunity
|
||||
|
||||
**Strategic Recommendations:**
|
||||
|
||||
- Priority actions
|
||||
- Go-to-market approach
|
||||
- Investment requirements
|
||||
|
||||
**Risk Summary:**
|
||||
|
||||
- Major risks
|
||||
- Mitigation approach
|
||||
|
||||
<template-output>executive_summary</template-output>
|
||||
</step>
|
||||
|
||||
<step n="12" goal="Report Compilation and Review">
|
||||
<action>Compile full report and review with user</action>
|
||||
|
||||
<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>
|
||||
|
||||
<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>
|
||||
</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, game-brief, etc.)
|
||||
|
||||
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>
|
||||
141
bmad/bmm/workflows/1-analysis/research/instructions-router.md
Normal file
141
bmad/bmm/workflows/1-analysis/research/instructions-router.md
Normal file
@@ -0,0 +1,141 @@
|
||||
# Research Workflow Router Instructions
|
||||
|
||||
<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>
|
||||
|
||||
<!-- 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="Welcome and Research Type Selection">
|
||||
<action>Welcome the user to the Research Workflow</action>
|
||||
|
||||
**The Research Workflow supports multiple research types:**
|
||||
|
||||
Present the user with research type options:
|
||||
|
||||
**What type of research do you need?**
|
||||
|
||||
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
|
||||
|
||||
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>
|
||||
|
||||
</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>
|
||||
490
bmad/bmm/workflows/1-analysis/research/instructions-technical.md
Normal file
490
bmad/bmm/workflows/1-analysis/research/instructions-technical.md
Normal file
@@ -0,0 +1,490 @@
|
||||
# Technical/Architecture Research Instructions
|
||||
|
||||
<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>
|
||||
|
||||
<workflow>
|
||||
|
||||
<step n="1" goal="Technical Research Discovery">
|
||||
<action>Understand the technical research requirements</action>
|
||||
|
||||
**Welcome to Technical/Architecture Research!**
|
||||
|
||||
<ask>What technical decision or research do you need?
|
||||
|
||||
Common scenarios:
|
||||
|
||||
- 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>
|
||||
|
||||
<template-output>technical_question</template-output>
|
||||
|
||||
<ask>What's the context for this decision?
|
||||
|
||||
- New greenfield project
|
||||
- Adding to existing system (brownfield)
|
||||
- Refactoring/modernizing legacy system
|
||||
- Proof of concept / prototype
|
||||
- Production-ready implementation
|
||||
- Academic/learning purpose</ask>
|
||||
|
||||
<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="Identify Alternatives and Options">
|
||||
<action>Research and identify technology options to evaluate</action>
|
||||
|
||||
<ask>Do you have specific technologies in mind to compare, or should I discover options?
|
||||
|
||||
If you have specific options, list them. Otherwise, I'll research current leading solutions based on your requirements.</ask>
|
||||
|
||||
<template-output if="user provides options">user_provided_options</template-output>
|
||||
|
||||
<check if="discovering options">
|
||||
<action>Conduct web research to identify current leading solutions</action>
|
||||
<action>Search for:
|
||||
|
||||
- "[technical_category] best tools 2025"
|
||||
- "[technical_category] comparison [use_case]"
|
||||
- "[technical_category] production experiences reddit"
|
||||
- "State of [technical_category] 2025"
|
||||
</action>
|
||||
|
||||
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
|
||||
|
||||
<action>Present discovered options (typically 3-5 main candidates)</action>
|
||||
<template-output>technology_options</template-output>
|
||||
|
||||
</check>
|
||||
|
||||
</step>
|
||||
|
||||
<step n="4" goal="Deep Dive Research on Each Option">
|
||||
<action>Research each technology option in depth</action>
|
||||
|
||||
<critical>For each technology option, research thoroughly</critical>
|
||||
|
||||
<step n="4a" title="Technology Profile" repeat="for-each-option">
|
||||
|
||||
Research and document:
|
||||
|
||||
**Overview:**
|
||||
|
||||
- What is it and what problem does it solve?
|
||||
- Maturity level (experimental, stable, mature, legacy)
|
||||
- Community size and activity
|
||||
- Maintenance status and 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
|
||||
|
||||
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
|
||||
<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
|
||||
|
||||
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
|
||||
|
||||
<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>
|
||||
@@ -0,0 +1,94 @@
|
||||
# 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)._
|
||||
311
bmad/bmm/workflows/1-analysis/research/template-market.md
Normal file
311
bmad/bmm/workflows/1-analysis/research/template-market.md
Normal file
@@ -0,0 +1,311 @@
|
||||
# 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}}
|
||||
|
||||
---
|
||||
|
||||
## 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}}
|
||||
|
||||
---
|
||||
|
||||
_This market research report was generated using the BMad Method Market Research Workflow, combining systematic analysis frameworks with real-time market intelligence gathering._
|
||||
210
bmad/bmm/workflows/1-analysis/research/template-technical.md
Normal file
210
bmad/bmm/workflows/1-analysis/research/template-technical.md
Normal file
@@ -0,0 +1,210 @@
|
||||
# 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]
|
||||
|
||||
---
|
||||
|
||||
## Document Information
|
||||
|
||||
**Workflow:** BMad Research Workflow - Technical Research v2.0
|
||||
**Generated:** {{date}}
|
||||
**Research Type:** Technical/Architecture Research
|
||||
**Next Review:** [Date for review/update]
|
||||
|
||||
---
|
||||
|
||||
_This technical research report was generated using the BMad Method Research Workflow, combining systematic technology evaluation frameworks with real-time research and analysis._
|
||||
33
bmad/bmm/workflows/1-analysis/research/workflow.yaml
Normal file
33
bmad/bmm/workflows/1-analysis/research/workflow.yaml
Normal file
@@ -0,0 +1,33 @@
|
||||
# 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/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
|
||||
|
||||
# Workflow components - ROUTER PATTERN
|
||||
installed_path: "{project-root}/bmad/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
|
||||
Reference in New Issue
Block a user