When should I use the Brainstorm skill?

Use it when a request is ambiguous (e.g., 'add login') or when multiple architectural approaches are possible and tradeoffs matter.

What happens after the brainstorming phase?

Once the scope is locked, the skill provides a clear handoff to specialized planning skills like 'architect' or 'design-discovery' for execution.

How does it handle external technical information?

It utilizes Context7 and local file analysis to gather facts about libraries, APIs, and existing code patterns to ensure recommendations are data-driven.

Does this skill write implementation code?

No, the Brainstorm skill focuses exclusively on clarification, alignment, and scoping; it specifically avoids writing implementation plans or production code.

What is a 'request-lock snapshot'?

It is a set of markdown tables that fix the scope, public surfaces, and work bundles in the user's own language to ensure alignment before planning begins.

Brainstorm (Codex)

Name: Brainstorm (Codex)
Author: SeoJaeWan

bySeoJaeWan

0•

Productividad y Flujo de Trabajo

Clarifies ambiguous project requests by locking scope, requirements, and architecture choices before implementation begins.

Brainstorm is a specialized pre-planning skill for Claude Code designed to eliminate ambiguity in complex development tasks. It guides the AI to decompose vague goals—such as 'improve UX' or 'add a dashboard'—into concrete work bundles, public surfaces, and state ownership rules. By producing structured request-lock snapshots and comparing implementation approaches through detailed tradeoff tables, it ensures that developers and AI are perfectly aligned on the project direction, significantly reducing rework and architectural drift.

Características Principales

01Structured request-lock snapshots using standardized markdown tables

02Multi-approach comparison with pros, cons, and implementation costs

03Context-aware research via local repository analysis and external fact-checking

04Ambiguity resolution for vague or high-level project requests

050 GitHub stars

06Premise challenging to validate problem framing and reduce project risk

Casos de Uso

01Identifying missing business rules and UX policies before starting a complex refactor

02Refining high-level feature requests into actionable technical requirements

03Comparing different architectural patterns or library choices for a new module

Características Principales

01Structured request-lock snapshots using standardized markdown tables

02Multi-approach comparison with pros, cons, and implementation costs

03Context-aware research via local repository analysis and external fact-checking

04Ambiguity resolution for vague or high-level project requests

050 GitHub stars

06Premise challenging to validate problem framing and reduce project risk

Casos de Uso

01Identifying missing business rules and UX policies before starting a complex refactor

02Refining high-level feature requests into actionable technical requirements

03Comparing different architectural patterns or library choices for a new module