ctx-brainstorming | claude-cortex | ClaudePluginHub

Skill

Community

ctx-brainstorming

From claude-cortex

5

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.

Install

1

Add the repository(one-time)

$

/plugin marketplace add NickCrew/claude-cortex

2

Install the plugin

$

/plugin install nickcrew-claude-ctx-2@NickCrew/claude-cortex

Tool Access

This skill inherits all available tools. When active, it can use any tool Claude has access to.

Supporting Assets

View in Repository

resources/examples.md

Skill Content

`/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) and scenarios/ 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/*.md tied to the feature.
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: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.

Links

GitHub Stats

0 forks

Updated 1 day ago

Similar Skills

Command Development

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

53.4k

Agent Development

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

53.4k

Hook Development

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.

53.4k