Agent Skills › stella/stella › product-think

product-think

GitHub

在产品需求模糊或方案未定时，引导澄清问题、分离供需、定义目标与约束，评估选项并明确权衡，最终产出包含问题、用户、目标和风险的产品简报，确保实施前具备清晰的产品逻辑。

.agents/skills/product-think/SKILL.md stella/stella

触发场景

需求描述模糊不清存在多种可行解决方案执行风险超过产品清晰度

安装

npx skills add stella/stella --skill product-think -g -y

更多选项

非标准路径

npx skills add https://github.com/stella/stella/tree/main/.agents/skills/product-think -g -y

不安装直接使用

npx skills use stella/stella@product-think

指定 Agent (Claude Code)

npx skills add stella/stella --skill product-think -a claude-code -g -y

安装 repo 全部 skill

npx skills add stella/stella --all -g -y

预览 repo 内 skill

npx skills add stella/stella --list

SKILL.md

Frontmatter

{
    "name": "product-think",
    "description": "Shape a feature or problem before implementation. Use this when the request is still fuzzy, when several solutions are possible, or when execution risks outrunning product clarity."
}

Product Think

Shape a feature or problem before implementation. Use this when the request is still fuzzy, when several solutions are possible, or when execution risks outrunning product clarity.

Arguments

$ARGUMENTS — Feature idea, problem statement, or change request.

Instructions

Clarify the problem first:
- who is affected?
- what pain or friction exists today?
- why does it matter now?
Separate problem from solution:
- write down the user need
- write down the proposed solution
- check whether the solution actually addresses the need
Define outcome, not just output:
- what should be better if this works?
- what user or business behavior should change?
State constraints:
- technical constraints
- organizational constraints
- compliance or trust constraints
- timeline constraints
Explore options:
- simplest viable option
- stronger but more expensive option
- what not to build yet
Make tradeoffs explicit:
- speed vs correctness
- breadth vs depth
- automation vs control
- flexibility vs clarity
Define scope:
- in scope
- out of scope
- follow-up ideas that should not block the first version
Define success:
- what would we measure?
- what would we observe qualitatively?
- what would count as failure?
Produce a short product brief in prose or markdown, with:
- problem
- user
- goal
- options considered
- recommendation
- risks
- success signal
Only move to implementation planning after this is coherent.