Home / teambrilliant / dev-skills · skills/product-discovery/SKILL.md · GitHub

product-discovery skillA

Name: product-discovery
Author: teambrilliant

product-discovery is agent-read markdown (skill) from teambrilliant/dev-skills: 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 shaping-.

Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified before it reaches your agent: the main file against the SHA-256 recorded here, the others against the git hashes of its source commit. The deterministic audit below grades 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

Latest version

mdr add teambrilliant/dev-skills/product-discovery@git:20260927.b9558d0

Exact content

mdr add teambrilliant/dev-skills/product-discovery@sha256:871c713586b7ec7f

Pin to a label to follow the author's releases, or to a sha256 for exact bytes. Either way the resolved hash is written to mdr.lock, and mdr install fetches those bytes again and checks them, so it installs them exactly or fails.

Badge

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

0 badge views in 30 days

Versions

version	committed	commit	size	audit
git:20260927.b9558d0 latest	2026-09-27	b9558d0	11,140 B	A	view · diff
git:20260621.8a08169	2026-06-21	8a08169	11,521 B	A	view · diff
git:20260324.e094a36	2026-03-24	e094a36	9,618 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Deterministic, no model, 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 · 6 stars · license none · pushed 2026-09-27 · 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 agent 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.