brainstorm

Guides one-question-at-a-time dialogue to define outcomes and approaches before coding.

Updated May 5, 2026
One-click install
npx skills add https://github.com/josippapez/ai-setup --skill brainstorm-josippapez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/josippapez/ai-setup/tree/main/claude/plugins/orchestrate/skills/brainstorm
Command: npx skills add https://github.com/josippapez/ai-setup --skill brainstorm-josippapez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Requests like "build me X" often arrive with no defined outcome, data source, or approach, and jumping straight into tracking or code produces the wrong thing. This Skill forces a short, structured dialogue that pins down what to build and how before any decomposition, tracking, or implementation begins. ## Core Features & Use Cases - Two-path classification: Choose between a Quick call (outcome mostly stated, one or two closing questions) and Explore (genuinely open outcome or approach, with 2-3 trade-offed options and a recommendation). - Hard approval gate: Blocks epic tracking, decomposition, builder spawning, and code until the user explicitly approves a plainly stated outcome and approach. - Orchestration handoff: Folds the approved outcome and approach directly into Gate/Intake of the orchestrate skill, with EPIC.md as the durable spec. - Use Case: A user says "I need a way to scrape competitor pricing." The Skill asks one question at a time about data sources and output shape, proposes two approaches with trade-offs, gets approval, then hands the pinned spec to orchestrate. ## Quick Start Ask the assistant to brainstorm the outcome and approach for your new feature idea before any planning or coding begins.

Frequently Asked Questions about brainstorm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clarify requirements before starting a coding task?

Use a structured brainstorm dialogue that asks one question at a time, proposes 2-3 approaches with trade-offs, and requires explicit approval of the outcome before any code. This prevents building the wrong thing from an ambiguous request.

When should I brainstorm instead of going straight to task planning?

Brainstorm when the outcome or approach itself is undecided, such as a new capability with no defined data source or output shape. If the outcome is already clear and only scope or acceptance criteria are missing, skip straight to intake-style grilling.

What is the difference between the Quick call and Explore paths?

Quick call applies when the outcome is basically stated and one or two questions close remaining gaps. Explore applies when the outcome or approach is genuinely open, requiring multiple-choice questions and 2-3 proposed approaches with trade-offs.

Does brainstorming replace task decomposition or epic tracking?

No. Brainstorming settles what to build and how, then hands the approved outcome to Gate/Intake in the orchestrate skill, which handles scope, acceptance criteria, and decomposition. It runs before tracking, not instead of it.

What happens if a simple request turns out to hide a design decision?

Re-classify mid-conversation from Quick call to Explore and say so explicitly. Hidden scope is a reason to stop and surface the decision, not to continue quietly with an assumed approach.