home / skills / ladderchaos / tora-skills / brainstorm

brainstorm skill

/brainstorm

This skill guides you through structured brainstorming to explore options, analyze trade-offs, and converge on a clear implementation plan.

npx playbooks add skill ladderchaos/tora-skills --skill brainstorm

Review the files below or copy the command above to add this skill to your agents.

Files (1)
skill.md
2.8 KB
---
name: brainstorm
description: Structured ideation and exploration workflow. Use this skill when exploring ideas, evaluating options, or needing creative problem-solving before implementation.
---

# Brainstorm

Structured workflow for exploring ideas, evaluating trade-offs, and reaching decisions before committing to implementation.

## When This Skill Activates

- Exploring multiple approaches to a problem
- Evaluating architecture or design options
- Creative problem-solving sessions
- When "I'm not sure how to approach this"
- Before starting complex features

## Brainstorm Protocol

### Phase 1: Diverge (Generate Options)

Generate multiple approaches without judgment:

```markdown
## Options

### Option A: [Name]
- **Approach**: [Brief description]
- **Pros**: [Benefits]
- **Cons**: [Drawbacks]

### Option B: [Name]
- **Approach**: [Brief description]
- **Pros**: [Benefits]
- **Cons**: [Drawbacks]

### Option C: [Name]
- **Approach**: [Brief description]
- **Pros**: [Benefits]
- **Cons**: [Drawbacks]
```

**Rules for divergence:**
- Aim for 3-5 distinct options
- Include at least one unconventional approach
- No filtering yet - capture all ideas
- Brief descriptions only

### Phase 2: Analyze (Evaluate Trade-offs)

Compare options against criteria:

```markdown
## Analysis

| Criteria | Option A | Option B | Option C |
|----------|----------|----------|----------|
| Complexity | Low | Medium | High |
| Time to implement | Fast | Medium | Slow |
| Maintainability | Good | Good | Poor |
| Fits existing patterns | Yes | Partial | No |
| Risk | Low | Medium | High |
```

**Common criteria:**
- Implementation complexity
- Performance implications
- Maintainability
- Security considerations
- Alignment with existing patterns

### Phase 3: Converge (Decide)

Make a recommendation:

```markdown
## Recommendation

**Selected**: Option [X]

**Rationale**: [Why this option best balances the trade-offs]

**Risks to monitor**: [What could go wrong]

**Next steps**:
1. [First action]
2. [Second action]
```

## Quick Brainstorm (5-minute version)

For smaller decisions:

```markdown
## Quick Decision: [Topic]

**Options**: A) [option] | B) [option] | C) [option]

**Pick**: [Choice] because [one-line rationale]
```

## When to Skip Brainstorming

- Clear requirements with obvious solution
- Bug fixes with known cause
- Following established patterns
- User has already decided approach

## Output Formats

| Scenario | Format |
|----------|--------|
| Architecture decision | Full 3-phase + ADR |
| Feature approach | Full 3-phase |
| Implementation detail | Quick brainstorm |
| Naming/style choice | Quick brainstorm |

## Anti-Patterns

- Analysis paralysis - set time limit
- Premature convergence - explore before deciding
- Skipping trade-off analysis
- Not documenting the decision rationale

Overview

This skill provides a structured ideation and exploration workflow to generate options, evaluate trade-offs, and reach a clear recommendation before implementation. It guides teams through divergence, analysis, and convergence so decisions are documented and actionable. Use it to reduce premature choices and surface unconventional alternatives.

How this skill works

First, the workflow rapidly generates 3–5 distinct options, including at least one unconventional idea, without judging them. Next, it evaluates those options against concrete criteria (complexity, time, maintainability, security, alignment) to surface trade-offs. Finally, it converges on a recommended option with rationale, risks to monitor, and clear next steps.

When to use it

  • Exploring multiple approaches to a problem or feature
  • Evaluating architecture or design options before committing
  • Creative problem-solving when direction is unclear
  • Prior to implementing complex features or systems
  • Time-boxed decision sessions to avoid analysis paralysis

Best practices

  • Start with divergence: generate 3–5 distinct options quickly
  • Include at least one unconventional approach to broaden thinking
  • Use objective criteria to compare options and document trade-offs
  • Time-box each phase to prevent analysis paralysis
  • Record the recommendation, rationale, risks, and next steps

Example use cases

  • Choose between monolith, modular monolith, or microservices for a new product
  • Decide on a database strategy: SQL, NoSQL, or hybrid
  • Pick a front-end architecture: component library, micro-frontends, or single app
  • Select a deployment model: managed platform, self-hosted, or serverless
  • Name a new API surface or decide on a public SDK design

FAQ

How many options should I generate?

Aim for 3–5 distinct options to balance breadth and focus; include at least one unconventional idea.

When is a quick brainstorm enough?

Use the 5-minute quick version for small, low-risk decisions like naming, style choices, or minor implementation details.