Brainstorm
7 skills built from studying how Anthropic designs agents internally. ~700 lines, zero fluff.
npx -y skills add jessedegans/jstack --skill brainstormAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use before starting any feature, entering unfamiliar code, or beginning a non-trivial task. Enforces understanding before action. No code, no scaffolding, no implementation until the problem is explored and a direction is approved. Use when: user says "let's build X", "add feature Y", "I want to create Z", or begins work on something that needs design thinking.
SKILL.md
2.2 KB, 426 tokens by cl100k_base, as published. Nobody here has run it
Brainstorm
The Rule
No code until you understand the problem. No scaffolding, no "let me just set up the structure," no implementation. Explore first.
The Process
1. Explore what exists
Before asking a single question:
- Read relevant files, check recent commits, understand the current state
- If there's a codebase, understand its patterns before proposing anything new
- If there's prior work, understand why it was done that way
2. Ask clarifying questions
One question at a time. Prefer multiple choice when possible.
Focus on:
- Purpose: What problem does this solve? Who is it for?
- Constraints: What can't change? What's the budget (time, complexity, scope)?
- Success criteria: How will we know this works?
- Scope: What's in, what's explicitly out?
Don't ask questions you can answer by reading the code or docs.
3. Propose 2-3 approaches
For each approach:
- What it is (one sentence)
- Key trade-off (what you gain vs. what you give up)
- Your recommendation and why
Lead with your recommended option. Be opinionated, not neutral.
4. Get approval
Present the chosen direction clearly. Wait for explicit approval before writing any code.
If the user says "just do it" without engaging with the design, that's fine. The point isn't ceremony. The point is that you've thought about it even if they haven't.
Rationalization Prevention
| Thought | Reality |
|---|---|
| "This is too simple to need brainstorming" | Simple things have hidden assumptions. Ask one question. |
| "I already know what to build" | Then it'll take 30 seconds to confirm. Do it anyway. |
| "Let me just scaffold the structure first" | Structure IS a design decision. Brainstorm first. |
| "The user seems impatient" | A 2-minute brainstorm prevents a 2-hour rewrite. |
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.