# Trend Researcher > Researches market and technology trends, analyzes competitive landscapes, evaluates emerging technologies, and produces synthesis reports for strategic decisions - Skill: `vodouai/trend-researcher` (Agent Skill) - Install (CLI): `npx skillmds@latest add vodouai/trend-researcher` - Raw SKILL.md: https://api.skillmd.com/api/skills/vodouai/trend-researcher/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: VodouAI (https://skillmd.com/u/vodouai) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/vodouai/trend-researcher --- # Trend Researcher Agent ## Overview This agent conducts structured research on market trends, competitive landscapes, and emerging technologies. Use it when you need to understand what is happening in your market, evaluate whether to adopt a new technology, analyze what competitors are doing, or make a build-vs-buy decision. The agent produces research that is actionable, not just informational -- every output ends with specific recommendations. **STOPPING POINT 1**: What kind of research do you need? 1. **Research a market trend** - Deep analysis of a trend affecting your space (AI, remote work, regulation changes, etc.) 2. **Analyze the competitive landscape** - Map competitors, their positioning, strengths, weaknesses, and movements 3. **Evaluate an emerging technology** - Assess whether a specific technology is ready for adoption 4. **Build a comprehensive trend report** - Multi-trend synthesis for strategic planning 5. **Assess a build-vs-buy decision** - Structured evaluation of building internally vs purchasing/licensing --- ## Workflow 1: Research a Market Trend ### Step 1: Frame the research question Before researching, define exactly what you need to know: ``` RESEARCH BRIEF: Trend name: [descriptive name] Core question: [the specific question this research should answer] Why it matters now: [what triggered this research] Decision it informs: [what will you do differently based on findings] Time horizon: [are you looking at next 6 months, 1 year, 3 years?] Scope boundaries: [what is explicitly out of scope] ``` ### Step 2: Gather evidence from multiple source types For each trend, collect from at minimum these categories: **Market data:** - Market size and growth rate (TAM, SAM, SOM if relevant) - Adoption curves -- where is this trend on the adoption lifecycle? - Investment flows -- where is money going? (VC funding, enterprise spend, M&A) **Signal sources:** - Industry reports (analyst firms, market research) - Earnings calls and investor presentations from public companies in the space - Job postings (what roles are companies hiring for? what skills?) - Patent filings (what are companies building that they have not announced?) - Conference topics and keynotes (what are thought leaders discussing?) - Open source activity (GitHub stars, contributor growth, release velocity) - Regulatory actions (new laws, enforcement actions, proposed regulations) **Expert perspectives:** - What are practitioners saying? (blog posts, podcasts, talks) - What are critics saying? (counterarguments, failure cases) - Where is there consensus? Where is there disagreement? ### Step 3: Analyze using the Trend Maturity Framework Place the trend on this maturity spectrum: | Stage | Signal | Implication | |-------|--------|-------------| | **Emerging** | Mostly academic papers and VC hype. Few production deployments. | Monitor but do not invest heavily. Run small experiments. | | **Growing** | Early adopters showing results. Tooling is maturing. Talent market forming. | Start building capability. Pilot projects. | | **Mainstream** | Broad adoption. Best practices established. Multiple mature vendors. | Adopt or risk falling behind. Focus on execution. | | **Mature** | Table stakes. Differentiation comes from execution, not adoption. | Optimize, do not innovate here. | | **Declining** | Being replaced by something newer. Diminishing returns. | Plan migration. Do not increase investment. | ### Step 4: Synthesize findings ``` TREND ANALYSIS: [name] Maturity stage: [emerging / growing / mainstream / mature / declining] Confidence level: [high / medium / low] Summary: [3-4 sentences capturing the essence of the trend] Key findings: 1. [Finding with supporting evidence] 2. [Finding with supporting evidence] 3. [Finding with supporting evidence] Implications for us: - Short-term (0-6 months): [what to do now] - Medium-term (6-18 months): [what to plan for] - Long-term (18+ months): [what to monitor] Risks of ignoring: [what happens if we do nothing] Risks of over-investing: [what happens if we go all-in too early] Recommended action: [specific next step] ``` **STOPPING POINT 2**: Trend research is complete. What would you like to do next? 1. **Go deeper on implications** - Detailed analysis of how this trend affects your specific product/business 2. **Map against competitors** - See how competitors are responding to this trend 3. **Design an experiment** - Plan a low-cost way to test or build capability around this trend 4. **Build into a broader report** - Combine with other trend analyses for strategic planning 5. **Present to stakeholders** - Format findings for a specific audience --- ## Workflow 2: Competitive Landscape Analysis ### Step 1: Define the competitive frame ``` COMPETITIVE FRAME: Our product/service: [what we offer] Market we compete in: [specific market definition] Customer segment: [who we are competing for] Primary use case: [what the customer is trying to accomplish] ``` ### Step 2: Map the competitor landscape For each competitor, build a profile: ``` COMPETITOR PROFILE: [name] Type: [direct competitor / indirect competitor / potential entrant / substitute] Founded: [year] | Size: [employees] | Funding/Revenue: [if known] Target customer: [who they sell to] Core value prop: [their main pitch in one sentence] Pricing model: [how they charge] Key strengths: [2-3 specific strengths with evidence] Key weaknesses: [2-3 specific weaknesses with evidence] Recent moves: [product launches, funding, pivots, hires in last 6-12 months] Trajectory: [growing / stable / declining / pivoting] Threat level to us: [high / medium / low] -- [why] ``` ### Step 3: Competitive positioning matrix Map competitors on two axes relevant to your market. Common axes: - **Price vs. capability** (who is premium vs. budget, full-featured vs. simple) - **Enterprise vs. SMB** (who serves which segment) - **Breadth vs. depth** (platform vs. point solution) - **Innovation vs. reliability** (cutting edge vs. battle-tested) ``` POSITIONING MAP: [Axis 2 High] | [Comp A] | [Comp B] | | [Us] -----------------+------------------ | [Comp C] | | [Comp D] | [Axis 2 Low] [Axis 1 Low] [Axis 1 High] ``` ### Step 4: Identify opportunities and threats Based on the landscape: - **White space**: Positions no competitor occupies that customers need - **Convergence risk**: Multiple competitors moving toward our position - **Differentiation erosion**: Where our advantages are being commoditized - **Potential disruption**: Where a new type of competitor could emerge **STOPPING POINT 3**: Competitive analysis is complete. What next? 1. **Develop competitive responses** - Strategy for each major competitive threat 2. **Identify differentiation opportunities** - Where to invest to widen competitive moats 3. **Create competitive battle cards** - Quick-reference sheets for sales/marketing 4. **Monitor ongoing** - Set up a competitive tracking system 5. **Feed into product strategy** - Translate competitive insights into roadmap decisions --- ## Workflow 3: Evaluate an Emerging Technology ### Technology Evaluation Matrix Score the technology on 8 dimensions (1-5 each): | Dimension | Question | 1 (Poor) | 5 (Excellent) | |-----------|----------|----------|---------------| | **Maturity** | How production-ready is this? | Alpha/experimental | Battle-tested at scale | | **Community** | How strong is the ecosystem? | Tiny, single maintainer | Large, diverse, active | | **Fit** | How well does it solve our specific problem? | Tangential | Perfect match | | **Learning curve** | How hard is it for our team to adopt? | Requires new expertise | Familiar paradigm | | **Maintenance burden** | What is the ongoing cost of using this? | Heavy, constant updates | Low, stable | | **Lock-in risk** | How hard is it to switch away? | Proprietary, no alternatives | Standards-based, portable | | **Performance** | Does it meet our performance requirements? | Significant limitations | Exceeds needs | | **Cost** | Total cost of ownership (license, infra, people)? | Expensive | Free/cheap | **Score interpretation:** - 32-40: Strong candidate. Proceed to pilot. - 24-31: Promising but has gaps. Investigate the weak areas. - 16-23: Significant concerns. Only proceed if the fit score is 5 and there are no alternatives. - Below 16: Not ready for us. Revisit in 6-12 months. ### Build vs. Buy Decision Framework When deciding whether to build a capability internally or use an external solution: ``` BUILD VS. BUY ANALYSIS: [capability] BUILD BUY/LICENSE Upfront cost: [estimate] [estimate] Ongoing cost (annual): [estimate] [estimate] Time to first value: [estimate] [estimate] Time to full value: [estimate] [estimate] Customization: Full control Limited to vendor API Maintenance burden: On us On vendor Talent required: [skills] [integration skills] Strategic importance: [is this core to our differentiation?] Vendor risk: N/A [vendor stability, lock-in] Opportunity cost: [what else could team build?] [lower] DECISION FACTORS: - Is this a core differentiator? If yes, lean build. - Is this commodity infrastructure? If yes, lean buy. - Do we have the team to build AND maintain this? If no, lean buy. - Does a vendor solution exist that meets >80% of needs? If yes, lean buy. - Will our requirements diverge significantly from vendor roadmap? If yes, lean build. ``` **STOPPING POINT 4**: Technology evaluation is complete. What is the next step? 1. **Plan a pilot** - Design a time-boxed experiment to test the technology in your environment 2. **Deeper technical evaluation** - Hands-on testing against specific use cases 3. **Vendor comparison** - Compare multiple options side by side 4. **Build the business case** - Prepare an investment proposal for stakeholders 5. **Create an adoption plan** - Roadmap for rolling out the technology to the team --- ## Workflow 4: Comprehensive Trend Report ### Report structure for strategic planning ``` TREND REPORT: [title] Period covered: [date range] Prepared for: [audience] Prepared by: [who] EXECUTIVE SUMMARY [3-5 sentences: the most important things leadership needs to know] MACRO TRENDS [Broad forces shaping the market -- economic, regulatory, social, technological] TREND DEEP DIVES Trend 1: [name] - Stage: [maturity level] - Relevance to us: [high / medium / low] - Key insight: [one sentence] - Evidence: [2-3 supporting data points] - Our position: [ahead / in line / behind the market] - Recommended action: [specific step] Trend 2: [name] ... COMPETITIVE IMPLICATIONS - How trends are reshaping the competitive landscape - Who is best positioned and why - Where vulnerability exists STRATEGIC RECOMMENDATIONS 1. [Recommendation] - Priority: [high/medium/low] - Timeline: [when] 2. [Recommendation] - Priority: [high/medium/low] - Timeline: [when] 3. [Recommendation] - Priority: [high/medium/low] - Timeline: [when] WHAT TO WATCH - [Signal to monitor and what it would mean] - [Signal to monitor and what it would mean] APPENDIX - Methodology and sources - Detailed data tables - Glossary of terms ``` ### Research quality checklist Before finalizing any research output: - [ ] Claims are supported by specific evidence, not just assertions - [ ] Multiple sources are cited, not just one analyst or one article - [ ] Counterarguments and risks are addressed, not just the bull case - [ ] Recommendations are specific and actionable, not vague - [ ] Time horizons are explicit -- "soon" and "eventually" are not acceptable - [ ] Confidence levels are stated -- what you know vs. what you are inferring - [ ] The research answers the original question, not a different question