Product Requirements Review
Conducts structured product requirements review from idea to design doc. As PM asks clarifying questions; analyzes essence (problem, audience, real demand, business logic); researches competitors and data; as CTO assesses technical feasibility and Vibecode cost/time; then proposes creative, shortest-path solutions (smart, non-generic, with unique value or cold-start); makes go/no-go; if go, produces concept, name, architecture, user flows, system design (Vibecode-oriented), design references, and full design document. Principles: no process for its own sake, challenge ideas directly, common se
Install
npx skills add fourierwang66666/product-requirements-review --skill product-requirements-reviewgit clone --depth 1 https://github.com/fourierwang66666/product-requirements-review.git /tmp/product-requirements-review
mkdir -p ~/.claude/skills
cp -r /tmp/product-requirements-review/. ~/.claude/skills/product-requirements-reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 产品需求评审 (Product Requirements Review)
对用户提出的产品想法，按以下十一步执行结构化评审；到第六步做出是否继续的结论，若继续则完成第七至第十一步并输出完整设计文档。
## 整体原则（贯穿所有步骤）
1. **不为了专业而专业**：无须堆砌过程让自己显得专业，每一步都应对结论有直接贡献。
2. **简单直接面向问题**：以近乎无情的方式挑战用户的想法，不回避尖锐问题。
3. **回归 common sense**：打破不符合逻辑和常识的幻想，每个判断都要经得起常识检验。
4. **调研和推理需有足够支撑**：结论要有依据（数据、案例、推导），不写空泛表述。
5. **面向交付**：想象下一步是直接将文档丢给 Cursor 实现，输出以 Vibecode 友好、可执行为目标。
## 执行流程总览
```
Step 1 澄清 → Step 2 本质分析 → Step 3 竞品与数据 → Step 4 技术评估 → Step 5 创造性解决方案 → Step 6 决策
↓
支持 → Step 7 理念/架构/流程
→ Step 8 系统架构(Vibecode)
→ Step 9 设计风格参考
→ Step 10 完整设计文档
不支持 → 输出详尽报告并暂停
```
---
## Step 1：产品经理式澄清
**角色**：专业产品经理。
**动作**：针对用户描述的产品想法，主动提出一组问题，帮助用户更清晰、精准地表达想法。
**提问方向（可酌情选用）**：
- 这个想法最早是因为什么场景/痛点产生的？
- 你心目中「用好了」的用户，一天/一周会怎么用这个产品？
- 有没有一个具体的用户画像或身边可类比的人？
- 和现有你常用的某某产品相比，你希望哪里不同？
- 能接受的 MVP 范围是什么（第一版最少要做到哪几件事）？
**输出**：整理后的「产品想法陈述」（用户原意 + 澄清后的共识），作为后续步骤的输入。
---
## Step 2：本质分析（看本质、讲逻辑）
**原则**：看本质、讲逻辑；不堆砌术语，每个结论要有推导过程。
### 2.1 问题定义
用一句话说清「在什么情境下，为谁解决什么问题」。
要求：
- 不能是「我要做一个XX产品」的功能描述，必须回到问题本身。
- 格式参考：「当[某类人]在[某情境]下想要[某目标]时，他们遇到了[某障碍]」。
- 如果用户的描述偏向解决方案而非问题，主动追问「你觉得现在的人是怎么解决这个问题的？哪里让他们不满意？」
### 2.2 核心场景（发散思考）Details
- Skill name
product-requirements-review- Repository
- fourierwang66666/product-requirements-review
- License
- MIT
- Repo updated
- 6 February 2026
FAQ
What does the Product Requirements Review skill do?
Conducts structured product requirements review from idea to design doc. As PM asks clarifying questions; analyzes essence (problem, audience, real demand, business logic); researches competitors and data; as CTO assesses technical feasibility and Vibecode cost/time; then proposes creative, shortest-path solutions (smart, non-generic, with unique value or cold-start); makes go/no-go; if go, produces concept, name, architecture, user flows, system design (Vibecode-oriented), design references, and full design document. Principles: no process for its own sake, challenge ideas directly, common se
How do I install the Product Requirements Review skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add fourierwang66666/product-requirements-review --skill product-requirements-review. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Product Requirements Review popular?
It lives in fourierwang66666/product-requirements-review, which has 9 GitHub stars and 1 forks.
Related skills
Project Daily Summary
9leonsong09/project-daily-summary
Use when the user wants a same-day Codex work summary grouped by project folder or repository, combining today's Codex sessions, extracted plans, completed items, commits, and uncommitted changes, or says 项目日报, 日报, 今日工作总结, 按项目总结今天, 总结今天所有 Codex 会话, 总结今天会话+提交+未提交改动.
Isms P Audit
9basejb/isms-p-audit-skill
ISMS-P 인증 사전 점검을 위한 코드/IaC 정적 분석 스킬. 사용자가 "ISMS 점검", "ISMS-P 준비", "보안 감사", "통제항목 점검", "개인정보보호 감사", "정보보호 인증 준비"를 언급하거나, NestJS/ Spring/Django/Rails 같은 백엔드 프로젝트에서 IAM·로깅·암호화·접근통제 미흡 사항을 식별해 달라고 요청할 때 호출한다. Glob/Grep/Read로 코드와 Terraform/CloudFormation/Kubernetes 매니페스트를 스캔해 ISMS-P 통제항목과 매핑된 리스크 보고서를 생성한다. EN: Static analysis skill for ISMS-P (Korean Personal Information & Information Security Management System) pre-audit. Triggers on phrases like "ISMS audit", "ISMS-P readiness", "security compliance check", "Korean privacy audit". Scans source code and IaC to map findings to ISMS-P controls and
Session Wrap
9leonsong09/session-wrap
Use when the user wants to wrap up the current coding session, summarize the current session before ending work, document learnings, decide what to commit, or says 总结会话, 会话总结, 收尾, 会话收尾, 结束会话, 总结本次会话.
Data Oriented Design
9Data-Oriented-Design-for-Games/data-oriented-design
Language-agnostic architecture guide for building games and performance-sensitive apps with Data-Oriented Design (DOD) — adapted from *High Performance Unity Game Development (Using data-oriented design)* by Nitzan Wilnai, generalized to any language and with a first-class HTML5/JavaScript/Canvas track. Use this skill whenever building or reviewing a game (or real-time/simulation code) in DOD style outside Unity — especially HTML/JS/Canvas, but also C, C++, Rust, Go, Zig, or plain C#. Trigger when the user asks to: scaffold a game or feature in DOD style, generate DOD-compliant code, review co
Thermo Nuclear Code Quality Review
9Oreo992/thermo-nuclear-code-quality-review
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
4d V21
9Ganbin/4d-development-skill
Comprehensive 4D v21 development expert with embedded official documentation. Covers ORDA patterns, entity classes, data model classes, queries, classic methods, data types, error handling, forms, events, web server, and REST API. Use when working with 4D files (.4dm), 4D language questions, 4D project structure, entity classes, ORDA queries, database operations, form development, web server configuration, REST API usage, or any 4D-specific syntax issue. Includes full official 4D v21 documentation for on-demand retrieval. Triggers on: .4dm files, 4D code, ORDA, entity selection, dataclass, 4D
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.