product-discovery SKILL.md skillA

product-discovery from teambrilliant/dev-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add teambrilliant/dev-skills/product-discovery@git:20260927.b9558d0

Pins git:20260927.b9558d0 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
teambrilliant/dev-skills
Path
skills/product-discovery/SKILL.md
Versions recorded
3
Latest version
git:20260927.b9558d0, committed Sep 27, 2026
First version recorded
Mar 24, 2026
Size
11,140 bytes
Repository stars
5
License
none declared

Validate whether a product idea will actually work before committing engineering — find what you don't know, design the cheapest test, set evidence gates that justify or kill the investment. Use when someone says "validate this idea", "discovery", "run an experiment", "test this hypothesis", "what are the risks", "is this worth building", "feasibility check", "prototype plan", or a team is about to spend weeks on something nobody has tested. Sits between product-thinker (should we?) and…

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Product Discovery

Figure out whether an idea is worth building before you commit engineering time. The goal is sufficient evidence that the solution will work — not certainty, but enough to bet responsibly.

70-90% of features built without validation fail to deliver business results. Discovery exists to catch the failures early and cheap, so engineering investment goes toward ideas with real evidence behind them.

## Core Principle

Every idea tested in discovery should cost at least one order of magnitude less than building the real thing. If engineering a feature takes 4 weeks, discovery should take days. If it takes months, discovery should take weeks.

Discovery code is **built to learn, not built to last** — it's meant to be ripped out. Use the lightest materials that produce the evidence (a hardcoded page, a manual step behind the curtain, a key-value store instead of a schema migration). Skip the unit tests, the refactors, and the durability work until an idea earns the real build. A healthy discovery process *kills most ideas*: a 30–40% rate of experiments worth shipping is good, which means most of what you build here is thrown away on purpose. Pride belongs in the…
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_i4ya4rkrplswb7ng/871c713586b7ec7f696cdb673d6c72a3af00ff51e499e1ffabb64255a3b9a6ca.json

Then /plugin install product-discovery@markdownregistry-i4ya4rkrplswb7ng in Claude Code. It installs git:20260927.b9558d0, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add teambrilliant/dev-skills/product-discovery@sha256:871c713586b7ec7f

The line at the top of this page pins the label git:20260927.b9558d0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_i4ya4rkrplswb7ng.svg)](https://markdownregistry.com/a/art_i4ya4rkrplswb7ng)

4 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in teambrilliant/dev-skills/product-discovery since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of product-discovery from somewhere else? Ask it: where did my product-discovery come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 3 versions of this file, between Mar 24, 2026 and Sep 27, 2026, about one every 94 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20260927.b9558d0 latest2026-09-27 b9558d0 11,140 BA view · diff
git:20260621.8a081692026-06-21 8a08169 11,521 BA view · diff
git:20260324.e094a362026-03-24 e094a36 9,618 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (11140 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

teambrilliant/dev-skills · 5 stars · license none declared · pushed 2026-10-26 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_i4ya4rkrplswb7ng
GET https://markdownregistry.com/api/v1/resolve?ref=teambrilliant/dev-skills/product-discovery
GET https://markdownregistry.com/api/v1/blob/871c713586b7ec7f696cdb673d6c72a3af00ff51e499e1ffabb64255a3b9a6ca

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from teambrilliant/dev-skills

CLAUDE.md CLAUDE.md file
teambrilliant/dev-skills · CLAUDE.md
git:20261008.865c794 · audit A · 5 stars
execute-plan SKILL.md skill
teambrilliant/dev-skills · skills/execute-plan/SKILL.md · Execute an approved plan from thoughts/plans/ to completion — every phase, every check, every acceptance criterion —…
git:20261026.069feb8 · audit A · 5 stars
explain SKILL.md skill
teambrilliant/dev-skills · skills/explain/SKILL.md · Explain a plan, a shape, a shipped change, code, or the last message so it's impossible to misunderstand — an ASCII…
git:20261008.81e7416 · audit A · 5 stars
product-primitives SKILL.md skill
teambrilliant/dev-skills · skills/product-primitives/SKILL.md · Break down complex products, features, or systems into fundamental primitives and building blocks from a software…
git:20260507.c5d07e6 · audit A · 5 stars
product-thinker SKILL.md skill
teambrilliant/dev-skills · skills/product-thinker/SKILL.md · Use for product decisions, user behavior analysis, and UX evaluation. Trigger when the user wants to: evaluate whether…
git:20261008.81e7416 · audit A · 5 stars
qa-test SKILL.md skill
teambrilliant/dev-skills · skills/qa-test/SKILL.md · Browser-based QA verification after any implementation. Use when someone says "QA this", "test this in browser"…
git:20260927.b9558d0 · audit A · 5 stars
shaping-work SKILL.md skill
teambrilliant/dev-skills · skills/shaping-work/SKILL.md · Shape rough ideas into clear, actionable work definitions. Use this skill whenever someone has an unstructured idea…
git:20261008.81e7416 · audit A · 5 stars
strategic-thinker SKILL.md skill
teambrilliant/dev-skills · skills/strategic-thinker/SKILL.md · Use for cross-domain strategic reasoning, approach selection, and systems-level analysis. Trigger when the user wants…
git:20261008.81e7416 · audit A · 5 stars
working-backwards SKILL.md skill
teambrilliant/dev-skills · skills/working-backwards/SKILL.md · Write an Amazon-style PR-FAQ (mock press release + FAQ) to pressure-test a product idea customer-first and kill weak…
git:20261008.81e7416 · audit A · 5 stars
write-plan SKILL.md skill
teambrilliant/dev-skills · skills/write-plan/SKILL.md · Write a technical implementation plan to thoughts/plans/ before coding starts (separate from the harness's plan mode)…
git:20261008.81e7416 · audit A · 5 stars

Every file in teambrilliant/dev-skills

Other files named product-discovery

product-discovery SKILL.md skill
cbrock84/headcount · plugins/product/skills/product-discovery/SKILL.md · Finds out whether a problem is real and a solution would work, before building it — recruiting the right people…
git:20260901.9844f9d · audit A · 2,543 stars
product-discovery SKILL.md skill
majiayu000/spellbook · skills/product-discovery/SKILL.md · Product discovery and market research expert. Use when validating product ideas, conducting market research, user…
git:20260523.d39dd11 · audit A · 297 stars
product-discovery SKILL.md skill
magnus919/agent-skills · product-discovery/SKILL.md · Discover external customer problems and product requirements from human stakeholders. Assess customer evidence before…
git:20261101.6eeef1d · audit A · 181 stars
product-discovery SKILL.md skill
nahid-sparktales/agent-dispatcher · skills/product/product-discovery/SKILL.md · Find the real problem behind a feature request before anyone scopes a solution — whose job is stuck, what evidence…
git:20260919.a0d4f55 · audit A · 58 stars
product-discovery SKILL.md skill
peterbamuhigire/chwezi-dev-engine · skills/product-business/product-discovery/SKILL.md · Use when testing whether a product, feature, or workflow deserves investment through risk framing, prototypes…
git:20261031.feccc13 · audit A · 31 stars
product-discovery SKILL.md skill
qa-aman/claude-skills · skills/by-role/pm/product-discovery/SKILL.md · Run product discovery to identify what to build. Use when the user says "product discovery", "how do I know what to…
git:20260303.e2bea1e · audit A · 27 stars
product-discovery SKILL.md skill
yannickyamo/skills · product-discovery/SKILL.md · Run continuous discovery to find problems worth solving. Use when setting up weekly discovery rhythm, building…
v1.0.0 · audit A · 24 stars
product-discovery SKILL.md skill
martinolivero/saas-builder · skills/product-discovery/SKILL.md · This skill should be used when the user has a product idea but is not sure what to build, what the MVP is, or where to…
git:20260605.5e4d680 · audit A · 5 stars

Browse by kind, by grade A, or by owner.