Skip to content
Skills Library
Management & product · Planning

brainstorm

/brainstorm

Use when the ask is still fuzzy and no direction is chosen yet: "not sure what we want", several ways to go, or a scope to settle before any plan is written.

Licence
MIT
Last repository change
13.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
1
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

Use when the ask is still fuzzy and no direction is chosen yet: "not sure what we want", several ways to go, or a scope to settle before any plan is written.

Triggers from the description

not sure what we want
Original author description

Use when the ask is still fuzzy and no direction is chosen yet: "not sure what we want", several ways to go, or a scope to settle before any plan is written.

How it works

  1. When
  2. The loop
  3. Guardrails
  4. DoD (this skill's contribution)
Original SKILL.md headings · 44 lines, 468 words
SKILL.md preview
---
name: brainstorm
description: |
  Use when the ask is still fuzzy and no direction is chosen yet: "not sure what we want", several ways to go,
  or a scope to settle before any plan is written.
---

# Brainstorm — diverge before you converge

<!-- routing-eval reads the next line; why it sits in the body: AGENT_TEMPLATE.md -->
Trigger phrases: "brainstorm", "explore options", "not sure what we want", "help me scope", "ideate"

## When
The ask is **under-defined**: the goal, the users, or the shape of the solution aren't clear yet, so jumping
straight to `spec-planning` would just plan the wrong thing. This is the front-end of planning, not a
replacement — brainstorm *diverges* (widens the option space), spec-planning *converges* (breaks the chosen
option into tasks). If scope is already clear, skip this and go straight to [[spec-planning]].

## The loop
1. **Frame the real problem** — restate the request as the underlying need in one sentence ("the user wants
   X so that Y"). Separate the stated solution from the goal; often the solution is negotiable, the goal isn't.
2. **Diverge — generate distinct directions.** Produce **2–4 genuinely different** approaches, not variations
   of one. For each: the core idea, who it serves, the main trade-off. Include a deliberately cheap/minimal
   option (fight gold-plating early).
3. **Surface the unknowns** — list assumptions and open questions that would change the answer. Mark which are
   **blocking** (must resolve before planning) vs. deferrable.
4. **Converge — ask, don't guess.** Present the directions as **explicit numbered options** and let the user
   choose (CLAUDE.md discipline: a decision point = multiple choice, never a prose either/or). Record the
   chosen direction + the rejected ones with the one-line reason they lost.
   How to put a question, what is worth asking and what to do when no answer comes:
   `references/asking.md`; `/crew-interview` runs the whole round of questions as a command.
5. **Hand off.** The chosen direction + resolved constraints flow into `spec-planning`; a lasting
   architectural choice made here is recorded with [[adr]].

## Guardrails
- **Bounded, not open-ended.** Divergence has a stop: 2–4 options, then converge. Endless ideation with no
  decision is the failure mode, not thoroughness.
- **No premature convergence either.** Don't collapse to the first idea to look decisive — the point is that
  the option space was actually explored before a direction was picked.
- **Evidence over invention.** Read the existing code/data and state assumptions explicitly; a plausible guess
  presented as fact is worse than a named unknown.
- **Token discipline** ([[token-budget]]): the options + the decision are a short summary to the main thread;
  push a long exploration to `docs/DISCOVERY.md` and return the option headings + the choice.

## DoD (this skill's contribution)
- The real goal is stated separately from the requested solution.
- 2–4 distinct directions exist, each with its trade-off, including a minimal option.
- Blocking unknowns are named and were asked as explicit options — nothing ambiguous was filled by guessing.
- A direction is chosen and ready to enter [[spec-planning]] (rejected options logged with their reason).
Files in this package (2)
  • SKILL.md 3 KB
  • references/asking.md 3 KB

Versions

RepositoryScoreLicence
This page · byerlikaya/claude-starter-kit90MIT
yonatangross/orchestkit100MIT
yonatangross/orchestkit100MIT
vanducng/skills100MIT
Kanevry/session-orchestrator100MIT
nigelng/nng-kit100MIT
joris887/exosuit100MIT
duronext/jig100MIT
verygoodopensource/vgv-wingspan100MIT

Database snapshot: 13.11.2026 · package version cf58cdbc0e10 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100brainstorm-beagle
    Use when the user has a fuzzy idea and wants to shape it into a concrete project spec before planning or building. Triggers on: \"brainstorm this\", \"I have an idea for...\", \"help me think through this project\", \"what should I build\", \"spec this out\". Also catches vague…
  • 100discovering
    Clarify goals, scope, and requirements to produce an agreed direction. Use when idea is vague, multiple interpretations exist, scope is undefined, or stakeholders need alignment before technical work begins
  • 100coach
    Use when planning a fork: more than one defensible direction and no active standard covers it. Settle the plan before work starts. Do not use merely because a request is vague or underspecified; vagueness takes a clarifying question, not a standard.
  • 100rb-brainstorm
    Interactive brainstorming for ralph-ban projects. This skill should be used when the user has a fuzzy idea, vague goal, or problem statement that needs exploration before it becomes board cards. Triggers on "brainstorm", "explore an idea", "I want to build", "let's think about",…
  • 90ce:brainstorm
    Explore requirements and approaches through collaborative dialogue before writing a right-sized requirements document and planning implementation. Use for feature ideas, problem framing, when the user says ''let''s brainstorm'', or when they want to think through options before…
  • 90grilling
    Grill a plan, decision, or idea until it is clear: ask the questions that can be answered now, wait for the answers, and write each round into a testimony. It writes the testimony and nothing else: what the discussion settled is written by `adr` and `glossary`, run by…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.