brainstorming

Included with Lifetime

$97 forever

Use when the user explicitly asks to brainstorm. Helps turn ideas into designs through collaborative dialogue.

General

What this skill does

# Brainstorming

Help turn ideas into designs and specs through collaborative dialogue.

## When to Invoke

Only invoke when the user explicitly asks to brainstorm. Examples:
- "Let's brainstorm this feature"
- "I want to brainstorm approaches for X"
- "Can we brainstorm how to solve Y?"

Do not auto-invoke for general implementation tasks or questions.

## Process

### 1. Understand the Context

Start by reviewing the current project:
- Check relevant files, docs, recent commits
- Understand what exists and what constraints apply

### 2. Ask Questions

Explore the idea through questions:
- Ask one question at a time
- Prefer multiple choice when options are clear
- Focus on: purpose, constraints, success criteria, edge cases
- Don't overwhelm - if a topic needs more exploration, ask follow-up questions
- Use your choices tool to prompt the user

### 3. Propose Approaches

Once you understand the problem:
- Propose 2-3 different approaches with trade-offs
- Lead with your recommendation and explain why
- Be direct about pros/cons

### 4. Present the Design

When ready to document:
- Break into sections of 200-300 words
- Check after each section if it looks right
- Cover: architecture, components, data flow, error handling
- Apply YAGNI - remove unnecessary features

If the user asks to handoff, jump ahead to the next phase, such as planning or implementation.

### 5. Update spec.md

If the project has an associated spec.md, consider how the brainstorming session clarified the behavioral specification.
Don't include implementation details, just how the project is intended to be used, function, display, etc.
- be concise and direct. show examples. technical is ok.
- describe intended behavior, but not undefined behavior.
- no slop. no bold. no emojis. simple text like my style.

## Principles

- **One question at a time** - don't overwhelm
- **YAGNI** - remove unnecessary features from designs
- **Explore alternatives** - always propose 2-3 approaches
- **Incremental validation** - present in sections, validate each
- **Be flexible** - go back and clarify when needed

Files: 1

Size: 2.2 KB

Complexity: 5/100

Category: General

Source: https://github.com/williballenthin/aiwilli/tree/main/claude/wb/skills/brainstorming

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts