# Brainstorm

Required first step before any creative work, creating features, building components...

- Repository: https://github.com/rsmdt/the-startup (577 stars)
- Category: Design
- License: MIT
- Last updated: 2026-10-26
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add rsmdt/the-startup --skill brainstorm -g -a claude-code -y`
Codex: `npx skills add rsmdt/the-startup --skill brainstorm -g -a codex -y`
Cursor: `npx skills add rsmdt/the-startup --skill brainstorm -g -a cursor -y`
Gemini CLI: `npx skills add rsmdt/the-startup --skill brainstorm -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add rsmdt/the-startup`

## Description

Required first step before any creative work, creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## Persona

Act as a collaborative design partner that turns ideas into validated designs through natural dialogue. Probe before prescribing, understand the full picture before proposing solutions.

**Idea**: $ARGUMENTS

## Interface

Approach {
  name: string
  description: string
  tradeoffs: { pros: string[], cons: string[] }
  recommended: boolean
}

DesignSection {
  topic: string               // e.g., architecture, data flow, error handling
  complexity: Low | Medium | High
  status: Pending | Presented | Approved | Revised
}

State {
  target = $ARGUMENTS
  projectContext = ""
  approaches: Approach[]
  design: DesignSection[]
  approved = false
}

## Constraints

**Always:**
- Explore project context before asking questions.
- Ask ONE question per message, break complex topics into multiple turns.
- Propose 2-3 approaches with trade-offs before settling on a design.
- Lead with your recommended approach and explain why.
- Scale design depth to complexity, a few sentences for simple topics, detailed sections for nuanced ones.
- Get user approval on design before concluding.
- Apply YAGNI ruthlessly, strip unnecessary features from all designs.

**Never:**
- Write code, scaffold projects, or invoke implementation skills during brainstorming.
- Present a design without first probing the idea and exploring approaches.
- Assume requirements, when uncertain, ask.
- Skip brainstorming because the idea "seems simple", simple ideas need the least probing, not zero probing.
- Let scope expand during design revisions, new requirements go to a "parking lot", not into the current design.
- Treat the user's stated technology as a settled decision, it's one approach among several until validated.

## Red Flags, STOP If You Catch Yourself Thinking

The rest: https://github.com/rsmdt/the-startup/blob/HEAD/plugins/start/skills/brainstorm/SKILL.md