← Back to list
⚡

brainstorm-ideas-new Checked

Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer p…
⚡ Productivity skills By phuryn Version v1.0.0 Added 2026-09-03 Updated 2026-09-03 Source ↗
7.6Overall rating
2Views
6Downloads
26.0kStars

Installation

🤖 Install via AI

Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.

Install the "brainstorm-ideas-new" skill by following the instructions at https://skill123.me/install/brainstorm-ideas-new.
⌨️ Command line install

Run in your terminal — downloads and installs to ~/.claude/skills/.

curl -fsSL https://skill123.me/install/brainstorm-ideas-new.sh | bash
📦 Download ZIP

Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.

⬇ Download v1.0.0 · 1 KB
📊 Static rating
7.6/10
Trigger
6.5
Structure
7.3
Workflow
6.4
Content
8.0
Engineering
9.0
Security
9.5

Six-dimension rubric with reviewer rationale.

View scorecard ↓
🛡 Dynamic test
—

Not live-tested yet — this skill is rated on static analysis only.

About this skill

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.

Documentation

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.

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:

1. **Understand the opportunity**: Confirm the product concept, target market segment, and what the users want to achieve.

2. **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

3. **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

4. **For each prioritized idea**, provide reasoning and key assumptions to test.

Think step by step. Save substantial output as a markdown document.

---

### Further Reading

Score breakdown

Trigger
6.5
Clear What/When with discovery keywords; overlaps heavily with sibling existing-product variant and lacks When-Not.
Structure
7.3
Single compact file with clean sections; no scripts or offloaded references.
Workflow
6.4
Task-oriented steps with 3-perspective structure and stage-specific weights; no failure handling or verification.
Content
8.0
Concise imperative instructions; initial-vs-continuous domain note adds useful context briefly.
Engineering
9.0
Valid frontmatter, no scripts, no broken internal references.
Security
9.5
No scripts or injection; links to reputable productcompass.pm only.
Good trio-perspective ideation skill with new-product-specific prioritization weights, but no boundary definition, error handling or verification loop.