brainstorming
Structured idea exploration from vague to direction, or pressure-test of an existing idea or plan. Two paths: greenfield maps a problem space from scratch; relentless stress-tests existing thinking to expose weakness, validate, refine, or surface a pivot. Diverge generates alternatives, converge evaluates trade-offs, capture produces the artifact. Use when brainstorming, exploring options, comparing approaches, rethinking a direction, considering a pivot, asking for a second opinion, finding holes in a plan, or grilling assumptions before building. Not for documenting a finalized direction.
What this skill does
# Brainstorming
Structured idea exploration from vague to direction.
## Workflow
```
trigger --> detect path --> discover --> diverge --> converge --> capture
^________________________________| (if no viable direction)
```
Detect path from entry state — greenfield when no concrete idea is
present, relentless when an idea or plan exists regardless of
maturity. Discover maps the problem space. Diverge generates
alternatives. Converge evaluates trade-offs and picks a direction.
Capture produces the artifact.
## References
- Discovery (any entry) → [discovery.md](references/discovery.md)
- Diverge (after discovery gate) → [diverge.md](references/diverge.md)
- Converge (after 4+ alternatives) → [converge.md](references/converge.md)
- Capture (after user approves direction) → [capture.md](references/capture.md)
Workflow always starts with discovery. Load each reference when its
phase begins.
## Guidelines
- Generate at least 4 alternatives during diverge, including non-obvious
options
- Challenge every alternative with trade-offs during converge
- Require explicit user approval before capturing the direction
- Mark unknowns as TBD rather than inventing constraints
- Stay at the problem-and-direction level; defer implementation choices
## Anti-Pattern: Premature Convergence
Stopping at 2-3 obvious alternatives skips the value of brainstorming.
The non-obvious option is often the one worth choosing — or the one that
reframes the problem. When pressure to commit shows up early, push for
breadth first; converge only after the space has been explored.
## Anti-Pattern: Hidden Trade-offs
Recommending a direction without surfacing what it costs misleads the
user. Every recommendation must name the gain and the give-up explicitly.
If a trade-off feels too small to mention, it probably isn't.
## Anti-Pattern: Solution-First Discovery
In greenfield, when the user describes what to build before why,
discovery has not happened — they have a hypothesis. Redirect to the
problem before generating alternatives. Without grounded motivation,
diverge produces options for an unverified target.
In relentless, the solution is the input by definition. Do not
redirect — discovery maps the assumptions, dependencies, and signals
behind the existing idea or plan so diverge can attack from grounded
vectors.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.