tonitangpotato/rustclaw/research

# Research: {feature-name}
 
## Executive Summary
2-3 sentence overview of findings and recommendation.
 
## Competitive Landscape
 
### {Competitor 1}
-**URL**: 
-**What it does**: 
-**Key features**: 
-**Strengths**: 
-**Weaknesses**: 
-**Pricing**: (if applicable)
-**User sentiment**: (from reviews, forums, etc.)
 
### {Competitor 2}
...
 
### Competitive Matrix
| Feature | Us (planned) | Competitor 1 | Competitor 2 |
|---------|--------------|--------------|--------------|
| ...     | ...          | ...          | ...          |
 
## Technical Approaches
 
### Option A: {approach name}
-**Description**: 
-**Pros**: 
-**Cons**: 
-**Effort estimate**: 
-**Key libraries/dependencies**: 
 
### Option B: {approach name}
...
 
### Technical Recommendation
Which approach to use and why.
 
## Market Signals
 
### User Demand Evidence
-Forum discussions, Reddit threads, HN comments
-GitHub issues/stars on related projects
-Search volume trends (if available)
 
### Pain Points Found
-What problems users are reporting
-What's missing in existing solutions
 
### Market Size Indicators
-Target audience size estimates
-Growth trends in the space
 
## Prior Art
 
### Open Source Projects
-Relevant repos with brief assessment
 
### Academic Papers / Blog Posts
-Key technical resources that inform the design
 
### Lessons Learned from Others
-What worked/failed for similar projects
 
## Key Insights
 
1.**Insight 1**: [actionable takeaway]
2.**Insight 2**: [actionable takeaway]
3.**Insight 3**: [actionable takeaway]
4.**Insight 4**: [actionable takeaway]
5.**Insight 5**: [actionable takeaway]
 
## Recommendation
 
### Go / No-Go Assessment
**Recommendation**: [GO / NO-GO / PIVOT]
 
**Reasoning**:
-[Key factor 1]
-[Key factor 2]
-[Key factor 3]
 
### If GO, Key Success Factors
-What must be true for this to succeed
-What differentiates us from competition
 
### If NO-GO, Alternatives
-What should we do instead

→ find . -type f \( -name "*.rs" -o -name "*.ts" -o -name "*.py" \) | xargs grep -li "{feature_keywords}" 2>/dev/null
→ find . -path "*/packages/*" -o -path "*/crates/*" -o -path "*/src/*" | grep -i "{feature_name}"
→ Check if implementation already exists under a different name/path
→ If files found:
   - Read them to understand what's already built
   - Document in research output: "## Existing Implementation" section
   - Assess: is this task already done? partially done? needs different approach?
   - If fully implemented: STOP research, report "already exists at {path}"
→ If nothing found: proceed to Step 1

→ web_search("{feature} alternatives")
→ web_search("{feature} competitors")
→ web_search("{feature} open source")
→ For each competitor found:
   → web_fetch(competitor_url) to understand features
   → web_search("{competitor} reviews") for user sentiment

→ web_search("{feature} implementation")
→ web_search("{feature} architecture")
→ web_search("{feature} rust library" or "{feature} python library")
→ Check GitHub trending/search for relevant projects
→ Evaluate feasibility based on existing tools/libraries

→ web_search("{feature} demand")
→ web_search("{feature} reddit" or "{feature} hacker news")
→ web_search("{feature} problems" or "{feature} pain points")
→ Look for patterns in user complaints/requests

→ web_search("{feature} paper" or "{feature} research")
→ web_search("{feature} blog post" or "{feature} tutorial")
→ GitHub search for related projects, check their issues/discussions

→ Compile findings into structured document
→ Identify patterns across sources
→ Make go/no-go recommendation with clear reasoning
→ If GO, identify key differentiators and success factors