# Quick Brainstorm for Design Decisions

Users struggle with slow, over-structured brainstorming that delays decisions. The simple-brainstorm skill provides a lightweight, focused process to quickly explore options, evaluate trade-offs, and reach actionable conclusions without unnecessary ceremony.

## Install

```bash
npx skillstore add roin-orca/simple-brainstorm
```

## Metadata

- - Slug: roin-orca-simple-brainstorm
- - Version: 1.0.0
- - Author: roin-orca
- - GitHub username: roin-orca
- - License: MIT
- - Repository: https://github.com/roin-orca/skills/tree/main/skills/simple-brainstorm/
- - 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-simple-brainstorm
- - Manifest: https://skillstore.pages.dev/api/skills/roin-orca-simple-brainstorm/manifest

## Capabilities

- Guide users through a 4-step brainstorming process: Discover, Propose, Converge, Capture
- Ask focused clarifying questions in batches to understand project context
- Present 2 approaches with trade-offs and lead with a recommendation
- Iterate proposals up to 2 rounds to reach user alignment
- Capture the chosen direction as an inline comment or chat summary

## Use Cases

- Quick Feature Design: When starting a new feature, use the skill to quickly explore approaches, evaluate trade-offs, and pick a direction before writing code.
- Component Architecture Decisions: When facing a design choice between multiple implementation approaches, use the skill to structure the discussion and reach a clear decision.
- Behavioral Change Validation: When modifying existing behavior, use the skill to understand the full context and ensure changes align with project conventions.

## Prompt Templates

### Basic Brainstorm Request

```
I need to brainstorm about [describe your task or decision]. Can you help me explore the options and pick a direction?
```

### Architecture Discussion

```
We need to decide on [specific architectural choice]. What are the main approaches we could take and what are the trade-offs of each?
```

### Quick Trade-off Analysis

```
I'm torn between approach A and approach B for [describe the decision]. Can you help me think through the pros and cons of each?
```

### Full Feature Exploration

```
I want to build [describe the feature]. Before we start, let's explore: What are we trying to achieve? What are the key constraints? What's the simplest approach that could work? What's the main risk?
```

## Limitations

- Does not write code or create files - focuses purely on decision-making discussion
- Does not access external resources or APIs for research
- Limited to 2 proposal iterations - requires user to state direction if stuck
- Not designed for large-scale architectural reviews or multi-team consensus

## Best Practices

- Answer all clarifying questions in one response to keep the conversation moving
- When presenting options, lead with your recommendation and explain why
- Once a direction is approved, capture it immediately as an inline comment or summary

## Anti Patterns

- Answering clarifying questions across multiple messages instead of batching them
- Jumping straight to implementation without user approval of a direction
- Proposing more than 2 approaches, which creates analysis paralysis

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-03-02T08:55:07.258\+00:00
- - Summary: Security audit completed. Static findings are false positives: \(1\) Backticks at SKILL.md:17 are DOT diagram syntax for Graphviz, not shell commands. \(2\) No cryptographic code exists - the 'weak algorithm' findings are spurious pattern matches. This is a pure documentation skill with no code execution, network access, or sensitive operations.

## Stats

- - Views: 114
- - Downloads: 7
- - Favorites: 0
- - Popularity score: 0