who-built-this-before-me

Scan code repositories, products, and literature to map prior art for an idea.

75|9|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/iagochavarry/who-built-this-before-me --skill who-built-this-before-me
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: who-built-this-before-me
Source: https://github.com/iagochavarry/who-built-this-before-me/tree/main
Command: npx skills add https://github.com/iagochavarry/who-built-this-before-me --skill who-built-this-before-me

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams and engineers determine whether an idea has already been built, preventing wasted effort by surfacing prior art and clearly stating the verdict.

Core Features & Use Cases

  • Idea restatement and framing: restates the idea in one sentence to confirm the search target.
  • Vocabulary generation and framing: creates multiple perspectives to guide diverse search queries.
  • Landscape search and clustering: queries code repositories, products, and literature, then groups findings into Direct matches, Adjacent solutions, Partial solutions, and Abandoned.
  • Pattern extraction and verdict: identifies standard design patterns and delivers a verdict with concrete next steps.

Quick Start

Describe your idea in one sentence and start the prior-art search.

Frequently Asked Questions about who-built-this-before-me

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my software idea already exists?

To check if your software idea already exists, scan the landscape for direct matches, adjacent solutions, and related efforts across code repositories, product announcements, engineering blogs, and standards or papers, then map the prior art to benchmark your angle.

What is prior-art landscape analysis for product discovery?

Prior-art landscape analysis for product discovery is the process of querying code repositories and literature to group findings into direct matches, adjacent solutions, partial solutions, and abandoned projects, identifying standard design patterns to deliver a structured verdict.

How do I validate product ideas against existing competitor research?

You validate product ideas against competitor research by restating the idea, generating diverse search vocabulary, clustering landscape findings into four buckets, and performing a fair differentiator analysis to determine concrete next steps for your angle.

Can I use this for architecture patterns and open source tooling discovery?

Yes, you can use this for architecture patterns and open source tooling discovery because the process applies to software ideas, products, and tooling, extracting standard design patterns from repositories and engineering blogs to map related efforts.

What is the best way to find abandoned projects during idea validation?

The best way to find abandoned projects during idea validation is to scan the landscape across code repositories and literature, clustering findings into an abandoned bucket to analyze why prior efforts failed and avoid repeating mistakes.

When do I need a prior-art search for software engineering ideas?

You need a prior-art search for software engineering ideas when you want to prevent wasted effort by determining whether a given idea has already been built, mapping the landscape to clearly state a verdict and benchmark your unique angle.