brainstorm

Explore user intent, constraints, and design approaches before implementation.

1.2k|140|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/first-fluke/oh-my-agent --skill brainstorm-first-fluke
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/first-fluke/oh-my-agent/tree/main/.agents/skills/brainstorm
Command: npx skills add https://github.com/first-fluke/oh-my-agent --skill brainstorm-first-fluke

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill tackles the ambiguity and potential for wasted effort in the early stages of development by ensuring a clear design and user intent are established before any planning or implementation begins.

Core Features & Use Cases

  • Design-First Ideation: Explores user intent, constraints, and potential approaches.
  • Approach Evaluation: Compares multiple design options with trade-off analysis.
  • Use Case: When a product manager has a new feature idea, this Skill can be used to explore the user's needs, define constraints, and propose 2-3 different design solutions before a single line of code is written or a task is planned.

Quick Start

Use the brainstorm skill to explore a new feature idea for user authentication.

Frequently Asked Questions about brainstorm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I explore user intent and constraints before coding a new feature?▼

To explore user intent and constraints before coding, use design-first ideation to sequentially clarify requirements, propose multiple approaches with trade-offs, and secure incremental design approval.

What is the best way to evaluate multiple design approaches for product development?▼

Evaluating multiple design approaches for product development requires comparing 2-3 different design solutions with explicit trade-off analysis, ensuring clear constraints and user needs are defined before implementation planning.

How do I brainstorm and define requirements for ambiguous feature requests?▼

To brainstorm and define requirements for ambiguous feature requests, facilitate sequential clarification sessions to explore the user's core needs, evaluate potential approaches, and establish a clear design before planning begins.

When do I need approach evaluation and ideation before software implementation?▼

You need approach evaluation and ideation before software implementation when facing ambiguous requests, ensuring a clear design is established to prevent wasted development effort on misaligned solutions.

Does this design-first ideation process require any specific dependencies or frameworks?▼

No, this design-first ideation process requires no specific dependencies or frameworks, allowing you to focus purely on concept exploration and approach evaluation without prerequisite technical environment setup.