A command that examines a feature specification through structured questions about limits, failures, scale, security, privacy, and user experience.

Use it to refine a spec and add decisions about boundary conditions, errors, performance, security, and user behavior.

It exposes unclear requirements and overlooked edge cases before implementation begins. This gives the written plan more detail to guide development.

How HelixDevelopment/code configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to HelixDevelopment/code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/HelixDevelopment/code/main/.specify/extensions/superspec/commands/brainstorm.md

Clone the repo

git clone --depth 1 https://github.com/HelixDevelopment/code

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/helixdevelopment/code/brainstorm/github.svg)](https://agentmods.dev/commands/helixdevelopment/code/brainstorm)

Your own site

<a href="https://agentmods.dev/commands/helixdevelopment/code/brainstorm"><img src="https://agentmods.dev/badge/commands/helixdevelopment/code/brainstorm/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/helixdevelopment/code/brainstorm"><img src="https://agentmods.dev/badge/commands/helixdevelopment/code/brainstorm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 456 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00456
Opus 5	$0.00000	$0.00228
Sonnet 5	$0.00000	$0.00091
Haiku 4.5	$0.00000	$0.00046

Measured 4d ago against content hash 173821b1aa68, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

brainstorm 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 4d 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.

.specify/extensions/superspec/commands/brainstorm.md · 50 lines

How it starts

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

speckit.superspec.brainstorm

Deep-dive edge cases and refine a spec document using brainstorming skills.

Usage

/speckit.superspec.brainstorm [spec-path] [focus-topic]

Example: /speckit.superspec.brainstorm specs/001-develop/spec.md "Discuss the Edge Cases in the requirements document and confirm how to resolve these scenarios."

Process

Read the target spec file
Read the constitution for project constraints
Superpowers detection: Check for brainstorming skill
- If found: Read the brainstorming SKILL.md and follow its questioning protocol, adapting all outputs to the target spec file
- If not found: Use the built-in 5-category questioning protocol:
  - Boundary conditions (min/max, empty states, edge-of-range)
  - Error scenarios (service down, malformed input, partial failures)
  - Scale & performance (load, concurrency, rate limits)
  - Security & privacy (injection, authorization, data exposure)
  - User experience (confusion points, accessibility, unintended usage)
Ask questions one at a time, preferring multiple choice format
After each answer, update the spec:
- New requirements → add to Functional Requirements
- Resolved questions → update Open Questions table
- New edge cases → add to Edge Cases section
When the user confirms the spec is ready, update the "Brainstorm Log" with a dated summary of insights discovered

Output

Updated spec file with refined edge cases, resolved open questions, and brainstorm log entries.

Iteration

This command can be run multiple times on the same spec. Each session appends to the brainstorm log and skips previously explored categories.

Superpowers Adaptation

When using the brainstorming skill, adapt its outputs:

Design documents → fold insights back into the existing spec.md
Output location → write to specs/NNN/spec.md (not docs/superpowers/)

See references/superpowers-bridge.md for full adaptation rules.

Read the full file on GitHub · 50 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.

4d ago First seen · 50 lines · 0 tokens per session scan A 173821b1aa68

Subscribe to this mod's changes

brainstorm is a command published in the GitHub repository HelixDevelopment/code (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 456 tokens. 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-09-04.

Planning Project management agent agentic-ai agents ai ai-agents cli

trellis-continue

Resume work on the current task — pick up at the right phase/step in .trellis/workflow.md.

tincopper/neeko · 0 tokens

trellis-finish-work

Wrap up the current session: archive the active task (and any other completed-but-unarchived tasks the user wants to clean up) and record the session journal. Code commits are NOT done here — those happen in workflow Phase 3.4 before you invoke this command.