Get the FREE Ultimate OpenClaw Setup Guide →

research

Scanned
npx machina-cli add skill ajaywadhara/agentic-sdlc-plugin/research --openclaw
Files (1)
SKILL.md
4.2 KB

Read docs/PRD.md to understand what is being built.

You are a Product Researcher. Your single goal: "Should the user build this, and if yes — how should they build it differently?"

━━━ STEP 1: COMPETITOR DISCOVERY ━━━

Search the web for:

  • Direct competitors (same problem, same target user)
  • Indirect competitors (same user, different approach to the problem)
  • Failed attempts (products that tried this and shut down — especially valuable)
  • Open source alternatives

For each competitor, capture in a table: | Name | Type (direct/indirect) | Pricing | Platform | Rating | Last Updated | Status |

Include dead products. A graveyard of failed competitors is signal, not noise.

Save to: docs/research/COMPETITORS.md

━━━ STEP 2: DEEP ANALYSIS (top 3-5 competitors only) ━━━

For each, research and answer:

POSITIONING

  • What is their core value proposition in one sentence?
  • Who do they say they're for?

USER SENTIMENT (from app store reviews, Reddit, Product Hunt comments)

  • What do 1-star reviews complain about most? (This is the most valuable data in this entire research. It tells you exactly what users hate and what gap you could fill.)
  • What do 5-star reviews praise? (This tells you what users consider non-negotiable — table stakes you must match.)

PRODUCT ANALYSIS

  • What features do ALL competitors have? (Table stakes. You must match these or explain why you're not.)
  • What feature does NONE of them have? (Opportunity gap. Consider this seriously for differentiation.)
  • How does onboarding work? (First 60 seconds for a brand new user)
  • How do they handle the empty state? (When a new user has no data yet. Most apps fail here. This is often where users churn. Note what each does.)
  • What is their pricing model? What tier do most users actually use?

Save to: docs/research/COMPETITIVE_ANALYSIS.md

━━━ STEP 3: THE VERDICT ━━━

Write a plain-English verdict in docs/research/VERDICT.md with these exact sections:

RED FLAGS — reasons to reconsider building this: (e.g. "A well-funded startup launched this exact product 3 months ago and has strong reviews. Competing head-on would be very difficult.")

GREEN FLAGS — reasons this gap is real and worth pursuing: (e.g. "All existing apps require a paid subscription. None have a usable free tier. Users complain about this constantly in reviews.")

YOUR ANGLE — the one thing to do differently from everyone else: (e.g. "Every competitor treats mobile as an afterthought. Build mobile-first.") (This becomes the product's north star. One sentence. Be specific.)

FEATURES TO REPLICATE — UX patterns competitors do well that you should copy: (Don't reinvent these. Match them and move on to your differentiation.)

FEATURES TO AVOID — things competitors built that users consistently hate: (Add these explicitly to Out of Scope in the PRD.)

PRICING INSIGHT — what pricing model is this market trained on? (Users in some markets expect free. In others they expect to pay. Know this early.)

━━━ STEP 4: UPDATE THE PRD ━━━

Open docs/PRD.md and make these additions:

  1. Add a "Competitive Context" section (3-4 sentences summarising the landscape)
  2. Update "Out of Scope" with features competitors have that you're intentionally skipping
  3. Mark any P0 feature that is a table stake with [TABLE STAKES]
  4. Mark any P1 feature that is your differentiation with [DIFFERENTIATOR]
  5. Add any new features discovered in research to P1 or P2 as appropriate

━━━ FINAL OUTPUT TO USER ━━━

Present a 3-paragraph summary: Paragraph 1: What the competitive landscape looks like Paragraph 2: The most important insight from user reviews (1-star patterns) Paragraph 3: Your recommended angle and whether to proceed

End with: "Research complete. PRD updated. Ready to wireframe — run /wireframe."

NOTE: All findings are directional, not gospel. Competitors pivot. Ratings shift. Use this to inform decisions, not to make them automatically.

Source

git clone https://github.com/ajaywadhara/agentic-sdlc-plugin/blob/main/skills/research/SKILL.mdView on GitHub

Overview

As a Product Researcher, you assess whether to build this idea and how to differentiate. You perform competitive discovery, analyze top players for positioning, sentiment, features, onboarding, and pricing, and deliver a verdict plus PRD updates. This ensures a data-driven go/no-go and a clear differentiator.

How This Skill Works

Step 1: Discover competitors, including direct, indirect, failed attempts, and open sources, saving to docs/research/COMPETITORS.md. Step 2: Do deep analysis on the top 3-5 competitors: positioning, user sentiment from reviews, onboarding, empty state handling, features, and pricing, saving to docs/research/COMPETITIVE_ANALYSIS.md. Step 3: Write a plain-English verdict in docs/research/VERDICT.md and update docs/PRD.md; present a final three-paragraph summary and close with a clear recommendation.

When to Use It

  • When validating a new product idea against direct/indirect competitors
  • When identifying what users hate and what they love from reviews
  • When mapping a differentiation strategy based on gaps others miss
  • When preparing PRD updates and go/no-go decisions for stakeholders
  • When planning a data-driven pricing and onboarding approach

Quick Start

  1. Step 1: Run STEP 1 Competitor Discovery and save results to docs/research/COMPETITORS.md
  2. Step 2: Perform STEP 2 Deep Analysis on top 3-5 competitors and save to docs/research/COMPETITIVE_ANALYSIS.md
  3. Step 3: Write STEP 3 The Verdict in docs/research/VERDICT.md, update docs/PRD.md, and deliver the three-paragraph summary

Best Practices

  • Include direct, indirect, and failed products to capture full market signals
  • Prioritize top 3-5 competitors for deep analysis to stay focused
  • Extract 1-star pain points and 5-star praises to ground hypotheses
  • Document findings in the prescribed docs paths (COMPETITORS.md, COMPETITIVE_ANALYSIS.md, VERDICT.md)
  • Clearly separate replication-worthy patterns from differentiators and reflect in PRD

Example Use Cases

  • Compare a new CRM entrant against Salesforce and HubSpot, noting gaps in onboarding and pricing
  • Study a meal-planning app's reviews to identify friction points and desired features
  • Analyze a failed competitor to understand what not to repeat and why it failed
  • Identify a feature no competitor offers and validate demand from user feedback
  • Synthesize a mobile-first angle if all incumbents overlook mobile onboarding

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers