product-think
GitHub在功能或问题模糊时,通过澄清痛点、分离供需、定义目标与约束、探索方案及权衡,产出产品简报,确保执行前具备清晰的产品逻辑。
Trigger Scenarios
Install
npx skills add stella/stella --skill product-think -g -y
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.
Version History
- 85792bd Current 2026-07-24 16:11


