product-idea-brief
Use when a product idea workbook is complete or partly complete and needs a one-page summary, executive brief, pitch summary, or go/no-go recommendation for stakeholders or investors.
- License 许可
- MIT
- 最近更新
- 2026-10-18
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- product-idea-brief
- description
- Use when a product idea workbook is complete or partly complete and needs a one-page summary, executive brief, pitch summary, or go/no-go recommendation for stakeholders or investors.
02 资源文件 2
- 参考文档example.md3.0 KB
- 参考文档template.md870 B
03 SKILL.md 正文
Product Idea Brief
The one-page summary that opens the Product Idea Workbook. It's written last, and it's often the only part a stakeholder reads.
Input
workbooks/<product-slug>.md, with as many stages done as possible.
Procedure
-
Fill in
template.md(in this skill's folder) using only what's in the workbook. Don't add new numbers or claims.example.mdshows a finished brief for a fictional product. -
If a stage isn't done, write "Not yet done: run
<skill>" in its rows. Never fill a gap with a guess. -
Choose the top 3 risks from the riskiest assumptions, the ASSUMPTION labels, and the stage decisions. For each, give the cheapest test that would confirm or kill it.
-
Make the decision:
- GO: every stage says PROCEED.
- PIVOT: any stage says PIVOT.
- NO-GO: any stage says STOP.
Then give the single next action.
Quality gate
- [ ] Fits on one page (about 400 words)
- [ ] Every number matches the workbook exactly
- [ ] Unfinished stages are marked, not invented
- [ ] Each risk has a concrete, cheap test
- [ ] The decision follows from the stage decisions
Output
Write or replace the Product Idea Brief section, which is the first section after the workbook heading in workbooks/<product-slug>.md.
04 同仓库更多 Skills
stage-review
Use when a section of a product idea workbook (customer problem, market, solution, value, or brief) has been drafted and needs a critical review before its PROCEED / PIVOT / STOP decision, or when someone asks to stress-test, red-team, or poke holes in a product idea.
solution-space
Use when turning a validated customer problem and market position into a product concept — "what should we build?", product concept outline, user flow, wireframes, functional requirements, non-functional requirements, context diagram, MVP scope.
new-product-idea
Use when someone has a new product idea, wants to build a product that competes in an existing market, or asks to evaluate, validate, or work through a product idea end to end.
market-space
Use when a product idea needs its market sized, segmented, or positioned against competitors — "how big is the market?", "who are the competitors?", "where should we position?", "which segment first?", positioning map, position-to-own, market focus.
market-research
Use when a product or market analysis needs real, cited numbers — customer counts, market size, competitor prices and positioning, industry statistics, willingness to pay — or when a figure in a product idea workbook has no source.
idea-screen
Use when someone has several product ideas and wants to know which one to pursue, or wants a quick, cheap sanity check on an idea before a full workbook — "which of these ideas should I build?", "compare these ideas", "rank my ideas", "quick gut check on this idea".