← ClaudeAtlas

ideatelisted

Research a product idea on the web to assess market viability, identify competitors, and decide whether to pursue it. Searches for existing solutions, GitHub repos, ProductHunt listings, and community signals. Writes .harness/product/idea.md. Use as the very first step when you have a new project idea, before product-plan.
RubenGlez/harness · ★ 0 · Code & Development · score 75
Install: claude install-skill RubenGlez/harness
# Ideate ## Step 1: Capture the idea If the user has already described their idea in the conversation, use that. Otherwise ask one question: > "Describe the product you want to build in one sentence — what it does and who it's for." Do not ask follow-up questions. Move straight to research. ## Step 2: Research Search the web systematically. Read the top results in full for each search — don't skim. **Competitor discovery** - Search `[keyword] app`, `[keyword] tool`, `[keyword] software` - Search `[keyword] site:producthunt.com`, `[keyword] site:github.com` - Search `best [keyword] alternative`, `open source [keyword]` - For each competitor found: what it does, who it targets, pricing model, main limitation, approximate user base or GitHub stars **User pain signals** - Search `[keyword] reddit`, `[keyword] site:news.ycombinator.com` - Look for "I wish [existing tool] could...", "why is there no tool that..." - Note the recurring complaints users have with existing solutions — these are the real gaps **Market saturation** - How many serious competitors exist? Are they well-funded, indie, or abandoned? - Is the open-source space active (recent commits, high stars) or stale? - Are there multiple funded startups? One dominant player? A fragmented market? ## Step 3: Synthesize Assess across four dimensions: **Saturation** — how crowded is the space? Is it dominated by one player, fragmented, or wide open? **Gap** — what do users consistently complain about that no exis