discovery
Skill2 starsChanged 3 days agoApache-2.0View on GitHub
Use when the user proposes a feature or product idea with no plan yet, asks whether something is worth building, to challenge a feature, compare with existing products or competitors, run a market scan, or write an opportunity brief. Also use when the user mentions product discovery, build versus buy, PR-FAQ, or jobs to be done.
28 other projects use a version of this.
Adopted by
Most recently taken up by
- jdonohoo/vern-bottheir own version, first seen Nov 15, 2026
- GustavoAlecio/claude-setuptheir own version, first seen Nov 8, 2026
- anotb/forward-deployedtheir own version, first seen Nov 8, 2026
- newkirkjosh/skillstheir own version, first seen Nov 1, 2026
- jantichy/claudetheir own version, first seen Oct 27, 2026
- CrowdStrike/agentworks-skillstheir own version, first seen Oct 25, 2026
Used with
Projects with it also use specify, brainstorm and 4 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ArvorCoSkillspecify
Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.
Also in 3 projects that use this
nicolasestremSkillbrainstorm
Structured idea generation and solution exploration with systematic analysis.
Also in 4 projects that use this
Hugging FaceSkillimplement
Make tests pass. Invoke after /write-tests produces failing tests.
Also in 6 projects that use this
MicrosoftSkillinit
Also in 3 projects that use this
AnthropicSkillarchitecture
Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 6 projects that use this
Other versions28 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 28
- AICMO/AiCMO-Marketing-Prompt-Collection★ 229same name
- avelikiy/great_cto★ 115same name
- joelhooks/joelclaw★ 66same name
- Kanevry/session-orchestrator★ 53same name
- jantichy/claude★ 52same name
- DGouron/review-flow★ 44same name
- Dan-Cleary/fdestack★ 40same name
- tekliner/improvado-agentic-frameworks-and-skills★ 17same name
- jdonohoo/vern-bot★ 15same name
- steepy-it/steepy-apex★ 14same name
18 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- bias-analysisSkill
- c4-graphSkill
- code-reviewSkill
- create-grafana-dashboardsSkill
- debugSkill
- evidence-based-analysisSkill
- git-conventionsSkill
- planSkill
- retroSkill
- skillSkill
- software-engineerSkill
- tddSkill
The file
Files
Discovery
When to use
- User proposes a feature or product idea and no workspace or plan exists
- User asks whether something is worth building, or to challenge a feature
- User asks what already exists: competitors, alternatives, build versus buy
- User asks for an opportunity brief, a PR-FAQ, or a market scan
Overview
Discovery decides whether and what to build. Planning decides how. The job is
killing risk before engineering commits, so a day spent deciding not to build is a
win, never a failure. The output is a one-page opportunity brief ending in a
verdict: build, buy, test first, or drop. On build, the plan
skill takes over.
Reference: market-scan.md. Read it at workflow step 3.
Workflow
- Reframe as an outcome. Rewrite the request as the user or business outcome it serves, measurable in one sentence. A feature with no stated outcome is the first red flag: ask one question, or in a delegated context derive the outcome from the brief and record it as an assumption.
- Challenge the four big risks (Cagan, Inspired): value (will anyone
use it), usability (can they figure it out), feasibility (can we build
it in the time we have), viability (does it work for the business: cost,
legal, support). One sentence per risk, each marked
low,open, orblocking, with its evidence. - Scan the market. Browse what already solves the job: competitors, adjacent products, open source, internal tools, and doing nothing. Search the job in the end user's words before any solution-shaped query, or adjacent players stay invisible. Compare by how well each completes the user's job, never by feature checklist. Query shapes, table format, and sources live in market-scan.md.
- Map opportunities before solutions (Torres, opportunity solution tree). One outcome per tree: outcome, then unmet needs, then candidate solutions, then assumption tests. Hold at least three candidates before choosing, and "integrate an existing product" from step 3 is always one of them.
- Test the riskiest assumption cheaply. Name the single assumption that kills the idea fastest. Name the cheapest test: a query over existing data, a prototype, five user conversations. Never a build.
- Write the brief to
docs/discovery/<name>.mdand stop for the verdict. In a delegated context, decide, record the reason, and continue.
The opportunity brief
One page. Every claim cites a source: a user quote, a metric, a ticket, or a URL.
| Section | Holds |
| Outcome | The measurable user or business outcome, one sentence |
| Evidence | Demand signals, each with its source |
| Market | Full player list (rejected ones included), scan verdict, and the comparison table from step 3 |
| Risks | The four risks, each low, open, or blocking, with why |
| Verdict | Build, buy, test first, or drop, with the reason |
| Kill criteria | The evidence that would reverse the verdict |
Not: "Competitor X has dashboards, we need dashboards." Yes: "Users export to Excel weekly to answer one question (tickets #312, #340); X answers it in-product."
Boundaries
This skill decides whether and what, never how. On a build verdict it hands the
brief to the plan triage; tasks, ADRs, and code start there.
Weighing conflicting reviews or field reports belongs to
bias-analysis. Claims about the existing codebase
follow evidence-based-analysis.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

