product-market-fit-validator
Validate whether a proposed or shipped feature fits the product, solves a meaningful user problem, and stays differentiated from existing surfaces. Use when reviewing overlap between features, checking product market fit, challenging roadmap ideas, evaluating retention or adoption risk, or pressure-testing new UX against the current product.
来源信息
- 仓库
- khorzhenwin/tenxeng
- 最近来源活动
- 2026年3月22日 08:38
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 0
- 分支
- 0
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- product-market-fit-validator
- description
- Validate whether a proposed or shipped feature fits the product, solves a meaningful user problem, and stays differentiated from existing surfaces. Use when reviewing overlap between features, checking product market fit, challenging roadmap ideas, evaluating retention or adoption risk, or pressure-testing new UX against the current product.
# Product Market Fit Validator
## When To Use
Use this skill when you need to:
- Validate whether a new feature deserves to exist in this product
- Check if a feature overlaps too much with an existing one
- Pressure-test product positioning before or after implementation
- Identify adoption, retention, or differentiation risks
- Recommend whether to keep, merge, rename, narrow, or remove a feature
## Default Workflow
1. Inspect the current product surfaces in `README.md`, relevant product docs, and the main dashboard entry points.
2. State the user job for the feature being reviewed in one sentence.
3. Compare that user job against nearby existing features and identify overlap.
4. Decide whether the feature should be:
- kept as is
- repositioned
- narrowed
- merged into another surface
- removed
5. Recommend the minimum changes needed to make the product clearer.
6. If the feature remains viable, update product docs and UX copy so the distinction is explicit.
## Evaluation Questions
- What user problem does this feature solve that is not already solved elsewhere?
- Why would a user open this surface instead of an adjacent one?
- Is the difference visible from labels, entry points, and first-screen copy?
- Does this feature strengthen the core loop or fragment it?
- Does the product need a new surface, or only a better action within an existing one?
- What would confuse a first-time user?
## Output Format
When reviewing product fit, return:
1. `Confusion points`
2. `Recommended positioning`
3. `Minimum product changes`
4. `Residual risks`
Keep findings concrete and tied to existing surfaces, docs, or UI entry points.
## Repo-Specific Guidance
- Core product shell lives in `app/dashboard/page.tsx`.
- Product feature packets live in `docs/product/`.
- Use `README.md` to understand the full shipped capability set before proposing a new surface.
- If a feature overlaps with `Review mistakes`, `Practice`, `Leaderboard`, `PvP`, or `Social`, compare the user job directly instead of judging each in isolation.
## Guardrails
Do not:
- Approve a feature just because it is technically implementable
- Create parallel surfaces with nearly identical user jobs
- Treat naming problems as cosmetic when the real issue is product overlap
- Expand scope before clarifying the feature's role in the product
在 GitHub 查看