Brainstorm Ideas Existing

What Is This?

Overview

Product teams working on established products face a recurring challenge: generating fresh, actionable ideas without losing sight of technical constraints, user needs, and business goals. The Brainstorm Ideas Existing skill addresses this by structuring ideation across three distinct professional viewpoints, those of the Product Manager, the Designer, and the Engineer. This multi-perspective approach ensures that no single discipline dominates the creative process, producing a more balanced and implementable set of ideas.

The skill is designed for continuous product discovery, meaning it fits naturally into ongoing development cycles rather than one-time planning events. By prompting the model to think from each role's perspective in sequence, it surfaces ideas that a single-role brainstorm would typically miss. A PM might focus on market positioning and user retention, while a Designer considers interaction patterns, and an Engineer evaluates what is technically feasible within the current architecture.

After generating ideas from all three viewpoints, the skill consolidates and prioritizes them, helping teams move from raw ideation to a ranked shortlist that can feed directly into a backlog or discovery sprint. This structured output reduces the time teams spend organizing post-brainstorm notes and makes the results immediately actionable.

Who Should Use This

• Product managers running discovery sessions for an existing product line
• UX designers looking to generate feature concepts grounded in technical reality
• Software engineers who want to contribute product ideas beyond their immediate implementation scope
• Product trios preparing for a structured ideation workshop or sprint planning session
• Startup founders iterating on a launched product and seeking structured creative input
• Product coaches and consultants facilitating ideation sessions with cross-functional teams

Why Use It?

Problems It Solves

• Single-perspective brainstorming produces ideas that are either technically impractical, visually underdeveloped, or disconnected from business goals
• Unstructured ideation sessions generate long lists of ideas with no clear prioritization, making follow-up difficult
• Product trios often lack a shared framework for combining their different viewpoints into a coherent set of proposals
• Teams working on mature products struggle to find genuinely new directions without a structured prompt to shift their thinking
• Brainstorm outputs frequently sit in documents without being translated into actionable backlog items

Core Highlights

• Generates ideas from PM, Designer, and Engineer perspectives in a single structured pass
• Applies continuous product discovery principles rather than one-time planning logic
• Prioritizes ideas after generation, reducing post-session organization work
• Works for both open-ended ideation and targeted opportunity-specific brainstorming
• Produces output that maps directly to backlog items or discovery tickets
• Encourages cross-functional alignment by making each discipline's reasoning visible
• Scales from solo use to full product trio facilitation

How to Use It?

Basic Usage

Invoke the skill with a clear description of your existing product and the opportunity or problem area you want to explore.

/brainstorm-ideas-existing

Product: Task management app for remote teams
Focus area: Improving daily standup workflows
Current constraints: Web-only, REST API, no mobile app yet

The skill will then generate ideas grouped by PM, Designer, and Engineer perspectives before producing a prioritized summary.

Specific Scenarios

Scenario 1: Feature expansion for a SaaS product A PM wants to explore retention features for a project management tool. The skill generates PM ideas around onboarding nudges and milestone notifications, Designer ideas around dashboard personalization, and Engineer ideas around webhook integrations with calendar tools.

Scenario 2: Addressing a known user pain point A team has identified through user research that reporting is too manual. The skill focuses ideation on that specific opportunity, producing targeted ideas from each perspective rather than general feature suggestions.

Real-World Examples

A product trio at a B2B analytics company used this skill before a quarterly planning session. The structured output gave each discipline a voice and reduced the planning meeting from three hours to ninety minutes.

A solo founder iterating on a launched productivity app used the skill weekly to maintain a steady flow of discovery ideas without needing a full team present.

Important Notes

Requirements

• A clearly defined existing product with at least a basic description of its purpose and users
• An identified focus area, opportunity, or problem statement to direct the brainstorm
• Basic awareness of current technical constraints to make Engineer perspective ideas actionable