lean-prd

Converts customer discovery notes into a structured, testable PRD.

Updated Aug 27, 2026

Search Tags:#scoping #validation #discovery #prd #product-management #build-brief

Ready to run

npx skills add https://github.com/120ventures/claude-skills --skill lean-prd-120ventures

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lean-prd
Source: https://github.com/120ventures/claude-skills/tree/main/lean-prd
Command: npx skills add https://github.com/120ventures/claude-skills --skill lean-prd-120ventures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning rich customer discovery into a concise, testable PRD that guides fast, validated product bets.

Core Features & Use Cases

Extracts a single, testable hypothesis per PRD driven by discovery evidence.
Structures PRD sections to enable rapid translation into a build spec.
Bridges discovery to development by defining scope, bets, and validation criteria.

Quick Start

Write a single sentence that converts discovery notes into a lean PRD outline ready for the build.

Frequently Asked Questions about lean-prd

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

FAQPage Schema

How do I turn customer discovery notes into a testable PRD?▼

To turn customer discovery notes into a testable PRD, you extract a single hypothesis driven by discovery evidence and structure it with defined scope, bets, and validation criteria for rapid translation into a build spec.

What is the best way to structure a lean PRD for fast product validation?▼

A lean PRD for fast product validation is structured around a single testable hypothesis, bridging discovery to development by defining scope decisions, bets, and validation criteria to guide rapid, validated product bets.

How do I scope product decisions from user interviews into a build brief?▼

Scoping product decisions from user interviews into a build brief requires defining specific scope boundaries and validation criteria that translate discovery insights directly into shippable product requirements.

Can I use this approach to translate discovery insights directly into a build spec?▼

Yes, you can translate discovery insights directly into a build spec because the PRD structure is specifically designed to enable rapid translation by defining clear scope decisions, bets, and validation criteria.

Does a lean PRD require a single testable hypothesis per document?▼

Yes, a lean PRD requires extracting a single testable hypothesis per document, ensuring the product bet is driven directly by evidence gathered from customer discovery interviews and notes.