
Brainstorming
- 1 installs
- 28 repo stars
- Updated June 29, 2026
- nickcrew/claude-cortex
A rapid ideation skill to kick off sessions by defining scope, aligning on goals, and exploring the solution space before coding.
About
Provides a rapid ideation flow adapted from obra/superpowers to open a working session before implementation. A developer uses it to define scope, align on goals, and explore options before writing code.
- Adapted from obra/superpowers for cortex sessions
- Front-loads scope and goal alignment before coding
Brainstorming by the numbers
- 1 all-time installs (skills.sh)
- Ranked #2,473 of 3,280 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/nickcrew/claude-cortex --skill brainstormingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 28 |
| Last updated | June 29, 2026 |
| Repository | nickcrew/claude-cortex ↗ |
What it does
A rapid ideation skill to kick off sessions by defining scope, aligning on goals, and exploring the solution space before coding.
Files
/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) andscenarios/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/*.mdtied 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:plannext to formalize).
Output format
### Problem / Goal
### Success Signals
### Constraints / Risks
### Existing Assets
### Options
- Option A …
- Option B …
- Option C …
### Chosen Direction & Next ChecksPaste the summary into the chat (or save under scenarios/). Then move to /ctx:plan.
Resources
- See
skills/collaboration/brainstorming/resources/examples.mdfor ready-made follow-up prompts.
/ctx:brainstorm Snippets
- Design System Feature – Focus on
modes/Super_Saiyan.md+agents/security-auditorwhen accessibility/security are explicit goals. - Infrastructure Spike – Pair brainstorm with
/dev:implementonce high-level strategy is picked; log hypotheses in Task view immediately.
Use these snippets as optional follow-ups after the main skill runs.