How to use the Existing Product Idea Brainstorm agent skill

What is an agent skill and what does this one do?

An agent skill is a folder containing a SKILL.md file with instructions that an AI agent loads when a task matches the skill's description. The agent then follows those instructions for that task.

This skill is for continuous product discovery on an existing product. Once it is active, the agent generates five ideas from each of three viewpoints: product manager (business value, strategic alignment, customer impact), product designer (user experience, usability, delight) and software engineer (technical possibilities, data leverage, scalable solutions). It then picks the best five across all perspectives and, for each one, gives a name, a one-sentence description, the reasoning for selecting it, and the key assumptions to validate.

• Generates 5 ideas from each of 3 viewpoints (15 candidates)
• Prioritizes the top 5 based on strategic alignment, potential impact, feasibility and effort, and differentiation
• Lists assumptions to test for each selected idea
• Can read files you provide, such as research data, opportunity trees or personas
• Can look at a product's website if you give it a URL
• Saves substantial output as a markdown document in your workspace

How do you install the skill?

There are two ways to install it. Choose the one that matches how you use your agent.

Option A is a local skills folder. Download the ZIP of this skill from our page and unzip it into your personal skills folder at ~/.claude/skills/, or into a project's .claude/skills/ folder if you want it available only in that project.

Option B is the Claude apps. Download the ZIP from our page, then upload it in the Claude apps under Settings → Capabilities → Skills.

• Personal (all projects): unzip into ~/.claude/skills/
• Single project: unzip into .claude/skills/ inside the project folder
• Claude apps: Settings → Capabilities → Skills, then upload the ZIP

How do you trigger the skill with natural requests?

You do not need special syntax. Describe what you want in plain language. The skill is meant to be used when you are generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio, so mention one of those goals.

The agent needs three things from you: the product, the objective, and the target segment with the outcomes you want. If any of these are unclear, the skill asks for clarification before generating ideas. Attaching research notes or personas, or giving a product URL, gives the ideas more grounding.

• Name the product and what it does
• State the objective and the customer segment
• Describe the desired outcomes
• Attach research, opportunity trees or personas if you have them
• Include the product URL if you want the agent to look up the site

What do example requests look like?

These examples follow the trigger themes in the skill description. Replace the details with your own product.

Each request should give the product, the goal and the segment. The more specific the request, the less generic the ideas will be.

• "Brainstorm new feature ideas for our project management app. Our goal is to reduce onboarding drop-off for small teams. Here are our onboarding interview notes."
• "We have identified that freelance designers struggle to share client feedback. Brainstorm solutions for this opportunity for our file-sharing product."
• "Run a product trio ideation session for our invoicing tool. Target segment: sole traders. Outcome: more invoices paid on time. Product site: https://example.com"

What does the skill need and what should you watch for?

The skill lists no required tools or packages. It does not run scripts. It does use the network: when you give it a product URL, it uses web search to understand the product.

The skill's output is generated from your prompt and any files you provide. It is not based on validated user data, so treat each assumption it lists as a hypothesis to test with real customers. Its ranking criteria are general and do not reflect your business constraints unless you state them.

• Requires: nothing listed
• Runs scripts: no
• Uses network: yes, for product URL lookups
• Ideas reflect your prompt and files, not validated customer data
• Add your own constraints (budget, team, technical limits) so the ranking reflects them

What tips improve the results?

Clear input gives better output. Vague descriptions produce generic ideas, so write one or two sentences about the product and the problem before you ask for ideas.

Treat the output as a structured first pass. Use it to start an ideation session or prepare for a discovery review, then test the assumptions with your team and customers.

• Give the agent the research and personas you already have
• Say what your team cannot do, so infeasible ideas are less likely to be picked
• Ask for the assumptions and test them before building anything
• Keep the saved markdown document so the team can review the reasoning later