Back to catalog
Human reviewedDesign

Skill dossier

brainstorming

Source declaration

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).

The author's original description, preserved in English. It describes intent, not verified performance.

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).

designscripts

Research summary

Human reviewed

Skill Atlas editorial baseline · editorial-0.1.0

A structured requirements conversation Skill. It pushes the agent to understand intent and constraints before implementation, using staged questions, options and a written design handoff.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Use before ambiguous creative or implementation work.
  • Separates design discussion from execution.
  • Produces a design document handoff.
  • Requires active user decisions.

Limitations & scope

  • Can slow down simple, well-specified tasks.
  • Quality still depends on asking useful questions and applying the answers.
  • No controlled success rate is claimed.

Relevant for

  • Product and engineering teams
  • Solo builders facing vague requests
  • Agents that tend to implement too early

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
3
scripts
4
references
2
Size
77.6 KB
Structural complexity
Moderate

File inventory

PathTypeBytes
skills/brainstorming/builder-check-prompt.mdReference881 B
skills/brainstorming/scripts/frame-template.htmlOther7.9 KB
skills/brainstorming/scripts/helper.jsScript5.5 KB
skills/brainstorming/scripts/server.cjsScript25.1 KB
skills/brainstorming/scripts/start-server.shScript7.1 KB
skills/brainstorming/scripts/stop-server.shScript3.2 KB
skills/brainstorming/SKILL.mdInstruction14.8 KB
skills/brainstorming/visual-companion.mdReference13.1 KB

SKILL.md frontmatter

{
  "name": "brainstorming",
  "description": "You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation)."
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Confirm scope

    Read the trigger conditions and decide whether this skill matches the current task.

  2. 02
    Action

    Load instructions

    Claude Code reads the full SKILL.md when the skill is selected.

  3. 03
    Decision

    Use resources deliberately

    Read references or run scripts only when the documented workflow requires them.

  4. 04
    Output

    Deliver and verify

    Produce the requested artifact and verify it against the source-described acceptance criteria.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

157 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Note

File modification is described or implemented

144 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 144 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

6 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 6 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

3 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 3 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Dynamic command execution is referenced

A shell, dynamic evaluation, or process execution primitive appears here. Inspect arguments and input control. Presence in source does not prove a command ran. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Inspect all security findings (157 findings)
High

File deletion is described or implemented

3 occurrences

Deletion syntax occurs in this line, including possible documentation. Review its exact target, recursive scope, and safeguards. The analyzer did not execute it. This rule matched 3 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

The Skill instructs conversation design; verify that referenced companion skills exist before relying on handoffs.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/obra/superpowers.git cd superpowers # Copy this skill directory into one of: # ~/.claude/skills/brainstorming # .claude/skills/brainstorming
  1. Open the immutable source at https://github.com/obra/superpowers/tree/22f0b463e7a5e579904dd6211a520321035526f7/skills/brainstorming/SKILL.md.
  2. Review the license, prerequisites and all bundled resources.
  3. Install the skill into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Check that SKILL.md is discoverable at the destination, then ask Claude Code to use the named skill on a test task.

Prerequisites

  • Can slow down simple, well-specified tasks.
  • Quality still depends on asking useful questions and applying the answers.
  • No controlled success rate is claimed.

Example prompts

Representative task

Use the brainstorming skill to help with this task. First summarize what the skill will do, then execute its documented workflow and show the source-linked evidence for each major decision.

Inspect before use

Read the brainstorming skill files at https://github.com/obra/superpowers/tree/22f0b463e7a5e579904dd6211a520321035526f7/skills/brainstorming/SKILL.md. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Forces intent discovery before building.
  • Clear gate between design and implementation.

Considerations

  • Can feel heavy for trivial changes.
  • Requires human participation.
Research conclusion

Useful as a guardrail against premature implementation; not a fast path for clear tasks.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

obrasuperpowersskills/brainstorming
Source type
Community
Commit
22f0b463e7a5e579904dd6211a520321035526f7
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
322,183
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.