home / skills / nickcrew / claude-cortex / brainstorming

brainstorming skill

safe

This skill helps teams rapidly generate diverse brainstorming options to align goals, identify blockers, and seed actionable tasks before coding.

npx playbooks add skill nickcrew/claude-cortex --skill brainstorming

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

Files (2)

SKILL.md

2.0 KB

---
name: brainstorming
description: Rapid ideation skill adapted from obra/superpowers to kick off cortex sessions. Use when defining scope, aligning on goals, or exploring solution space before coding.
license: MIT (obra/superpowers)
---

# `/collaboration:brainstorming`

Ported from obra/superpowers (MIT). Optimized for cortex so brainstorming outputs flow directly into Supersaiyan visuals and the Task TUI.

## When to run

- **Before touching code**: align on problem, success signals, blockers.
- **After big context shifts**: new stakeholder, major dependency change, fresh repo checkout.
- **When you feel stuck**: broaden solution space before diving back in.

## Inputs you need

- Current goal or ticket reference.
- Repo hints: relevant `modes/` (e.g., `modes/Super_Saiyan.md`) and `scenarios/` if they exist.
- Constraints (deadline, platforms, regulatory, etc.).

## Steps

1. **Set the stage**
   - Load `modes/Super_Saiyan.md` (CTRL+P → "Super Saiyan Mode") for visual/tone context.
   - Skim any `scenarios/ideation/*.md` tied to the feature.
2. **Map the landscape**
   - List known goals, success metrics, blockers, unknowns.
   - Capture existing assets (agents, rules, workflows) that might help.
3. **Generate options**
   - Expand at least three distinct approaches (different modes, agents, or workflows).
   - Note pros/cons, risk, required verification per approach.
4. **Select candidate plan**
   - Pick the best approach and flag what still needs validation.
5. **Seed Tasks**
   - Open the Task view (`T`) and add top-level tasks from the brainstorming takeaways (or run `/ctx:plan` next to formalize).

## Output format

```
### Problem / Goal
### Success Signals
### Constraints / Risks
### Existing Assets
### Options
- Option A …
- Option B …
- Option C …
### Chosen Direction & Next Checks
```

Paste the summary into the chat (or save under `scenarios/`). Then move to `/ctx:plan`.

## Resources

- See `skills/collaboration/brainstorming/resources/examples.md` for ready-made follow-up prompts.

Overview

This skill speeds up rapid ideation to kick off Cortex sessions and flow directly into visualizations and task management. Use it to align stakeholders, clarify scope, and explore multiple solution directions before writing code. It produces a concise summary you can paste into the chat or save to scenario files to move into planning.

How this skill works

The skill walks you through setting the stage, mapping goals and constraints, and generating distinct solution options with pros/cons and verification notes. It then selects a candidate plan and seeds top-level tasks so the ideas become executable work in the Task TUI or planning context. The output follows a fixed summary format to make downstream automation and visual tools consume the results reliably.

When to use it

Before touching code to align on problem and success metrics
After a major context shift (new stakeholder, dependency, or repo checkout)
When you’re blocked and need to broaden the solution space
When defining scope for a sprint, spike, or prototype
When preparing materials for a design or architecture review

Best practices

Start with a clear single-sentence problem or ticket reference to focus ideation
Collect constraints and known assets up front (platforms, deadlines, existing agents/workflows)
Produce at least three distinct approaches to avoid premature convergence
Record pros/cons, key risks, and verification steps for each option
Seed 3–6 top-level tasks from the chosen direction to convert ideas into work items

Example use cases

Kick off a new feature: align goals, success signals, and risks before design or implementation
Recovery after a context change: re-scope work when a new dependency or stakeholder appears
Unblock a stalled effort: surface alternative architectures, agent roles, or workflow changes
Prepare for demos: pick a focused approach with verification steps to deliver a working prototype
Plan cross-team integrations: capture assets, touchpoints, and validation paths

FAQ

What output does the skill produce?

A concise summary with Problem/Goal, Success Signals, Constraints/Risks, Existing Assets, Options (A/B/C), and the Chosen Direction with next checks.

How do I turn ideas into tasks?

After choosing a direction, seed top-level tasks into the Task view or run the planning command to formalize deliverables and owners.