| name | research |
| mode | agent |
| description | Conduct systematic multi-phase research on a topic and produce a documented findings report |
| argument-hint | [topic] |
Research
Overview
Conduct systematic research on a topic using structured phases that build upon each other, creating actionable todos and leveraging web search capabilities. Produces a documented research report in .code-captain/research/.
When to Use
- Investigating new technologies, frameworks, or tools
- Understanding problem domains before solution design
- Competitive analysis and market research
- Technical feasibility studies
- Learning about best practices in unfamiliar areas
Process
Phase 1: Define Research Scope
Objective: Establish clear research boundaries and questions
Actions:
- Create todos for the research phases using
TodoWrite:
- Phase 1: Define scope and questions [in_progress]
- Phase 2: Initial discovery [pending]
- Phase 3: Deep dive analysis [pending]
- Phase 4: Synthesis and recommendations [pending]
- Define primary research question(s) based on the provided topic
- Identify key stakeholders and their information needs
- Set success criteria for the research
Phase 2: Initial Discovery
Objective: Gather broad understanding of the topic landscape
Actions:
- Use
WebSearch with broad search terms related to the topic
- Search for:
- Overview articles and introductory content
- Current trends and recent developments
- Key players and thought leaders
- Common terminology and concepts
- Document initial findings and emerging themes
- Identify knowledge gaps that need deeper investigation
- Update
TodoWrite: mark Phase 2 in_progress
Search Strategy:
- Start with general terms: "[topic] overview", "[topic] 2024", "[topic] trends"
- Look for authoritative sources: documentation, whitepapers, industry reports
- Note recurring themes and terminology for Phase 3
Phase 3: Deep Dive Analysis
Objective: Investigate specific aspects identified in Phase 2
Actions:
- Use
WebSearch with specific, targeted queries based on Phase 2 findings
- Research specific sub-topics:
- Technical implementation details
- Pros and cons of different approaches
- Real-world case studies and examples
- Performance metrics and benchmarks
- Compare alternatives and trade-offs
- Validate claims from multiple sources
- Update
TodoWrite: mark Phase 3 in_progress
Search Strategy:
- Use specific terminology discovered in Phase 2
- Search for: "[specific approach] vs [alternative]", "[topic] case study", "[topic] performance"
- Look for criticism and limitations, not just benefits
Phase 4: Synthesis and Recommendations
Objective: Transform research into actionable insights and document findings
Actions:
- Synthesize findings into key insights
- Create recommendations based on research
- Identify next steps or areas requiring further investigation
- Document sources and evidence for claims
- Get current date:
date +%Y-%m-%d
- Create research document using
Write: .code-captain/research/[DATE]-[topic-name]-research.md
- Update
TodoWrite: mark all phases complete
Deliverables:
- Executive summary of key findings
- Pros/cons analysis of options
- Specific recommendations with rationale
- Risk assessment and mitigation strategies
- Further research needs
- Research document:
.code-captain/research/[DATE]-[topic-name]-research.md
Research Document Template
Create the file at .code-captain/research/[YYYY-MM-DD]-[topic-name]-research.md:
# [Topic Name] Research
**Date:** [YYYY-MM-DD]
**Status:** Complete
## Research Question(s)
[Primary questions this research aimed to answer]
## Executive Summary
[2-3 paragraph overview of key findings and recommendations]
## Background & Context
[Why this research was needed, current situation, stakeholders involved]
## Methodology
[How the research was conducted, sources used, timeframe]
## Key Findings
### Finding 1: [Title]
- **Evidence:** [Supporting data/sources]
- **Implications:** [What this means for the project/decision]
### Finding 2: [Title]
- **Evidence:** [Supporting data/sources]
- **Implications:** [What this means for the project/decision]
## Options Analysis
### Option 1: [Name]
- **Pros:** [Benefits and advantages]
- **Cons:** [Drawbacks and limitations]
- **Cost/Effort:** [Implementation requirements]
- **Risk Level:** [High/Medium/Low with explanation]
### Option 2: [Name]
- **Pros:** [Benefits and advantages]
- **Cons:** [Drawbacks and limitations]
- **Cost/Effort:** [Implementation requirements]
- **Risk Level:** [High/Medium/Low with explanation]
## Recommendations
### Primary Recommendation
[Specific recommended course of action with rationale]
### Alternative Approaches
[Secondary options if primary recommendation isn't feasible]
### Implementation Considerations
[Key factors to consider when moving forward]
## Risks & Mitigation
- **Risk 1:** [Description] → **Mitigation:** [How to address]
- **Risk 2:** [Description] → **Mitigation:** [How to address]
## Further Research Needed
- [Question/area that needs additional investigation]
## Sources
- [Source 1 with URL and access date]
- [Source 2 with URL and access date]
## Appendix
[Additional detailed information, raw data, extended quotes, etc.]
Output Summary
At the end, present a summary in chat:
- Research Question(s): [What you set out to learn]
- Key Findings: [3-5 bullet points of most important discoveries]
- Recommendations: [Actionable next steps based on research]
- Document saved:
.code-captain/research/[DATE]-[topic-name]-research.md
Best Practices
Search Strategy
- Start broad, then narrow down
- Use multiple search terms and phrasings
- Look for recent content (last 1-2 years) for rapidly evolving topics
- Cross-reference information from multiple sources
- Search for both benefits AND criticisms
Critical Thinking
- Question assumptions and biases in sources
- Look for evidence, not just opinions
- Consider the source's credibility and potential conflicts of interest
- Distinguish between correlation and causation
- Identify what information is missing
Common Pitfalls to Avoid
- Confirmation bias (only seeking information that supports preconceived notions)
- Stopping research too early when findings seem obvious
- Not considering implementation challenges
- Ignoring edge cases or limitations
- Failing to consider stakeholder perspectives beyond your own