LogoCocode Skills

Research Report: {{research_topic}}

Creative Intelligence로서 **리서치** 워크플로우를 실행합니다.

Creative Intelligence로서 리서치 워크플로우를 실행합니다.

Workflow Overview#

Goal: Conduct comprehensive research and provide actionable insights

Phase: Cross-phase (supports all BMAD phases)

Agent: Creative Intelligence

Inputs: Research topic, research type, specific questions

Output: Structured research report with findings, analysis, and recommendations

Duration: 30-90 minutes


Pre-Flight#

  1. Load context per helpers.md#Combined-Config-Load
  2. Explain purpose:

    "I'll conduct comprehensive research on your topic. This produces a structured report with findings, competitive analysis (if applicable), and actionable recommendations."


Research Process#

Use TodoWrite to track: Define Scope → Select Research Type → Gather Information → Analyze Findings → Create Competitive Matrix → Extract Insights → Generate Report → Update Status


Part 1: Define Research Scope#

Ask user:

Q1: Research Topic

"What are we researching?"

Examples:

  • Market size for fitness apps
  • Competitors in project management space
  • Best practices for authentication
  • User needs for accessibility features
  • Technology options for real-time features

Store as: ``

Q2: Research Type

"What type of research?"

Options:

  1. Market Research - Market size, trends, growth, customer segments
  2. Competitive Research - Competitors, features, positioning, gaps
  3. Technical Research - Technologies, frameworks, best practices, patterns
  4. User Research - User needs, pain points, behaviors, journeys
  5. Mixed - Combination of above

Store as: ``

Q3: Specific Questions

"What specific questions should this research answer?"

List 3-7 key questions to guide research.

Store as: ``

Q4: Constraints

"Any constraints or focus areas?"

Examples:

  • Geographic region (US market only)
  • Industry segment (B2B SaaS)
  • Technology stack (React ecosystem)
  • Budget range ($0-50K tools)

Store as: ``


Part 2: Select Research Methods#

Based on research type, determine methods:

For Market Research:

  • WebSearch for industry reports, market analysis, trends
  • WebFetch for analyst reports and whitepapers
  • Document secondary research sources
  • Quantify market size, growth rate, segments

For Competitive Research:

  • WebSearch for competitor websites, reviews, comparisons
  • WebFetch for product pages, pricing, documentation
  • Create competitive feature matrix
  • Identify gaps and opportunities

For Technical Research:

  • WebSearch for documentation, tutorials, comparisons
  • WebFetch for official docs, GitHub repos
  • Task tool with Explore subagent for codebase research
  • Evaluate technologies against criteria

For User Research:

  • WebSearch for user forums, reviews, surveys
  • WebFetch for user studies, accessibility guidelines
  • Analyze pain points and needs
  • Map user journeys

Inform user:

"Research approach:

  • Method 1:
  • Method 2:
  • Method 3:

Starting research..."


Part 3: Gather Information#

Execute research using appropriate tools.

Market Research

Use WebSearch for:

- " market size 2025"
- " industry trends"
- " growth projections"
- " customer segments"

Capture:

  • Market size (TAM, SAM, SOM if available)
  • Growth rate (CAGR)
  • Key trends
  • Major players
  • Customer segments
  • Revenue models

Competitive Research

For each competitor (3-7 competitors):

Use WebSearch:

- " features"
- " pricing"
- " reviews"
- " vs alternatives"

Use WebFetch on:

  • Product pages
  • Pricing pages
  • Documentation
  • Feature lists
  • Customer reviews

Capture per competitor:

### 

**Overview:** 
**Target Market:** 
**Pricing:** 
**Key Features:**
- Feature 1
- Feature 2
- Feature 3

**Strengths:**
- Strength 1
- Strength 2

**Weaknesses:**
- Weakness 1
- Weakness 2

**Unique Differentiators:** 

**Source:** 

Technical Research

For each technology/framework:

Use WebSearch:

- " documentation"
- " best practices"
- " vs "
- " performance benchmarks"

Use WebFetch for:

  • Official documentation
  • GitHub repo (stars, issues, activity)
  • Performance comparisons
  • Community size

If researching internal codebase:

  • Use Task tool with Explore subagent
  • Search for usage patterns
  • Identify dependencies
  • Analyze architecture

Capture per technology:

### 

**Purpose:** 
**Maturity:** 
**Community:** 
**Performance:** 

**Pros:**
- Pro 1
- Pro 2

**Cons:**
- Con 1
- Con 2

**Best For:** 
**Avoid If:** 

**Source:** 

User Research

Use WebSearch for:

- " pain points "
- " needs "
- "user reviews "
- "accessibility requirements "

Use WebFetch for:

  • User forums and discussions
  • Product reviews
  • Accessibility guidelines (WCAG, etc.)
  • User research reports

Capture:

  • User personas
  • Pain points
  • Needs and goals
  • Behavior patterns
  • Accessibility requirements
  • User journey insights

Part 4: Analyze Findings#

Synthesize all gathered information.

For each research question from Part 1:

### Q: 

**Answer:** 

**Supporting Evidence:**
- : 
- : 
- : 

**Confidence:** High | Medium | Low
**Gaps:** 

Identify patterns:

  • Common themes across sources
  • Conflicting information (note discrepancies)
  • Gaps in available information
  • Surprising findings

Part 5: Create Competitive Matrix (if applicable)#

If research type is Competitive or Mixed, create feature comparison.

Matrix format:

## Competitive Feature Matrix

| Feature | Our Product | Competitor 1 | Competitor 2 | Competitor 3 |
|---------|-------------|--------------|--------------|--------------|
| Feature 1 | ✓ Planned | ✓ | ✓ | ✗ |
| Feature 2 | ✗ | ✓ | ✗ | ✓ |
| Feature 3 | ✓ Unique | ✗ | ✗ | ✗ |

Legend:
- ✓ = Available
- ✗ = Not available
- ✓ Planned = On roadmap
- ✓ Unique = Our differentiator

Pricing comparison (if applicable):

## Pricing Comparison

| Competitor | Entry Tier | Mid Tier | Enterprise | Notes |
|------------|------------|----------|------------|-------|
| Competitor 1 | $10/mo | $50/mo | Custom | Free tier available |
| Competitor 2 | $0 | $25/mo | $200/mo | Freemium model |
| Competitor 3 | $15/mo | $75/mo | Custom | 14-day trial |

Part 6: Extract Key Insights#

Identify 5-10 actionable insights from research.

Format each insight:

### Insight : 

**Finding:** 

**Implication:** 

**Recommendation:** 

**Priority:** High | Medium | Low

**Supporting Data:** 

Categorize insights:

  • Market insights
  • Competitive insights
  • Technical insights
  • User insights
  • Risk insights
  • Opportunity insights

Part 7: Generate Research Report#

Create research report per helpers.md#Apply-Variables-to-Template

Use template: research-report.md (or generate inline)

Report structure:

# Research Report: 

**Date:** 
**Research Type:** 
**Duration:** 

## Executive Summary



Key findings:
- Finding 1
- Finding 2
- Finding 3

## Research Questions



## Methodology

**Research approach:**
- 
- 
- 

**Sources:**  sources consulted

**Time period:** 

## Findings

### Research Question 1: 


### Research Question 2: 


[All questions...]

## Detailed Analysis


### Market Overview
- Market Size: 
- Growth Rate: 
- Key Trends: 
- Customer Segments: 


### Competitive Landscape


#### Competitor Profiles


#### Competitive Gaps
- Gap 1: 
- Gap 2: 


### Technology Evaluation


#### Recommended Technology Stack
- Technology 1: 
- Technology 2: 


### User Insights
- Pain Points: 
- Needs: 
- Behavior Patterns: 
- Accessibility: 

## Key Insights



## Recommendations

### Immediate Actions (Next 2 weeks)
1. 
2. 

### Short-term (Next 1-3 months)
1. 
2. 

### Long-term (3+ months)
1. 
2. 

## Research Gaps

**What we still don't know:**
- Gap 1: 
- Gap 2: 

**Recommended follow-up research:**
- Follow-up 1
- Follow-up 2

## Sources

1.  - 
2.  - 
3.  - 

[All sources...]

## Appendix



---

*Generated by BMAD Method v6 - Creative Intelligence*
*Research Duration:  minutes*
*Sources Consulted: *

Save to: /research--.md

Inform user:

✓ Research Complete!

Research Type: 
Sources Consulted: 
Key Insights: 

Document: 

Top 3 Insights:
1. 
2. 
3. 

Top Recommendation: 

Update Status#

Per helpers.md#Update-Workflow-Status

Update bmm-workflow-status.yaml:

last_workflow: research
last_workflow_date: 
research:
  reports_completed: 
  last_research_topic: 
  last_research_type: 
  total_sources: 

Recommend Next Steps#

Based on research type and findings:

If Market Research → Business Analyst or Product Manager

Next: Use market insights for product positioning
Run: /product-brief or /prd
Incorporate market trends and customer segments

If Competitive Research → Product Manager

Next: Define competitive differentiation
Run: /prd
Use competitive gaps to inform feature prioritization

If Technical Research → System Architect

Next: Incorporate technology recommendations
Run: /architecture
Use evaluated technologies in system design

If User Research → Product Manager or UX Designer

Next: Create user-centered requirements
Run: /prd or /create-ux-design
Use pain points and needs to inform design

If Research revealed gaps → Creative Intelligence

Next: Conduct follow-up research
Run: /research again with refined questions
Fill knowledge gaps

If Research supports hypothesis → Continue to planning

Next: Move to planning phase
Run: /prd or /tech-spec
Use research insights to inform requirements

Helper References#

  • Load config: helpers.md#Combined-Config-Load
  • Apply template: helpers.md#Apply-Variables-to-Template
  • Save document: helpers.md#Save-Output-Document
  • Update status: helpers.md#Update-Workflow-Status
  • Determine next: helpers.md#Determine-Next-Workflow

Notes for LLMs#

  • Use TodoWrite to track 8 research steps
  • Use appropriate tools: WebSearch (market/competitive), WebFetch (documentation), Task with Explore (codebase)
  • Cite all sources with URLs
  • Quantify findings when possible (market size, feature counts, etc.)
  • Create competitive matrix for competitive research
  • Note confidence level for each finding
  • Identify research gaps and recommend follow-up
  • Extract actionable insights, not just raw data
  • Provide specific recommendations with priorities
  • Use helpers.md references for all common operations
  • Format report for readability (tables, lists, sections)
  • Include executive summary for quick reference
  • Recommend logical next workflow based on research type

Remember: Research should answer specific questions with evidence-based findings and actionable recommendations. Always cite sources and quantify when possible.