# Oma Brainstorm

Explore goals, constraints, and alternative approaches before choosing a design.

- Repository: https://github.com/first-fluke/oh-my-agent (1356 stars)
- Category: Design
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add first-fluke/oh-my-agent --skill oma-brainstorm -g -a claude-code -y`
Codex: `npx skills add first-fluke/oh-my-agent --skill oma-brainstorm -g -a codex -y`
Cursor: `npx skills add first-fluke/oh-my-agent --skill oma-brainstorm -g -a cursor -y`
Gemini CLI: `npx skills add first-fluke/oh-my-agent --skill oma-brainstorm -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add first-fluke/oh-my-agent`

## Description

Explore goals, constraints, and alternative approaches before choosing a design. Use when the user requests ideation or design exploration.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Brainstorm - Design-First Ideation

## Scheduling

### Goal
Explore user intent, constraints, and alternative approaches before planning or implementation, then preserve an approved design for downstream planning.

### Intent signature
- User says they have an idea, want to brainstorm, compare approaches, explore concepts, or design before planning.
- Request is ambiguous enough that implementation or task planning would be premature.

### When to use
- Exploring a new feature idea before planning
- Understanding user intent and constraints before committing to an approach
- Comparing multiple design approaches with trade-offs
- When the user says "I have an idea" or "let's design something"
- Before invoking `/plan` for complex or ambiguous requests

### When NOT to use
- Requirements are already clear and well-defined -> use `oma-pm` directly
- Implementing actual code -> delegate to specialized agents
- Performing code reviews -> use `oma-qa`
- Debugging existing issues -> use `oma-debug`

### Expected inputs
- Early idea, ambiguous goal, product concept, design question, or set of constraints
- Existing project context when the idea must fit a codebase or product direction
- User preferences and approval gates

### Expected outputs
- Clarified intent and constraints
- Viable approaches as prose briefs (scenario, mechanism, residual risk), with comparison and recommendation when alternatives aid the decision
- Section-by-section approved design document
- Blind-review issue list (Tier 1 resolved, Tier 2/3 resolved or explicitly deferred)
- Saved design artifact before handoff to planning

The rest: https://github.com/first-fluke/oh-my-agent/blob/HEAD/.agents/skills/oma-brainstorm/SKILL.md