workflow-brainstorming

workflow-brainstorming is a skill for Claude Code, Codex from Kastalien-Research/thoughtbox. It costs 78 tokens per session (1,314 once invoked), scanned A, original, MIT.

A guided discussion process for deciding what to build before planning or coding it.

In plain words
What is it for?
Use it when a feature request is vague, several solutions seem possible, or the scope needs to be narrowed. It can be skipped for a precise request or a straightforward bug fix.
Why use it?
It helps resolve unclear requirements, compare possible approaches, and discuss trade-offs before implementation begins.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/kastalien-research/thoughtbox/workflow-brainstorming
Any agent
npx skills add Kastalien-Research/thoughtbox --skill workflow-brainstorming
Clone the repo
git clone --depth 1 https://github.com/Kastalien-Research/thoughtbox

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for workflow-brainstorming

README.md
[![agentmods](https://agentmods.dev/badge/skills/kastalien-research/thoughtbox/workflow-brainstorming.svg)](https://agentmods.dev/skills/kastalien-research/thoughtbox/workflow-brainstorming)
Your own site
<a href="https://agentmods.dev/skills/kastalien-research/thoughtbox/workflow-brainstorming"><img src="https://agentmods.dev/badge/skills/kastalien-research/thoughtbox/workflow-brainstorming.svg" alt="Measured on agentmods" height="20"></a>
Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,314 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00078 $0.01314
Opus 5 $0.00039 $0.00657
Sonnet 5 $0.00016 $0.00263
Haiku 4.5 $0.00008 $0.00131

Measured 6d ago against content hash c1c0aa4513a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

workflow-brainstorming scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.agents/skills/workflow-brainstorming/SKILL.md · 190 lines

How it starts

The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Brainstorming

This skill provides detailed process knowledge for effective brainstorming sessions that clarify WHAT to build before diving into HOW to build it.

When to Use This Skill

Brainstorming is valuable when:

  • Requirements are unclear or ambiguous
  • Multiple approaches could solve the problem
  • Trade-offs need to be explored with the user
  • The user hasn't fully articulated what they want
  • The feature scope needs refinement

Brainstorming can be skipped when:

  • Requirements are explicit and detailed
  • The user knows exactly what they want
  • The task is a straightforward bug fix or well-defined change

Core Process

Phase 0: Assess Requirement Clarity

Before diving into questions, assess whether brainstorming is needed.

Signals that requirements are clear:

  • User provided specific acceptance criteria
  • User referenced existing patterns to follow
  • User described exact behavior expected
  • Scope is constrained and well-defined

Signals that brainstorming is needed:

  • User used vague terms ("make it better", "add something like")
  • Multiple reasonable interpretations exist
  • Trade-offs haven't been discussed
  • User seems unsure about the approach

If requirements are clear, suggest: "Your requirements seem clear. Consider proceeding directly to planning or implementation."

Phase 1: Understand the Idea

Ask questions one at a time to understand the user's intent. Avoid overwhelming with multiple questions.

Question Techniques:

  1. Prefer multiple choice when natural options exist

    • Good: "Should the notification be: (a) email only, (b) in-app only, or (c) both?"
    • Avoid: "How should users be notified?"
  2. Start broad, then narrow

    • First: What is the core purpose?
    • Then: Who are the users?
    • Finally: What constraints exist?
  3. Validate assumptions explicitly

    • "I'm assuming users will be logged in. Is that correct?"
  4. Ask about success criteria early

    • "How will you know this feature is working well?"

Read the full file on GitHub · 190 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 190 lines · 78 tokens per session scan A c1c0aa4513a8

Subscribe to this mod's changes

workflow-brainstorming is a skill published in the GitHub repository Kastalien-Research/thoughtbox (64 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 1,314 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.