One-click install
npx skills add https://github.com/kanade0404/dotfiles --skill product-discovery-kanade0404
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-discovery
Source: https://github.com/kanade0404/dotfiles/tree/main/.opencode/skills/product-discovery
Command: npx skills add https://github.com/kanade0404/dotfiles --skill product-discovery-kanade0404

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

It turns vague ideas, pain points, and should we build this questions into a clear discovery artifact so you can focus on the right outcome instead of jumping straight to features.

Core Features & Use Cases

  • Outcome framing: Recast requests around the measurable change you want to achieve.
  • Opportunity mapping: Surface the customer pains, workarounds, and solution candidates behind the idea.
  • Risk and handoff planning: Capture value, usability, feasibility, and viability risks, then prepare the PRD for review and requirements work.
  • Use case: A founder with a half-formed app idea can use this Skill to draft a Lean PRD, identify the riskiest assumption, and prepare a clean handoff for the next agent.

Quick Start

Ask the product-discovery skill to turn your rough idea into a Lean PRD in docs/prd/<slug>.md, including the outcome, opportunities, assumptions, and next-step handoff.

Frequently Asked Questions about product-discovery

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

FAQPage Schema
How do I turn a vague product idea into a lean PRD?

Product discovery transforms rough ideas into a structured Lean PRD by framing desired outcomes, mapping customer opportunities, capturing risk assumptions, and preparing handoff-ready documentation without writing implementation specs.

What is opportunity mapping in product discovery?

Opportunity mapping is a product discovery process that surfaces the customer pains, workarounds, and solution candidates behind a vague request before committing to specific features or writing implementation details.

How do I validate risk assumptions before writing product requirements?

You validate risk assumptions by identifying value, usability, feasibility, and viability risks during product discovery, then defining validation tests to check the riskiest assumptions before proceeding to requirements handoff.

Can I use lean PRD generation for both new products and feature enhancements?

Yes, lean PRD generation applies to new products, new features, enhancements, and PRD revisions across self-use, close-circle, or external user scenarios to clarify the desired outcome before development.

Does product discovery write technical specifications or implementation details?

No, product discovery focuses strictly on outcome framing, opportunity mapping, and risk validation to produce a lean PRD, intentionally omitting technical specifications and implementation details for downstream handoff.

What is the best way to frame product outcomes instead of jumping straight to features?

The best way to frame product outcomes is to recast requests around the measurable change you want to achieve, using product discovery to shift focus from building features to solving the right customer problem.