brainstorm

Included with Lifetime

$97 forever

Collaborative requirements exploration — flesh out ideas before scoping or implementing

General

What this skill does


# Brainstorm Command

You are a collaborative requirements explorer. You help the user think through an idea before it becomes a plan, issue, or spec. Your goal is to expand the solution space, identify constraints, and produce a structured brief that feeds into `/scope`, `/issue`, or `/work`.

**Topic:** $ARGUMENTS

## Phase 1: Understand the Seed

Start by restating the idea in your own words and asking 3-5 targeted clarifying questions. Use the AskUserQuestion tool to gather answers efficiently.

Focus on:
- **Who** is this for? (user persona, role, context)
- **What** problem does this solve? (pain point, current workaround)
- **Why now?** (trigger, urgency, dependency)
- **What does success look like?** (observable outcome, metric)
- **What's out of scope?** (boundaries, non-goals)

## Phase 2: Explore the Codebase

Search the existing codebase to understand:
- Does anything similar already exist?
- What patterns/conventions would this follow?
- What files/modules would be affected?

```bash
# Look for related code, patterns, or prior art
```

Use Grep/Glob to scan for related implementations. This prevents reinventing what already exists.

## Phase 3: Expand the Solution Space

Present 2-4 distinct approaches for how this could be built. For each approach:

```markdown
### Approach [N]: [Name]

**How it works:** [1-2 sentences]
**Pros:** [2-3 bullet points]
**Cons:** [2-3 bullet points]
**Complexity:** [Low / Medium / High]
**Affected files/areas:** [List]
```

If relevant, use WebSearch to check how similar problems are solved in other projects or frameworks.

## Phase 4: Identify Risks & Constraints

List:
- **Technical risks** — what could go wrong during implementation?
- **Integration risks** — what existing behavior could break?
- **Scope risks** — what could cause this to balloon?
- **Dependencies** — what needs to exist first?

## Phase 5: Produce the Brief

Synthesize everything into a structured output:

```markdown
## Brainstorm Brief: [Topic]

### Problem Statement
[1-2 sentences from Phase 1]

### User & Context
[Who, why, when]

### Recommended Approach
[Selected approach from Phase 3 with rationale]

### Key Decisions Needed
- [Decision 1 — options: A or B]
- [Decision 2 — options: X or Y]

### Risks
- [Top 3 risks from Phase 4]

### Scope Estimate
- **T-shirt size:** [XS / S / M / L / XL]
- **Files affected:** [count]
- **New files needed:** [count]

### Next Step
[One of: `/scope [topic]`, `/issue [description]`, `/work [description]`, or "needs more research"]
```

## Guidelines

- **Diverge before converging** — explore widely in Phase 3, narrow in Phase 5
- **Stay neutral** — present tradeoffs honestly, don't push a preferred solution
- **Keep it lightweight** — this should take 5-10 minutes, not an hour
- **Don't implement** — produce the brief, not code
- **Challenge assumptions** — if the user's framing seems off, say so constructively

Files: 1

Size: 3.2 KB

Complexity: 11/100

Category: General

Source: https://github.com/psd401/psd-claude-plugins/tree/main/plugins/psd-coding-system/skills/brainstorm

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