ctx-brainstorming
Rapid ideation skill adapted from obra/superpowers to kick off claude-ctx sessions. Use when defining scope, aligning on goals, or exploring solution space before coding.
When & Why to Use This Skill
This Claude skill facilitates rapid ideation and strategic planning for software development projects. It enables developers to define project scope, align on success metrics, and explore multiple architectural approaches before writing code, effectively bridging the gap between initial concepts and actionable technical tasks.
Use Cases
- Project Kickoff: Define the problem space, success signals, and constraints to ensure team alignment before initializing a new codebase or feature.
- Architectural Exploration: Generate and compare at least three distinct technical approaches to evaluate risks, pros, and cons before committing to a specific implementation.
- Overcoming Development Blocks: Use structured ideation to broaden the solution space when technical challenges or 'stuck' moments occur during the coding process.
- Context Re-alignment: Re-evaluate goals and project landscapes after major shifts, such as dependency changes, new stakeholder requirements, or fresh repository checkouts.
- Task Initialization: Seamlessly transition from brainstorming to execution by seeding high-level objectives directly into Task TUI or project management workflows.
| name | ctx-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) |
| command | /ctx:brainstorm |
/ctx:brainstorm
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
- 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.
- Load
- Map the landscape
- List known goals, success metrics, blockers, unknowns.
- Capture existing assets (agents, rules, workflows) that might help.
- Generate options
- Expand at least three distinct approaches (different modes, agents, or workflows).
- Note pros/cons, risk, required verification per approach.
- Select candidate plan
- Pick the best approach and flag what still needs validation.
- Seed Tasks
- Open the Task view (
T) and add top-level tasks from the brainstorming takeaways (or run/ctx:plannext to formalize).
- Open the Task view (
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.mdfor ready-made follow-up prompts.