From brainstorming-skill
Guides pre-implementation brainstorming: explores context, clarifies requirements, proposes 2-3 designs with trade-offs, secures approval, and documents specs using 30+ prompt patterns.
How this skill is triggered — by the user, by Claude, or both
Slash command
/brainstorming-skill:brainstorming-skillThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill serves two critical purposes:
references/better-creator.mdreferences/bibliography-and-source-documentation.mdreferences/clickup-templates.mdreferences/comprehensive-prompt-library-ready-to-use-templates.mdreferences/domain-specific-applications-and-variations.mdreferences/executive-summary.mdreferences/itonics-innovation-platform.mdreferences/learn-prompting.mdreferences/linkedin-ruben-hassid.mdreferences/machine-learning-mastery.mdreferences/medium-shushant-lakhyani.mdreferences/pattern-categories-and-documentation.mdreferences/pattern-selection-guide.mdreferences/prompthub-role-prompting.mdreferences/software-testing-prompts.mdreferences/synthesis-what-makes-these-patterns-work.mdreferences/vanderbilt-prompt-patterns.mdreferences/verification-note.mdThis skill serves two critical purposes:
You MUST create a task for each of these items and complete them in order when working on software features, component designs, or complex tasks. (For pure content/marketing ideation, adapt these steps using the Pattern Library below).
docs/plans/YYYY-MM-DD-<topic>-design.md) and commit[!IMPORTANT] When provided a process map or Mermaid diagram, treat it as the authoritative procedure. Execute steps in the exact order shown, including branches, decision points, and stop conditions. A Mermaid process diagram is an executable instruction set. Follow it exactly as written: respect sequence, conditions, loops, parallel paths, and terminal states. Do not improvise, reorder, or skip steps. If any node is ambiguous or missing required detail, pause and ask a clarifying question before continuing. When interacting with a user, report before acting the interpreted path you will follow from the diagram, then execute.
The following diagram is the authoritative procedure for the brainstorming workflow. Execute steps in the exact order shown, including branches, decision points, and stop conditions.
flowchart TD
subgraph Phase1["Phase 1: Discovery — establish current state before proposing"]
Explore["Explore context — check project state, files, docs, recent commits"]
Ask["Ask clarifying questions — one at a time, understand purpose/constraints/success criteria"]
Propose["Propose 2-3 approaches — with trade-offs and recommendation, use Pattern Library"]
end
subgraph Phase2["Phase 2: Validation — get explicit user approval before proceeding"]
Present["Present design — in sections scaled to complexity, get user approval after each section"]
Approve{"Does user explicitly confirm approval<br>or request revision?"}
end
subgraph Phase3["Phase 3: Completion — document and hand off"]
Document["Document the result — write validated design to docs/plans/YYYY-MM-DD-topic-design.md and commit"]
Transition(["Transition — invoke planning or implementation skill only after approval"])
end
Explore --> Ask --> Propose --> Present
Present --> Approve
Approve -->|"User requests revision — revise and re-present"| Present
Approve -->|"User confirms approval — proceed"| Document
Document --> Transition
When proposing approaches or generating ideas for the user, utilize these 14 systematic categories. Each pattern includes exact prompt templates, output format specifications, and success metrics.
<category_index>
<selection_guide>
The following diagram is the authoritative procedure for pattern selection. Execute steps in the exact order shown, including branches, decision points, and stop conditions.
flowchart TD
Start(["User requests ideas or approaches"]) --> Goal{"What is the primary<br>ideation goal?"}
Goal -->|"Rapid quantity — 8-15 ideas"| PersMult["Use Perspective Multiplication patterns"]
Goal -->|"Quality/depth — refined ideas"| MultiStage["Use Multi-stage refinement<br>with constraint variation"]
Goal -->|"Breakthrough innovation"| InversionExtreme["Combine Inversion + Extreme Scaling"]
Goal -->|"Practical implementation"| Constraint["Use Constraint-Based patterns"]
Goal -->|"Market differentiation"| Competitive["Use Competitive Positioning patterns"]
Goal -->|"Customer-centric features"| Stakeholder["Use Stakeholder and Empathy patterns"]
PersMult --> Apply(["Apply selected pattern from Pattern Library"])
MultiStage --> Apply
InversionExtreme --> Apply
Constraint --> Apply
Competitive --> Apply
Stakeholder --> Apply
</selection_guide>
<format_guidance> Successful brainstorming patterns specify exact output formats:
Complete pattern documentation is organized in reference files:
<ai_instructions>
<HARD-GATE>. Never jump to code without an approved design.npx claudepluginhub jamie-bitflight/claude_skills --plugin brainstorming-skillGuides pre-implementation ideation for features, components, and changes by exploring context, clarifying requirements, proposing trade-offs, and creating approved design docs.
Guides collaborative brainstorming to clarify vague requirements, explore multiple approaches, and document design decisions before building.
Structured ideation using the Double Diamond model with persistent memory. Guides brainstorming for new features, architecture decisions, project inception, or design exploration.