brainstorm
/brainstorm
TRIGGER when: asked to brainstorm, think through, explore, or pressure-test a technical idea or decision through conversation. Interviews adaptively, asks one question at a time, and closes with a chat recap. For technical products, architecture, infrastructure, tools, operations, and engineering workflows. Written design/specification and task-list requests belong to $kk:design; durable domain glossary/reference kits to $kk:model; implementation and fixes to $kk:implement. Not for nontechnical brainstorming.
- Author
- serpro69 ↗
- Repository
- claude-toolbox ↗
- Licence
- Apache-2.0
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 34
- Scripts
- 0
- HTML comments
- 1
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- 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
TRIGGER when: asked to brainstorm, think through, explore, or pressure-test a technical idea or decision through conversation. Interviews adaptively, asks one question at a time, and closes with a chat recap. For technical products, architecture, infrastructure, tools, operations, and engineering workflows. Written design/specification and task-list requests belong to $kk:design; durable domain glossary/reference kits to $kk:model; implementation and fixes to $kk:implement. Not for nontechnical brainstorming.
Original author description
TRIGGER when: asked to brainstorm, think through, explore, or pressure-test a technical idea or decision through conversation. Interviews adaptively, asks one question at a time, and closes with a chat recap. For technical products, architecture, infrastructure, tools, operations, and engineering workflows. Written design/specification and task-list requests belong to $kk:design; durable domain glossary/reference kits to $kk:model; implementation and fixes to $kk:implement. Not for nontechnical brainstorming.
How it works
- Workflow
- Inspiration
SKILL.md preview
--- name: brainstorm description: | TRIGGER when: asked to brainstorm, think through, explore, or pressure-test a technical idea or decision through conversation. Interviews adaptively, asks one question at a time, and closes with a chat recap. For technical products, architecture, infrastructure, tools, operations, and engineering workflows. Written design/specification and task-list requests belong to $kk:design; durable domain glossary/reference kits to $kk:model; implementation and fixes to $kk:implement. Not for nontechnical brainstorming. --- <!-- codex: tool-name mapping applied. See .codex/scripts/session-start.sh --> # Brainstorm a Technical Idea Help the user reach their next decision: pursue, discard, narrow, or investigate an idea. Match depth and vocabulary to their needs, whether they are a developer, architect, or anyone thinking through a technical topic. An implementation-ready specification is not required. Keep the working context and result in the conversation. Research is read-only through project files and web sources; do not search knowledge stores or session vaults, index memory, create project files, saved notes, temporary interview artifacts or task records, or mutate external resources. This boundary covers the skill's actions, not the host application's transcript storage. ## Workflow **Mandatory order — instructions before engagement.** The entry steps are strictly sequential: fully load this SKILL.md and both references below before researching project content, refining the idea, or asking interview questions. After loading, repeat the interview/research loop as needed, then close at sufficient clarity for the user's next decision. 1. **Load reasoning references.** Read [shared-ideation-frameworks.md](shared-ideation-frameworks.md) and [shared-idea-refinement-criteria.md](shared-idea-refinement-criteria.md). They supply lenses, not a mandatory questionnaire: apply relevant alternatives, constraint mapping, failure scenarios, and assumption audits. Product-market, adoption, differentiation, and MVP questions are context-dependent; omit them when they do not help the technical decision. 2. **Establish the current decision.** Use the idea and context already supplied. Ask a framing question only to resolve a real ambiguity about the problem or next decision; no ceremonial confirmation, persona interview, or numerical success metric is required. If the requested output is ambiguous between conversation and a written artifact, clarify that output before assuming permission to create anything. 3. **Interview and investigate.** Keep settled decisions, assumptions, open questions, and their dependencies in conversational context. - Ask one question at a time: the highest-value question whose prerequisites are understood. Prefer meaningful choices when useful; explain a recommendation when evidence supports one. Use open questions when choices would bias the answer. - Challenge contradictions and weak assumptions directly and constructively. Explore relevant alternatives and their costs rather than endorsing the first proposal. When a premise changes, reopen the affected conclusions while preserving unrelated settled decisions. - Read relevant project files, documentation, or web sources when evidence could change the advice. Target the current uncertainty; a repository and an initial broad inspection are not prerequisites. Research a discoverable fact instead of asking the user to repeat it. Distinguish observed evidence, assumptions, recommendations, and user decisions. When evidence is unavailable, state the uncertainty and its effect on the decision; continue useful discussion that does not depend on it. 4. **Converge and close in chat.** Stop when the idea, rationale, meaningful trade-offs, material uncertainties, and next decision are clear enough. Do not exhaust every branch or turn a blocking unknown into a premature recommendation to build. Recap settled decisions with their rationale, open assumptions that could change direction, details that can wait, and the next decision or investigation. If the user stops early, give a truthful partial recap without further interrogation or claiming the idea is validated. Written planning may be a useful next step: suggest `$kk:design` when appropriate, but do not load or invoke it, begin implementation, or create artifacts automatically. A later user request to write or build starts that workflow. The recap supplies context for its confirmations; it does not waive `$kk:design`'s gates or prevent decisions from being revisited. ## Inspiration The prerequisite-aware interview and separation of researched facts from user decisions draw on [Matt Pocock's grilling skill, pinned at `85f83d3`](https://github.com/mattpocock/skills/blob/85f83d3fde1d3a90d5c9a657f6998c79a6c37308/skills/productivity/grilling/SKILL.md). This workflow adapts those ideas to one question at a time and decision-level closure; the source is attribution, not a runtime instruction dependency.
Files in this package (34)
- SKILL.md 5 KB
- shared-idea-refinement-criteria.md 6 KB
- shared-ideation-frameworks.md 6 KB
- evals/README.md 8 KB
- evals/architecture-audience/eval.json 2 KB
- evals/architecture-audience/oracle/runbook.md 3 KB
- evals/changed-premise/eval.json 2 KB
- evals/changed-premise/oracle/runbook.md 3 KB
- evals/direct-implementation-request/eval.json 1 KB
- evals/direct-implementation-request/oracle/runbook.md 2 KB
- evals/direct-implementation-request/test-files/status.txt 1 KB
- evals/discoverable-project-fact/eval.json 2 KB
- evals/discoverable-project-fact/oracle/runbook.md 3 KB
- evals/discoverable-project-fact/test-files/ops/release-queue.md 1 KB
- evals/domain-kit-request/eval.json 1 KB
- evals/domain-kit-request/oracle/runbook.md 3 KB
- evals/domain-kit-request/test-files/records.json 1 KB
- evals/domain-kit-request/test-files/requirements.md 1 KB
- evals/early-stop/eval.json 1 KB
- evals/early-stop/oracle/runbook.md 2 KB
- evals/explicit-design-invocation/eval.json 1 KB
- evals/explicit-design-invocation/oracle/runbook.md 4 KB
- evals/explicit-design-invocation/test-files/README.md 1 KB
- evals/loose-technical-idea/eval.json 2 KB
- evals/loose-technical-idea/oracle/runbook.md 3 KB
- evals/no-repository/eval.json 2 KB
- evals/no-repository/oracle/runbook.md 3 KB
- evals/nontechnical-non-trigger/eval.json 1 KB
- evals/nontechnical-non-trigger/oracle/runbook.md 2 KB
- evals/unavailable-evidence/eval.json 2 KB
- evals/unavailable-evidence/oracle/runbook.md 3 KB
- evals/written-design-request/eval.json 1 KB
- evals/written-design-request/oracle/runbook.md 4 KB
- evals/written-design-request/test-files/README.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · serpro69/claude-toolbox | 100 | Apache-2.0 |
| yonatangross/orchestkit | 100 | MIT |
| yonatangross/orchestkit | 100 | MIT |
| vanducng/skills | 100 | MIT |
| Kanevry/session-orchestrator | 100 | MIT |
| nigelng/nng-kit | 100 | MIT |
| joris887/exosuit | 100 | MIT |
| duronext/jig | 100 | MIT |
| verygoodopensource/vgv-wingspan | 100 | MIT |
Database snapshot: 13.11.2026 · package version 5ca7a20a6c5d (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
- 100brainstorming
Interactive design exploration before implementation. Use when the user has a vague idea or feature request and no written spec. Asks one focused question at a time, writes a spec, and blocks implementation until approved. Triggers include 'I want to build', 'let's brainstorm', 'help me spec out'. - 100ql-brainstorm
Part of the quantum-loop autonomous development pipeline (brainstorm \u2192 spec \u2192 plan \u2192 execute \u2192 review \u2192 verify). Deep Socratic exploration of a feature idea before implementation. Asks questions one at a time, proposes 2-3 alternative approaches with… - 90idea
Code-first brainstorming — the proposal IS code, committed on an `idea/<topic>` branch the user reviews as a diff in their IDE; chat carries only the branch name, key decisions and open questions. Use for any technical proposal ("how would you do X", "sketch this", "propose an… - 100pointer
Runs a bounded evidence conversation over an existing implementation, asks one decision-changing question at a time, presents correction options, and applies the accepted correction plan once. Use when the user invokes /glasses:pointer, asks Pointer to inspect or correct an… - 100openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change. - 100openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.