# Structured Brainstorming for Fast Decisions

Get from idea to actionable direction quickly with a lightweight brainstorming process that explores intent and evaluates trade-offs without unnecessary overhead.

## Install

```bash
npx skillstore add roin-orca/fun-brainstorming
```

## Metadata

- - Slug: roin-orca-fun-brainstorming
- - Version: 1.0.0
- - Author: roin-orca
- - GitHub username: roin-orca
- - License: MIT
- - Repository: https://github.com/roin-orca/skills/tree/main/skills/fun-brainstorming/
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: safe
- - Quality score: 81
- - Quality tier: silver
- - Public page: https://skillstore.pages.dev/skills/roin-orca-fun-brainstorming
- - Manifest: https://skillstore.pages.dev/api/skills/roin-orca-fun-brainstorming/manifest

## Capabilities

- Guide users through a structured discovery phase to clarify intent and constraints
- Present 2-3 approach options with clear trade-offs and recommendations
- Facilitate convergent decision-making with explicit user approval
- Capture decisions inline or in chat without requiring formal documentation
- Adapt depth and formality to match task complexity
- Prevent premature implementation by enforcing approval before coding

## Use Cases

- Feature Design Decisions: When planning a new feature, use this skill to explore options, evaluate trade-offs, and get alignment on direction before writing code.
- Architectural Choices: Before refactoring or designing new system components, brainstorm the approach to ensure decisions are well-considered.
- Quick Problem Solving: When facing a technical problem, use the structured approach to systematically explore solutions rather than jumping to the first idea.

## Prompt Templates

### Basic Brainstorming Request

```
I need to brainstorm [describe your task or problem]. Can we explore some approaches together?
```

### Trade-off Exploration

```
I'm considering [option A] vs [option B] for [use case]. What are the trade-offs of each approach, and which would you recommend?
```

### Decision Review

```
I've been thinking about [problem] and my initial idea is [describe idea]. Can you help me think through whether this is the right direction?
```

### Constraint-Aware Planning

```
I need to solve [problem] but I have these constraints: [list constraints]. What approaches would work within these limits?
```

## Limitations

- Does not execute code or create files - acts only as a thinking partner
- No access to external tools or APIs for research
- Cannot generate diagrams or visual artifacts
- Relies on user input for project-specific context and constraints

## Best Practices

- Start with the Discover phase to clarify intent before jumping to solutions
- Present options with clear trade-offs, and lead with your recommendation
- Get explicit user approval before moving to implementation
- Batch your clarifying questions into one message to respect user time
- Match the depth of discussion to the complexity of the task

## Anti Patterns

- Jumping straight to code without brainstorming approval
- Asking one question at a time instead of batching
- Presenting more than 3 options which overwhelms rather than helps
- Skipping the approval step and assuming user agreement
- Using formal documentation for simple decisions when chat suffices

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-03-06T08:49:23.212\+00:00
- - Summary: Static analysis flagged external\_commands and weak cryptographic algorithms, but evaluation reveals these are false positives. The 'external\_commands' detection refers to a documented bash command in markdown \(not executed code\) and a Graphviz diagram block. The 'weak cryptographic algorithm' detection is a scanner bug - no cryptographic code exists in this file. This is a pure documentation file containing brainstorming methodology with no security risks.

## Stats

- - Views: 127
- - Downloads: 9
- - Favorites: 0
- - Popularity score: 0