Home / qa-aman / claude-skills · GitHub

product-discovery SKILL.md skillA

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

Install it, pinned

mdr add qa-aman/claude-skills/product-discovery@git:20260303.e2bea1e

Pins git:20260303.e2bea1e in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: qa-aman/claude-skills
Path: skills/by-role/pm/product-discovery/SKILL.md
Versions recorded: 1
Latest version: git:20260303.e2bea1e, committed Mar 3, 2026
Size: 4,264 bytes
Repository stars: 25
License: MIT

Run product discovery to identify what to build. Use when the user says "product discovery", "how do I know what to build", "validate this idea", "talk to customers", "are we building the right thing", "discovery process", or wants to reduce the risk of building something users don't want - even if they don't say "discovery".

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

## Overview

Based on **Inspired** by Marty Cagan (Silicon Valley Product Group). Cagan's central argument: the biggest risk in product is not execution risk - it's value risk (will users buy it?), usability risk (can users figure it out?), feasibility risk (can we build it?), and business viability risk (does it work for the business?). Discovery is how you tackle all four before writing a line of code.

The best product teams run discovery and delivery in parallel. Discovery is not a phase - it's a continuous habit.

## Workflow

### Step 1: Identify the four risks
For the idea or problem at hand, assess:
- **Value risk** - Do users actually want this? Will they use it?
- **Usability risk** - Will users understand how to use it?
- **Feasibility risk** - Can the team build it with current skills and tech?
- **Viability risk** - Does it work legally, financially, and ethically for the business?

Rate each: High / Medium / Low. Focus discovery on High risks.

### Step 2: Frame the opportunity (not the solution)
State the problem as an opportunity: "Users struggle to [X], which causes [Y impact]."
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add qa-aman/claude-skills/product-discovery@sha256:77d1290aebbd14d1

The line at the top of this page pins the label git:20260303.e2bea1e, 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](https://markdownregistry.com/badge/art_4wzbylicg2w3jebg.svg)](https://markdownregistry.com/a/art_4wzbylicg2w3jebg)

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

Versions

The registry has recorded 1 version of this file, committed on Mar 3, 2026.

version	committed	commit	size	audit
git:20260303.e2bea1e latest	2026-03-03	e2bea1e	4,264 B	A	view

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 (4264 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

qa-aman/claude-skills · 25 stars · license MIT · pushed 2026-10-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_4wzbylicg2w3jebg
GET https://markdownregistry.com/api/v1/resolve?ref=qa-aman/claude-skills/product-discovery
GET https://markdownregistry.com/api/v1/blob/77d1290aebbd14d1425977e92ef71ed452104fc5108267d5d3ee0aa2b2dd733e

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 qa-aman/claude-skills

create-skill SKILL.md skill

qa-aman/claude-skills · .claude/skills/create-skill/SKILL.md · Create or update Claude Code skills following Anthropic's official skill standard. Use when user says "create a skill"…

git:20260303.4fa499f · audit A · 25 stars

sync-skills SKILL.md skill

qa-aman/claude-skills · .claude/skills/sync-skills/SKILL.md · Fetch skills from projects on the current system, genericize them, and add to the claude-skills repository. Use when…

git:20260303.4fa499f · audit A · 25 stars

CLAUDE.md CLAUDE.md file

qa-aman/claude-skills · CLAUDE.md

git:20261019.be4abcc · audit A · 25 stars

audit-workpaper SKILL.md skill

qa-aman/claude-skills · skills/by-role/accountant/audit-workpaper/SKILL.md · Write a clear, reviewable audit workpaper documenting procedures, evidence, and conclusions. Use when an auditor says…