Product Thinking
Run structured product diagnosis before you code—clarify ideas, stress-test demand, shrink MVP scope, and design the smallest validation step.
Overview
Product-thinking is a journey-wide agent skill that applies structured product diagnosis—modes, red flags, and minimal validation—whenever a solo builder needs to clarify demand and scope before committing to build.
Install
npx skills add https://github.com/ssdiwu/product-thinking --skill SKILL.mdWhat is this skill?
- Routes each session into diagnostic, founder, or builder mode after task-type and uncertainty triage
- Uses high-discrimination questions, red-flag signals, and anti-flattery rules instead of generic encouragement
- Converges scope to MVP with explicit phenomena, judgments, and minimal validation actions
- Diagnoses existing products and reviews proposals with actionable homework and verification plans
- Outputs structured bundles: phenomenon, judgment, red flags, actions, assignments, and validation design
Adoption & trust: 12 GitHub stars.
What problem does it solve?
You have product instincts and fragments of research but no disciplined way to separate real user jobs from noise, shrink MVP, or decide what to validate next.
Who is it for?
Founders and solo PMs who want Socratic product rigor across ideation, scoping, live-product triage, and pre-build reviews without a full-time product partner.
Skip if: Teams that already have an approved PRD and signed-off spec ready for pure implementation, or users who only want visual/UI design or code generation with no product framing.
When should I use this skill?
You need to clarify a product idea, judge whether demand is real, understand user tasks, converge MVP, diagnose an existing product, review a plan, or design the next validation step—especially when uncertainty is high.
What do I get? / Deliverables
You leave with a explicit judgment, red flags, a minimal action list, homework, and a verification plan you can execute before invoking implementation or planning skills.
- Structured diagnosis: phenomena, judgments, red flags, and recommended actions
- Action homework and a minimal validation or experiment plan
- Mode-appropriate review (diagnostic, founder, or builder) with explicit next decisions
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Clarify a new tool concept, classify uncertainty, and list red flags before writing a landing page.
Force-rank must-have MVP slices and define the smallest experiment that could falsify the core hypothesis.
Diagnose why shipped features miss retention and decide the next verification instead of adding more scope.
Review launch narrative against actual user tasks and flag positioning that oversells unvalidated value.
Interpret engagement drops as product-job mismatches and propose lifecycle tests before big growth spends.
How it compares
Use instead of open-ended “is this a good idea?” chat when you need mode-specific diagnosis and falsifiable validation steps.
Common Questions / FAQ
Who is product-thinking for?
Solo builders, indie founders, and small teams who wear the product hat and want an agent to challenge assumptions, surface red flags, and propose minimal validation—not cheerlead features.
When should I use product-thinking?
Use it in Idea/research to clarify concepts and jobs-to-be-done; in Validate/scope to converge MVP; in Build/pm when diagnosing roadmap or feature fit; in Ship/launch prep when reviewing whether the offer matches real tasks; and anytime you need a structured review before the nex
Is product-thinking safe to install?
It is primarily conversational methodology with no implied credential exfiltration; review the Security Audits panel on this Prism page and the skill source before enabling it in agents with broad tool access.
SKILL.md
READMESKILL.md - Product Thinking
产品思维协作技能。用于帮助用户澄清产品想法、判断需求真假、理解用户任务、收敛 MVP、诊断已有产品问题、评审方案与设计下一步验证。默认先识别任务类型与不确定性，再进入诊断模式、创始人模式或构建者模式中的一种，使用高判别问题、红旗信号、反谄媚规则与最小验证动作，输出现象、判断、红旗、动作、行动作业与验证方案。 # product-thinking { "name": "product-thinking", "description": "产品思维协作技能。用于帮助用户澄清产品想法、判断需求真假、理解用户任务、收敛 MVP、诊断已有产品问题、评审方案与设计下一步验证。默认先识别任务类型与不确定性，再进入诊断模式、创始人模式或构建者模式中的一种，使用高判别问题、红旗信号、反谄媚规则与最小验证动作，输出现象、判断、红旗、动作、行动作业与验证方案。" }