deep-brainstorming
Use when brainstorming a product or feature where multiple valid technology choices exist and the wrong one is costly, when the user asks for 'objectively best' or 'highest quality', or when the domain has tools/frameworks where marketing or popularity biases could mislead research agents. Also use when starting architecture decisions, evaluating tech stacks, or when the user mentions bias, vendor lock-in, hallucinated benchmarks, or wants research-backed decisions rather than default recommendations.
npx skills add majiayu000/claude-skill-registry --skill deep-brainstorming --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Deep Brainstorming Research-hardened brainstorming that catches biases agents naturally introduce. Collapses what would otherwise be 3-4 sessions of iterative discovery into one disciplined session. **REQUIRED:** Run a standard brainstorming pass first (e.g., `superpowers:brainstorming` or equivalent). This skill augments brainstorming output — it does not replace it. ## When to Use ```dot digraph when { "Starting brainstorming?" [shape=diamond]; "Multiple valid tech choices?" [shape=diamond]; "Wrong choice costly to reverse?" [shape=diamond]; "Use regular brainstorming" [shape=box]; "Use deep brainstorming" [shape=box, style=bold]; "Starting brainstorming?" -> "Multiple valid tech choices?"; "Multiple valid tech choices?" -> "Use regular brainstorming" [label="no"]; "Multiple valid tech choices?" -> "Wrong choice costly to reverse?"; "Wrong choice costly to reverse?" -> "Use regular brainstorming" [label="no — easy to swap"]; "Wrong choice costly to reverse?" -> "Use deep brainstorming" [label="yes"]; } ``` ## Intensity Selector Pick intensity based on stakes and time budget. Default to **Standard** unless stakes clearly call for Quick or Thorough. | Level | Research Rounds | Bi
- When to Use
- Intensity Selector
- Process Overview
- Phase 1: Sanitize the Vision
- Phase 2: Research with Clean Prompts
- Phase 3: Bias Audit
- Phase 4: Independent Verification
- Phase 5: Claim Provenance
- Phase 6: Progressive File Capture
- Phase 7: Three-Phase Review
- Phase 8: "Objectively Best?" Quality Gate
- Transition to Planning
- The 9 Bias Types (Quick Reference)
- Common Mistakes
What does the deep-brainstorming skill do?
Use when brainstorming a product or feature where multiple valid technology choices exist and the wrong one is costly, when the user asks for 'objectively best' or 'highest quality', or when the domain has tools/frameworks where marketing or popularity biases could mislead research agents. Also use when starting architecture decisions, evaluating tech stacks, or when the user mentions bias, vendor lock-in, hallucinated benchmarks, or wants research-backed decisions rather than default recommendations.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill deep-brainstorming --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.