brainstorming
Clarify vague requirements through exploratory questioning and option generation before committing to research or implementation.
Best use case
brainstorming is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Clarify vague requirements through exploratory questioning and option generation before committing to research or implementation.
Teams using brainstorming should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/brainstorming/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How brainstorming Compares
| Feature / Agent | brainstorming | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Clarify vague requirements through exploratory questioning and option generation before committing to research or implementation.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Brainstorming ## Overview When requirements are vague and "what to build" is unclear, brainstorming clarifies the problem space through structured questioning and option generation. ## When to Use - Requirements lack clarity or specificity - Multiple valid approaches exist and trade-offs need exploration - The problem space needs definition before research - Stakeholders have not converged on a direction ## Distinction from Research - **Brainstorming**: Addresses "what to build" (unclear requirements) - **Research**: Addresses "how it works" (clear goal, unknown implementation) ## Process 1. **Explore problem space** - Ask clarifying questions one at a time 2. **Identify ambiguities** - Surface assumptions and unknowns 3. **Generate options** - Propose design alternatives with trade-offs 4. **Select approach** - Human chooses direction 5. **Synthesize requirements** - Produce clear requirements for research phase ## Tool Use Invoke via babysitter process: `methodologies/rpikit/rpikit-brainstorm`
Related Skills
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.
resume
Resume an existing Babysitter run from Codex.
project-install
Install the Babysitter Codex workspace integration into the current project.
plan
Plan a Babysitter workflow without executing the run.
observe
Observe, inspect, or monitor a Babysitter run.
model
Inspect or change Babysitter model-routing policy by phase.
issue
Run an issue-centric Babysitter workflow.