structured-brainstorming/skills/structured-brainstorming/SKILL.md
This skill should be used when the user needs to brainstorm, explore a problem space, think through design decisions, compare approaches, evaluate trade-offs, is stuck on an approach, or wants to explore multiple solutions. Trigger phrases include 'how should I approach this', 'what are my options', 'help me think through this', 'help me decide between X and Y', 'what are the pros and cons', 'weigh the trade-offs', 'compare these approaches', and 'I'm stuck'. Covers 8 bias-counteracting methods with user-gated parallel subagent exploration for deep dives.
npx skillsauth add oborchers/fractional-cto structured-brainstormingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Structured brainstorming applies specific thinking methods that counteract LLM reasoning biases during problem exploration. Without deliberate structure, LLM responses gravitate toward the most probable answer, skip genuine alternative exploration, and converge prematurely on conventional solutions.
This skill provides 8 methods selected because they fight known LLM failure modes. The /structured-brainstorming:brainstorm command drives an interactive flow where the user decides when to dispatch parallel brainstorm-explorer subagents for deep multi-angle exploration.
LLMs have specific reasoning biases that structured methods counteract:
| Bias | What Happens | Counteracting Method | |------|-------------|----------------------| | Premature convergence | Jumps to "the answer" without exploring alternatives | Diverge-then-Converge | | Sycophancy | Leans toward what the user seems to want | Inversion / Pre-Mortem | | Mode collapse | "Different" ideas are variations of the same idea | Constraint Manipulation | | Shallow exploration | Stays in the obvious solution neighborhood | First Principles Decomposition | | Authority bias | Defaults to best practices / conventional wisdom | Assumption Surfacing | | Single perspective | Thinks only as "helpful assistant" | Perspective Forcing | | Local search | Explores only adjacent solutions | Analogy Search | | Vague decomposition | Breaks problems into overlapping, incomplete parts | MECE Decomposition |
| # | Method | Core Question | Best For | |---|--------|--------------|----------| | 1 | First Principles Decomposition | "What is actually true here vs. assumed?" | Challenging conventional approaches | | 2 | Inversion / Pre-Mortem | "What would make this fail spectacularly?" | Risk assessment, robustness | | 3 | Constraint Manipulation | "What if I add/remove/reverse a constraint?" | Breaking out of local optima | | 4 | Perspective Forcing | "How does the [user/operator/critic/...] see this?" | Blind spot detection | | 5 | Analogy Search | "Where has a similar problem been solved?" | Novel approaches from other domains | | 6 | MECE Decomposition | "What are the non-overlapping parts of this?" | Systematic coverage | | 7 | Assumption Surfacing | "What am I taking for granted?" | Hidden constraint discovery | | 8 | Diverge-then-Converge | "How many distinct options exist before I evaluate?" | Overcoming premature convergence |
For detailed method descriptions, step-by-step processes, and application prompts, consult the corresponding file in references/.
Match problem type to recommended methods:
| Problem Type | Start With | Add If Needed | |-------------|-----------|---------------| | "How should I design X?" | First Principles, MECE | Perspective Forcing, Analogy | | "I'm stuck on X" | Assumption Surfacing, Constraint Manipulation | Inversion, Analogy | | "What could go wrong with X?" | Inversion / Pre-Mortem, Perspective Forcing | Assumption Surfacing | | "What are my options for X?" | Diverge-then-Converge, MECE | Constraint Manipulation, Analogy | | "Should I do X or Y?" | First Principles, Inversion | Perspective Forcing, Assumption Surfacing | | "How do others solve X?" | Analogy Search, Perspective Forcing | First Principles | | "How do I prioritize X?" | MECE Decomposition, Diverge-then-Converge | Perspective Forcing |
For focused problems where 2-3 methods suffice, apply methods directly without dispatching agents. Use the method selection table to pick methods, then apply each following its reference file. Spend enough depth per method to produce a concrete finding, not a platitude.
For complex, high-stakes, or multi-faceted problems, use the /structured-brainstorming:brainstorm command to dispatch parallel brainstorm-explorer agents. Each agent applies its assigned methods with the same depth, using the reference files for the detailed step-by-step process.
The /structured-brainstorming:brainstorm command asks the user whether to dispatch parallel brainstorm-explorer subagents or rephrase the problem statement first. When the user chooses to dispatch, spawn agents in parallel using the Agent tool — each exploring the problem from a different angle simultaneously.
Agent dispatch pattern:
Each agent receives: the problem statement, the assigned methods with their reference material, and instructions to explore deeply. Give agents access to the codebase (Read, Grep, Glob). If WebSearch is available, also grant it for cross-domain research in Analogy Search and Constraint Manipulation.
After all agents complete, synthesize: identify convergent themes, genuine disagreements, and surprising findings. Present a structured recommendation with the full exploration visible.
Every brainstorming session produces:
Detailed method descriptions, step-by-step processes, and application prompts:
references/first-principles-decomposition.md -- Stripping assumptions, decomposing to fundamentals, rebuilding from ground truthreferences/inversion-and-pre-mortem.md -- Working backwards from failure, forcing pessimistic analysisreferences/constraint-manipulation.md -- Adding, removing, and reversing constraints to escape local optimareferences/perspective-forcing.md -- Stakeholder simulation and structured role-based thinkingreferences/analogy-search.md -- Cross-domain pattern matching and analogical transferreferences/mece-decomposition.md -- Non-overlapping, collectively exhaustive problem breakdownsreferences/assumption-surfacing.md -- Identifying and challenging hidden assumptionsreferences/diverge-then-converge.md -- Separating idea generation from idea evaluationWorked brainstorming sessions:
examples/inline-brainstorm.md -- Event system design (5 methods applied, showing expected depth per method)examples/parallel-agent-exploration.md -- Auth system greenfield (4 subagents, full parallel exploration with user-gated dispatch)tools
This skill should be used when the user invokes any /plan-* command from the planning-tools plugin (/plan-context, /plan-master, /plan-open-questions, /plan-verify, /plan-tick, /plan-progress, /plan-delete), asks how Claude Code's plan files work, asks where plans are stored, asks to author or audit a multi-phase master planning document, asks how to walk through a plan's Open Questions interactively, asks how to write progress entries, or mentions ~/.claude/plans/ or .claude/planning-tools.local.md. Provides the index of planning-tools commands, the master-plan workflow lifecycle, the v0.3.0+ list-shape mandate (phases and questions as headings + bulleted scope items, never tables), the v0.3.2+ plain-bullet shape (no `- [ ]` checkboxes — heading emoji is the sole tick signal), the progress-entry methodology, and the mechanics of Claude Code's plan-mode file storage.
testing
This skill should be used when the user is adjusting spacing, padding, margins, content density, section gaps, vertical rhythm, or separation between elements. Also applies when reviewing whether a design feels cramped or too sparse, choosing between borders and whitespace for separation, or defining a spacing system. Covers the 4px/8px spacing system, macro vs micro whitespace, content density spectrum, separation techniques (whitespace > background shifts > borders), and vertical rhythm.
development
This skill should be used when the user is defining brand personality in design, choosing between illustration and photography, adding motion or animation, creating visual motifs, ensuring layout variety, customizing CSS framework defaults, or calibrating the level of creative expression for a given context. Covers Lavie & Tractinsky's expressive aesthetics, the expression spectrum (restrained to bold), brand personality translation, illustration systems, photography direction, and template independence.
development
This skill should be used when the user is establishing visual importance, designing headings, creating focal points, designing CTAs or buttons, arranging label-data relationships, implementing scanning patterns (F-pattern, Z-pattern), or ensuring one dominant element per screen. Covers the three levers of hierarchy (size, weight, color), three-tier information architecture, the 'emphasize by de-emphasizing' principle, CTA design, and label-data relationships.