brainstorm-ideas-new
Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-06
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- brainstorm-ideas-new
- description
- Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.
03 SKILL.md 正文
Brainstorm Product Ideas (New Product)
Multi-perspective ideation for initial product discovery of a new product. Generates specific feature ideas from PM, Designer, and Engineer viewpoints.
Context
You are supporting initial product discovery for a new product: $ARGUMENTS.
If the user provides files (market research, competitive analysis), read them first. Use web search to understand the market if needed.
Domain Context
Initial Discovery vs Continuous Discovery: Initial Discovery focuses on vision, business model, and market validation — you're testing whether the product should exist. Continuous Discovery runs in parallel with delivery — you're constantly learning and iterating on a live product. This skill is for initial discovery.
Instructions
The user will describe their target segment, opportunity, and desired outcomes. Work through these steps:
-
Understand the opportunity: Confirm the product concept, target market segment, and what the users want to achieve.
-
Ideate from three perspectives — generate 5 specific feature ideas each from:
- Product Manager: Focus on market fit, value creation, and competitive advantage
- Product Designer: Focus on user experience, onboarding, and engagement
- Software Engineer: Focus on technical innovation, API integrations, and platform capabilities
-
Prioritize the top 5 ideas across all perspectives. For a new product, weight heavily toward:
- Core value delivery (does it solve the primary problem?)
- Speed to validate (can we test this quickly?)
- Differentiation potential
-
For each prioritized idea, provide reasoning and key assumptions to test.
Think step by step. Save substantial output as a markdown document.
Further Reading
04 同仓库更多 Skills
tb-writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
tb-using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
tb-test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
tb-subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
tb-scrutinize
Outsider-perspective end-to-end review of a plan, PR, or code change. First questions intent and whether a simpler/more elegant approach would achieve the same goal, then traces the actual code path (not just the diff) to verify the change does what it claims. Output is concise, actionable, and every call carries its rationale. Trigger on /tb-scrutinize and proactively whenever the user asks to review, audit, sanity-check, or get a second opinion on a plan, PR, diff, design doc, or proposed code change.
tb-requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements