/brainstorm

Make it your own.

In Claude Code, use the slash command and add your context. In Codex, select brainstorm from the just-vibe skill picker, then send the same brief.

Version 0.11.0 also supports /jv brainstorm, /just-vibe brainstorm and /jv:brainstorm in Claude. See shortcut setup and context examples.

What the agent does

1. Restate the objective, then vary actual mechanisms such as ownership, interaction or persistence; include a minimal approach and discard duplicates.
2. For each remaining candidate explain its benefits and costs and attach a cheap validation experiment.

Inputs

• problem, audience, constraints, and desired breadth. Requires the brief, with repository context when relevant.

Optional context: scope, references, constraints, successCriteria, environment, mode, budget.

Scope

Reads

Generate distinct viable approaches; no implementation or final product commitment.

Writes

No source changes in inspect/plan. Save only requested planning artifacts. A separately requested repair uses the relevant implementation workflow.

Mode

Plan; problem, audience, constraints, and desired breadth. Requires the brief, with repository context when relevant.

Prerequisites

Resolve the user brief and inspect the relevant project or supplied evidence. External capabilities are optional unless the selected action actually needs them.

Expected output

• A bounded set of distinct options with tradeoffs and a validation experiment for each, and a justified shortlist.

How the work is checked

• Alternatives differ in actual behavior or architecture; all respect explicit constraints such as no new service.

When to stop or clarify

• Identify impossible constraint combinations. Avoid padding the output with renamed versions of the same idea.

Handling missing context

Infer

Resolve the named files, existing scripts, current task and earlier corrections from the conversation and repository.

Assume

Use the narrowest interpretation that completes a reversible local task; state a consequential assumption once.

Ask

Ask when competing targets or incompatible success conditions would change the result; continue independent inspection first.

Technical guidance

Evidence

Read the goal, hard constraints, existing approach and the kind of variation the user needs.

Method

Generate options that differ in actual mechanism or tradeoff and explain the constraint each option addresses.

Pitfall

Renaming the same architecture repeatedly is not useful diversity; brainstorming does not select or implement an option.

Check

Remove infeasible duplicates and make the decisive tradeoff between surviving options explicit.

Situational decisions

When constraints eliminate most options: Keep a small feasible set rather than adding cosmetic variants to meet a count.

The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.

Keep exploring