agentleFS
yuusakuriyuusakuri/agent-skills/skills/brainstorm-ideas-existing/SKILL.md

brainstorm-ideas-existing

Skill2 starsChanged 10 days agoMITView on GitHub

Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user provides files (research data, opportunity trees, personas), read them first.

    line 14
  2. Distinctive:

    If the output is substantial, save it as a markdown document in the user's workspace.

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Brainstorm Product Ideas (Existing Product)

Multi-perspective ideation for continuous product discovery. Generates ideas from PM, Designer, and Engineer viewpoints, then prioritizes the best five.

Context

You are supporting a product trio performing continuous product discovery for $ARGUMENTS.

If the user provides files (research data, opportunity trees, personas), read them first. If they mention a product URL, use web search to understand the product.

Domain Context

Product Trio (Teresa Torres, Continuous Discovery Habits): PM + Designer + Engineer collaborate on discovery together. "Best ideas often come from engineers." Discovery is not linear — loop back if experiments fail. Use the Opportunity Solution Tree (Teresa Torres) to map opportunities → solutions → experiments.

Instructions

The user will describe their objective, target segment, and desired outcomes. Work through these steps:

  1. Understand the opportunity: Confirm the product, objective, market segment, and desired outcomes. Ask for clarification if anything is ambiguous.
  2. Ideate from three perspectives — generate 5 ideas each from:
    • Product Manager: Focus on business value, strategic alignment, and customer impact
    • Product Designer: Focus on user experience, usability, and delight
    • Software Engineer: Focus on technical possibilities, data leverage, and scalable solutions
  3. Prioritize the top 5 ideas across all perspectives based on:
    • Strategic alignment with the stated objective
    • Potential impact on desired outcomes
    • Feasibility and effort required
    • Differentiation from existing solutions
  4. For each prioritized idea, provide:
    • A clear name and one-sentence description
    • Why it was selected (reasoning)
    • Key assumptions to validate

Think step by step. Present ideas in a clear, structured format.

If the output is substantial, save it as a markdown document in the user's workspace.


Further Reading

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.