协作头脑风暴
brainstorming
在实现前澄清需求、探索设计选择,并形成清晰的开发方向。
cpo-review【开发与工程】/cs:cpo-review <plan> — JTBD-driven interrogation of product roadmap, PMF signal, and portfolio focus. Use when committing a quarter's roadmap, deciding whether to kill a feature, or claiming PMF without a retention curve.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Command: /cs:cpo-review <plan>
The JTBD-driven builder cuts the roadmap in half. Six questions to surface what to ship and what to kill.
What job is this feature hired to do, in the user's words?
What user behavior does this move, and how does that ladder to the North Star?
What's the retention curve for users who hire this job — is it flat, decaying, or smiling?
Reach, Impact, Confidence, Effort — what's the score and where does this rank in the queue?
python product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py
What gets cut if this ships? Name the specific initiative or feature.
What signal would tell you in 90 days that this was the wrong bet?
python ../../../c-level-advisor/skills/cpo-advisor/scripts/pmf_scorer.py
python ../../../c-level-advisor/skills/cpo-advisor/scripts/portfolio_analyzer.py
# CPO Review: <feature/plan>
**Date:** YYYY-MM-DD
## JTBD
> <one sentence in user voice>
## North Star Link
- Metric moved: <name>
- Expected delta: <%>
## PMF Signal
- Retention curve shape: flat / smiling / decaying
- Cohort sample size: N
## Score
- RICE: <number>
- Rank in queue: #N of M
## Cut List
- Cut: <initiative>
- Reason: <why this matters more>
## Kill Criteria (90 days)
- Metric: <name>
- Threshold: <value>
- Action if missed: <kill | iterate>
## Verdict
🟢 SHIP | 🟡 SHARPEN | 🔴 KILL
/cs:cmo-review — does the positioning support this feature?/cs:execute — build the 90-day plan/cs:post-mortem — if kill criteria triggeredcs-cpo-advisorcpo-advisorproduct-team/skills/product-manager-toolkit/Version: 1.0.0