Agent skill

Brainstorm

by catlog22 in catlog22/Claude-Code-Workflow

Unified brainstorming skill with dual-mode operation — auto mode (framework generation, parallel multi-role analysis, cross-role synthesis) and single role analysis.

MITAuto-check: notesAgent Workflows

Install Brainstorm

skills CLI
$ npx skills add catlog22/Claude-Code-Workflow --skill brainstorm -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install catlog22/Claude-Code-Workflow brainstorm --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/brainstorm .claude/skills/brainstorm && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
brainstorm
GitHub stars
2.1k
Token cost
~4.8k tokens
SKILL.md length
1,246 words
Files
8
Skills in repo
82
Repo updated
First seen
Licence
MIT

At a glance

Unified brainstorming skill with dual-mode operation — auto mode (framework generation, parallel multi-role analysis, cross-role synthesis) and single role analysis.

  • Tasks that involve Brainstorming
  • SKILL.md covers Architecture Overview, Key Design Principles, Auto Mode and Execution Flow, plus 11 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Brainstorm is an agent skill from catlog22/Claude-Code-Workflow. Unified brainstorming skill with dual-mode operation — auto mode (framework generation, parallel multi-role analysis, cross-role synthesis) and single role analysis. Triggers on "brainstorm", "头脑风暴".

Its SKILL.md is about 4.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files (for example `README.md`, `phases/01-mode-routing.md` and `phases/02-artifacts.md`).

It sits in Agent Workflows, covering Brainstorming. The repository describes itself as: JSON-driven multi-agent cadence-team development framework with intelligent CLI orchestration (Gemini/Qwen/Codex), context-first architecture, and automated workflow execution. The licence is MIT.

When your agent uses it

  • Tasks that involve Brainstorming

Example prompts

  • “brainstorm”
  • “/brainstorm”

Requirements

  • Pre-approved tools (allowed-tools): Skill(*), Agent(conceptual-planning-agent, context-search-agent), AskUserQuestion(*), TodoWrite(*), Read(*), Write(*), Edit(*), Glob(*), Bash(*)

What it can do on your machine

Read from SKILL.md and the folder at commit 07491b0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Skill(*)
    • Agent(conceptual-planning-agent
    • context-search-agent)
    • AskUserQuestion(*)
    • TodoWrite(*)
    • Read(*)
    • Write(*)
    • Edit(*)
    • Glob(*)
    • Bash(*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json, javascript and bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Brainstorm loads about 4.8k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 1,246 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~53
When it runs · the whole SKILL.md, loaded when a task matches
~4.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Skill(*), Agent(conceptual-planning-agent, context-search-agent), AskUserQuestion(*), TodoWrite(*), 

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from catlog22/Claude-Code-Workflow at commit 07491b0, republished under its MIT licence (© catlog22). 1,246 words, ~4,833 tokens.

Download SKILL.mdSave it as .claude/skills/brainstorm/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
brainstorm
description
Unified brainstorming skill with dual-mode operation — auto mode (framework generation, parallel multi-role analysis, cross-role synthesis) and single role analysis. Triggers on "brainstorm", "头脑风暴".
allowed-tools
Skill(*), Agent(conceptual-planning-agent, context-search-agent), AskUserQuestion(*), TodoWrite(*), Read(*), Write(*), Edit(*), Glob(*), Bash(*)

Brainstorm

Unified brainstorming skill combining interactive framework generation, multi-role parallel analysis, and cross-role synthesis into a single entry point with two operational modes.

Architecture Overview

┌─────────────────────────────────────────────────────────────┐
│                    /brainstorm                                │
│         Unified Entry Point + Interactive Routing             │
└───────────────────────┬─────────────────────────────────────┘
                        │
              ┌─────────┴─────────┐
              ↓                   ↓
    ┌─────────────────┐  ┌──────────────────┐
    │   Auto Mode     │  │ Single Role Mode │
    │  (自动模式)      │  │ (单角色分析模式)   │
    └────────┬────────┘  └────────┬─────────┘
             │                    │
    ┌────────┼────────┐          │
    ↓        ↓        ↓          ↓
 Phase 2  Phase 3  Phase 4    Phase 3
Artifacts  N×Role  Synthesis  1×Role
 (7步)    Analysis  (8步)    Analysis
           并行               (4步)

Data Flow:

Auto Mode:
  Phase 2 (artifacts) → guidance-specification.md + selected_roles[]
    → Phase 3 (N × role-analysis) → {role}/analysis*.md (immutable)
      → Phase 4 (synthesis) → feature-specs/ + feature-index.json + synthesis-changelog.md

Single Role Mode:
  Phase 3 (1 × role-analysis) → {role}/analysis*.md

Key Design Principles

  1. Dual-Mode Routing: Interactive mode selection via AskUserQuestion, with parameter-based auto-detection
  2. Progressive Phase Loading: Phase files loaded on-demand via Ref: markers, not all at once
  3. Task Attachment/Collapse: Sub-tasks attached during phase execution, collapsed after completion
  4. Session Continuity: All phases share session state via workflow-session.json
  5. Auto-Continue Execution: Phases chain automatically without user intervention between them
  6. SPEC.md Quality Alignment: Guidance specification and role analysis follow SPEC.md standards (Concepts & Terminology, Non-Goals, Data Model, State Machine, RFC 2119 constraints)
  7. Template-Driven Analysis: Role-specific templates (e.g., system-architect) ensure consistent, high-quality outputs
  8. Quality Gates: Automated validation of guidance specification and role analysis against quality standards

Auto Mode

When --yes or -y: Auto-select auto mode, skip interactive routing question, auto-select recommended roles, skip all clarification questions, use default answers.

Execution Flow

Phase 1: Mode Detection & Interactive Routing

Ref: phases/01-mode-routing.md

Parse arguments, detect mode from flags/parameters, or ask user via AskUserQuestion.

Mode Detection Rules:

  1. If --yes or -y flag present → Auto Mode (no question asked)
  2. If first arg matches a known role name → Single Role Mode (no question asked)
  3. If --session flag present without role name → Ask user
  4. Otherwise → Ask user via AskUserQuestion

Output: execution_mode ("auto" | "single-role"), parsed parameters


Auto Mode Execution (execution_mode = "auto")

Phase 1.5: Terminology & Boundary Definition

  • Extract 5-10 core domain terms from user input and Phase 1 context
  • Generate terminology table (term, definition, aliases, category)
  • Collect Non-Goals via AskUserQuestion (明确排除的范围)
  • Store to session.terminology and session.non_goals
Phase 2: Interactive Framework Generation

Ref: phases/02-artifacts.md

Seven-phase interactive workflow: Context collection → Topic analysis → Role selection → Role questions → Conflict resolution → Final check → Generate specification.

Input: topic description, --count N, --yes flag Output: guidance-specification.md (with Concepts & Terminology, Non-Goals, RFC 2119 constraints), workflow-session.json (selected_roles[], session_id)

TodoWrite: Attach 7 sub-tasks (Phase 0-5), execute sequentially, collapse on completion.

Phase 3: Parallel Role Analysis

Ref: phases/03-role-analysis.md

Execute role analysis for EACH selected role in parallel (excluding ui-designer, which runs sequentially in Phase 3.5).

Input: selected_roles[] from Phase 2, session_id, guidance-specification.md Output: {role}/analysis*.md for each role

Parallel Execution: Launch N role-analysis calls simultaneously (one message with multiple Skill invokes). Each role with --skip-questions flag. Note: ui-designer is excluded from this parallel batch — it runs in Phase 3.5 with access to all text-role analyses.

For ui-designer: append --style-skill {package} if provided.

Template-Driven Analysis:

  • Load role-specific template if exists (e.g., templates/role-templates/system-architect-template.md)
  • Inject template into agent prompt as required structure
  • For system-architect: MUST include Data Model, State Machine, Error Handling, Observability, Configuration Model, Boundary Scenarios

Quality Validation:

  • After analysis generation, invoke role-analysis-reviewer-agent to validate against template
  • Check MUST have sections (blocking), SHOULD have sections (warning), quality checks (RFC keywords, valid diagrams)
  • Output validation report with score and recommendations

TodoWrite: Attach N parallel sub-tasks, execute concurrently, collapse on completion.

Phase 3.5: UI Design Exploration

Ref: phases/03a-ui-design-exploration.md

Sequential phase after text-role analyses complete. Generates tangible UI artifacts (HTML prototypes, ASCII mockups, or API sketches) based on project type detection.

Input: all role analyses from Phase 3 (read-only), guidance-specification.md, style_skill (optional) Output: html-prototypes/ or ascii-mockups/ or api-sketches/ directory with feature-index.json

Skip Conditions: project type is library/service, no ui-designer in selected_roles, --yes mode without --ui-explore

Optional Review: If 2+ prototypes and not --yes, load Ref: ~/.ccw/workflows/brainstorm-visualize.md for multi-round interactive review with intelligent grouping.

TodoWrite: Attach single task with sub-tasks (Detection → Generate → Validate → Review → Feedback), collapse on completion.

Phase 4: Synthesis Integration

Ref: phases/04-synthesis.md

Six-phase synthesis: Discovery → File discovery → Cross-role analysis → User interaction → Spec generation (single agent, sequential) + Conditional review → Finalization. Role analysis files are read-only (never modified). Spec is the final synthesis artifact.

Input: session_id from Phase 2, all role analysis files from Phase 3 (read-only) Output: feature-specs/, feature-index.json, synthesis-changelog.md

TodoWrite: Attach synthesis sub-tasks, execute sequentially, collapse on completion.


Single Role Mode Execution (execution_mode = "single-role")
Phase 3: Single Role Analysis

Ref: phases/03-role-analysis.md

Execute role analysis for ONE specified role with optional interactive context gathering.

Input: role_name, --session, --update, --include-questions, --skip-questions, --style-skill Output: {role}/analysis*.md

TodoWrite: Attach 4 sub-tasks (Detection → Context → Agent → Validation), execute sequentially.


Phase Reference Documents (read on-demand when phase executes):

PhaseDocumentPurposeUsed By
1phases/01-mode-routing.mdParameter parsing, mode detection, interactive routingBoth modes
2phases/02-artifacts.mdInteractive framework generation (7 phases)Auto mode only
3phases/03-role-analysis.mdRole-specific analysis generationBoth modes
3.5phases/03a-ui-design-exploration.mdUI prototype generation and reviewAuto mode only
4phases/04-synthesis.mdCross-role synthesis and feature specsAuto mode only
Show full SKILL.md (506 more words)Show less

Core Rules

  1. Start with Mode Detection: First action is Phase 1 (parse args + detect mode)
  2. Interactive Routing: If mode cannot be determined from args, ASK user via AskUserQuestion
  3. No Preliminary Analysis: Do not analyze topic before Phase 2 - artifacts handles all analysis
  4. Parse Every Output: Extract selected_roles from workflow-session.json after Phase 2
  5. Auto-Continue via TodoList: Check TodoList status to execute next pending phase automatically
  6. Task Attachment Model: Skill and Task executes attach sub-tasks to current workflow
  7. ⚠️ CRITICAL: DO NOT STOP: Continuous multi-phase workflow in auto mode. After executing all attached tasks, immediately collapse them and execute next phase
  8. Parallel Execution: Auto mode Phase 3 attaches multiple agent tasks simultaneously for concurrent execution
  9. Single Role Independence: Single role mode operates independently without requiring artifacts or synthesis

Input Processing

Parameter Parsing
javascript
// Parse from user input (argument string)
const args = parseArguments(user_input);

// Flags
const auto_yes = args.includes('--yes') || args.includes('-y');
const count = extractFlag(args, '--count', 3);  // default 3, max 9
const session_id = extractFlag(args, '--session', null);
const update_mode = args.includes('--update');
const include_questions = args.includes('--include-questions');
const skip_questions = args.includes('--skip-questions');
const style_skill = extractFlag(args, '--style-skill', null);

// Role detection
const VALID_ROLES = [
  'data-architect', 'product-manager', 'product-owner', 'scrum-master',
  'subject-matter-expert', 'system-architect', 'test-strategist',
  'ui-designer', 'ux-expert'
];
const first_arg = args[0]; // first non-flag argument
const is_role = VALID_ROLES.includes(first_arg);

// Mode detection
if (auto_yes) {
  execution_mode = 'auto';
  topic = extractTopic(args);
} else if (is_role) {
  execution_mode = 'single-role';
  role_name = first_arg;
} else {
  execution_mode = null;  // Ask user
  topic = extractTopic(args);
}
Usage Examples
bash
# Auto mode - full pipeline
/brainstorm "Build real-time collaboration platform" --count 3
/brainstorm -y "GOAL: Build platform SCOPE: 100 users" --count 5
/brainstorm "Design payment system" --style-skill material-design

# Single role mode - individual analysis
/brainstorm system-architect --session WFS-xxx
/brainstorm ux-expert --include-questions
/brainstorm ui-designer --session WFS-xxx --update --style-skill material-design
/brainstorm product-manager --skip-questions

# Ambiguous - will ask interactively
/brainstorm --session WFS-xxx
/brainstorm

Data Flow

Phase 1 (Mode Routing):
  Input:  user arguments
  Output: execution_mode, parsed_params
          ↓
  ┌───────┴───────┐
  Auto            Single Role
  ↓               ↓
Phase 2:          Phase 3:
  Input:  topic, count, auto_yes
  Output: session_id ─────────────→ Input: role_name, session_id
          selected_roles[]                  skip/include questions
          guidance-specification.md         style_skill
          ↓                         Output: {role}/analysis*.md
Phase 3:
  Input:  selected_roles[], session_id
          guidance-specification.md
          style_skill (for ui-designer)
  Output: {role}/analysis*.md (N files, immutable after this point)
          ↓
Phase 3.5:
  Input:  all analysis*.md (read-only), guidance-specification.md, style_skill
  Output: html-prototypes/ OR ascii-mockups/ OR api-sketches/
          feature-index.json, review_decisions (optional)
          ↓
Phase 4:
  Input:  session_id, all analysis files (read-only)
  Output: feature-specs/F-{id}-{slug}.md
          feature-index.json
          synthesis-changelog.md

TodoWrite Pattern

Auto Mode Lifecycle
Initial → Phase 1 Mode Routing (completed)
       → Phase 2 Artifacts (in_progress)
           → 7 sub-tasks ATTACHED (Phase 0-5)
           → Execute sequentially
           → Sub-tasks COLLAPSED
       → Phase 3 Parallel Role Analysis (in_progress)
           → N role sub-tasks ATTACHED simultaneously (excluding ui-designer)
           → Execute concurrently
           → Sub-tasks COLLAPSED
       → Phase 3.5 UI Design Exploration (in_progress)
           → Sub-tasks: Detection → Generate → Validate → Review → Feedback
           → Execute sequentially
           → Sub-tasks COLLAPSED
       → Phase 4 Synthesis (in_progress)
           → 8 sub-tasks ATTACHED
           → Execute sequentially
           → Sub-tasks COLLAPSED
       → All completed
Single Role Mode Lifecycle
Initial → Phase 1 Mode Routing (completed)
       → Phase 3 Role Analysis (in_progress)
           → 4 sub-tasks ATTACHED (Detection → Context → Agent → Validation)
           → Execute sequentially
           → Sub-tasks COLLAPSED
       → Completed
Initial TodoWrite (Auto Mode)
json
[
  {"content": "Phase 1: Mode detection and parameter parsing", "status": "in_progress", "activeForm": "Detecting mode"},
  {"content": "Phase 2: Interactive Framework Generation", "status": "pending", "activeForm": "Generating framework"},
  {"content": "Phase 3: Parallel Role Analysis", "status": "pending", "activeForm": "Executing parallel analysis"},
  {"content": "Phase 3.5: UI Design Exploration", "status": "pending", "activeForm": "Generating UI prototypes"},
  {"content": "Phase 4: Synthesis Integration", "status": "pending", "activeForm": "Executing synthesis"}
]
Initial TodoWrite (Single Role Mode)
json
[
  {"content": "Phase 1: Mode detection and parameter parsing", "status": "in_progress", "activeForm": "Detecting mode"},
  {"content": "Phase 3: Single role analysis for {role_name}", "status": "pending", "activeForm": "Executing role analysis"}
]

Session Management

⚡ FIRST ACTION: Check .workflow/active/ for existing sessions

Multiple Sessions Support:

  • Different Claude instances can have different brainstorming sessions
  • If multiple sessions found, prompt user to select
  • If single session found, use it
  • If no session exists:
    • Auto mode: Create WFS-[topic-slug]
    • Single role mode: ERROR if no session (must run auto mode first)

Session Continuity: All phases share session state via workflow-session.json

Available Roles

Role IDTitleFocus Area
data-architect数据架构师Data models, storage strategies, data flow
product-manager产品经理Product strategy, roadmap, prioritization
product-owner产品负责人Backlog management, user stories, acceptance criteria
scrum-master敏捷教练Process facilitation, impediment removal
subject-matter-expert领域专家Domain knowledge, business rules, compliance
system-architect系统架构师Technical architecture, scalability, integration
test-strategist测试策略师Test strategy, quality assurance
ui-designerUI设计师Visual design, mockups, design systems
ux-expertUX专家User research, information architecture, journey

Role Selection: Auto mode → handled by artifacts (Phase 2). Single role mode → user specifies directly.

Output Structure

.workflow/active/WFS-{topic}/
├── workflow-session.json              # Session metadata ONLY
├── .process/
│   └── context-package.json           # Phase 0 output (auto mode)
└── .brainstorming/
    ├── guidance-specification.md      # Framework (Phase 2, auto mode)
    ├── feature-index.json             # Feature index (Phase 4, auto mode, feature_mode)
    ├── synthesis-changelog.md         # Synthesis decisions audit trail (Phase 4, auto mode)
    ├── feature-specs/                 # Feature specs (Phase 4, auto mode, feature_mode)
    │   ├── F-001-{slug}.md
    │   └── F-00N-{slug}.md
    ├── specs/
    │   └── terminology-template.json  # Terminology schema
    ├── templates/
    │   └── role-templates/
    │       └── system-architect-template.md  # System architect analysis template
    ├── agents/
    │   └── role-analysis-reviewer-agent.md   # Role analysis validation agent
    ├── html-prototypes/               # Phase 3.5 (web/mobile/desktop-gui)
    │   ├── README.md                  # Prototype summary
    │   ├── feature-index.json         # File-to-feature mapping
    │   └── {feature-slug}.html        # Self-contained prototypes
    ├── ascii-mockups/                 # Phase 3.5 (cli projects)
    │   └── {feature-slug}.md
    ├── api-sketches/                  # Phase 3.5 (library/service projects)
    │   └── {feature-slug}.md
    ├── {role}/                        # Role analyses (IMMUTABLE after Phase 3)
    │   ├── {role}-context.md          # Interactive Q&A responses
    │   ├── analysis.md                # Main/index document
    │   ├── analysis-cross-cutting.md  # Cross-feature (feature_mode)
    │   └── analysis-F-{id}-{slug}.md  # Per-feature (feature_mode)
    └── synthesis-specification.md     # Integration (Phase 4, non-feature_mode only)

Error Handling

ErrorRecoveryMode
Invalid role nameShow valid roles list, ask againSingle Role
No active sessionAuto mode: create new. Single role: error with guidanceBoth
Role selection failureDefault to product-managerAuto
Agent execution failureAgent-specific retry with minimal dependenciesBoth
Template loading issuesGraceful degradationBoth
Synthesis conflictsHighlight disagreements without forced resolutionAuto
Context overflow (>100KB)Read only analysis.md index filesAuto

Context Overflow Protection:

  • Per-role limits: < 3000 words main, < 2000 words sub-docs, max 5 sub-docs
  • Synthesis protection: If total > 100KB, read only analysis.md (not sub-documents)
  • Recovery: reduce scope (--count 2) → use --summary-only → manual synthesis

Coordinator Checklist

Pre-Phase Actions:

  • Read Phase document via Ref: marker
  • Verify prerequisites (session exists, required files present)
  • Mark phase as in_progress in TodoWrite
  • Attach sub-tasks if applicable

Post-Phase Actions:

  • Validate phase outputs exist
  • Collapse sub-tasks to phase summary
  • Mark phase as completed in TodoWrite
  • Auto-continue to next pending phase (auto mode)
  • Report completion (single role mode)

Prerequisites:

  • /workflow:session:start - Start a new workflow session (optional, brainstorm creates its own)

Follow-ups (after brainstorm completes):

  • /workflow-plan --session {sessionId} - Generate implementation plan
  • /workflow:brainstorm:synthesis --session {sessionId} - Run synthesis standalone (if skipped)

Reference Information

Template Source: ~/.ccw/workflows/cli-templates/planning-roles/ Style SKILL Packages: .claude/skills/style-{package-name}/

© catlog22, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files in .claude/skills/brainstorm of catlog22/Claude-Code-Workflow.

  • SKILL.md
  • README.md
  • phases/01-mode-routing.md
  • phases/02-artifacts.md
  • phases/03-role-analysis.md
  • phases/03a-ui-design-exploration.md
  • phases/04-synthesis.md
  • specs/terminology-template.json

Open the folder on GitHubat commit 07491b0

Compare with similar skills

Brainstorm next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Brainstorm compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Brainstorm this skillcatlog22/Claude-Code-Workflow2.1k—~4.8kAutomated safety check: NotesMIT
Brainstormingxpinjection/test-driven-spring-boot11254 repos~2.6kAutomated safety check: PassMIT
LLM Councilgcpdev/llm-council-skill4611 repos~1kAutomated safety check: NotesMIT
Typesafe AIOpenAgentsInc/openagents4559 repos~2.5kAutomated safety check: PassMIT
Yao Meta Skillyaojingang/yao-meta-skill2.7k—~768Automated safety check: PassMIT
Trellis StartROYIANS/foliq-print-template-designer1356 repos~646Automated safety check: PassMIT

Similar skills

  • Brainstorming

    xpinjection/test-driven-spring-boot

    You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.

    112 GitHub starsUsed in 54 repos~2.6k tokens
    Agent WorkflowsAuto-check passed
  • LLM Council

    gcpdev/llm-council-skill

    Multi-LLM collaborative brainstorming and planning. An agent skill from gcpdev/llm-council-skill.

    461 GitHub starsUsed in 1 repo~1k tokens
    Agent WorkflowsAuto-check: notes
  • Typesafe AI

    OpenAgentsInc/openagents

    Build AI-powered software with TypeSafe: small units of AI intelligence you can use like programming primitives.

    455 GitHub starsUsed in 9 repos~2.5k tokens
    Agent WorkflowsAuto-check passed
  • Yao Meta Skill

    yaojingang/yao-meta-skill

    Create, improve, or evaluate an existing skill from workflows, prompts, SOPs, scripts.

    2.7k GitHub stars~768 tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • Trellis Start

    ROYIANS/foliq-print-template-designer

    Initializes an AI development session by reading workflow guides, developer identity, git status, active tasks, and project guidelines from .trellis/.

    135 GitHub starsUsed in 6 repos~646 tokens
    Agent WorkflowsAuto-check passed
  • Brainstorming Before Building

    jnMetaCode/superpowers-zh

    Turns a rough idea into an approved design before any code is written, sorting the request into spike, bounded or architectural and enforcing an approval gate.

    8.3k GitHub stars~1.8k tokensUpdated 3 days ago
    Agent WorkflowsAuto-check passed

More from catlog22/Claude-Code-Workflow

All 82 skills in this repo
  • Prompt Generator

    catlog22/Claude-Code-Workflow

    Generate or convert Claude Code prompt files — command orchestrators, skill files, agent role definitions, or style conversion of existing files.

    2.1k GitHub starsUsed in 1 repo~4.7k tokens
    Auto-check: notes
  • Ccw Help

    catlog22/Claude-Code-Workflow

    CCW command help system. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub stars~2.5k tokensUpdated 3 mo ago
    Auto-check passed
  • Team Ultra Analyze

    catlog22/Claude-Code-Workflow

    Deep collaborative analysis team skill. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub starsUsed in 1 repo~2.4k tokens
    Auto-check: notes
  • Ccw Chain

    catlog22/Claude-Code-Workflow

    Chain-based CCW workflow orchestrator. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub stars~1.1k tokensUpdated 3 mo ago
    Auto-check: notes
  • Delegation Check

    catlog22/Claude-Code-Workflow

    Check workflow delegation prompts against agent role definitions for content separation violations.

    2.1k GitHub stars~2.8k tokensUpdated 3 mo ago
    Auto-check: notes
  • Investigate

    catlog22/Claude-Code-Workflow

    Systematic debugging with Iron Law methodology. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub stars~1.1k tokensUpdated 3 mo ago
    Auto-check: notes

Categories

Questions about Brainstorm

What does Brainstorm do?

Unified brainstorming skill with dual-mode operation — auto mode (framework generation, parallel multi-role analysis, cross-role synthesis) and single role analysis. Brainstorm is an agent skill from catlog22/Claude-Code-Workflow. Unified brainstorming skill with dual-mode operation — auto mode (framework generation, parallel multi-role analysis, cross-role synthesis) and single role analysis.

When should I use Brainstorm?

Brainstorm fits situations like: tasks that involve Brainstorming.

How do I install Brainstorm in Claude Code?

Run `npx skills add catlog22/Claude-Code-Workflow --skill brainstorm -a claude-code`. Or copy the skill folder (.claude/skills/brainstorm in catlog22/Claude-Code-Workflow) into .claude/skills/brainstorm in your project. Claude Code loads it when a task matches its description.

How do I install Brainstorm in Codex?

Run `npx skills add catlog22/Claude-Code-Workflow --skill brainstorm -a codex`. Or copy the skill folder (.claude/skills/brainstorm in catlog22/Claude-Code-Workflow) into .agents/skills/brainstorm in your project. Codex loads it when a task matches its description.

Can I use Brainstorm in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add catlog22/Claude-Code-Workflow --skill brainstorm -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/brainstorm, .gemini/skills/brainstorm, .github/skills/brainstorm and .opencode/skills/brainstorm in your project.

What does Brainstorm need to run?

SKILL.md names no scripts, command-line tools or credentials: Brainstorm is instructions for the agent only. Its frontmatter pre-approves these tools: Skill(*), Agent(conceptual-planning-agent, context-search-agent), AskUserQuestion(*), TodoWrite(*), Read(*), Write(*), Edit(*), Glob(*), Bash(*).

Does Brainstorm access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Brainstorm safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Brainstorm use?

Brainstorm is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Brainstorm use?

About 4.8k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Brainstorm?

Skills that share tags, products or a category with Brainstorm: Brainstorming (xpinjection/test-driven-spring-boot, 112 stars), LLM Council (gcpdev/llm-council-skill, 461 stars), Typesafe AI (OpenAgentsInc/openagents, 455 stars) and Yao Meta Skill (yaojingang/yao-meta-skill, 2.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Brainstorm?

catlog22 (a GitHub user) maintains it in catlog22/Claude-Code-Workflow, which has 2,130 GitHub stars. The repository holds 82 skills in this directory. The repository was last updated on June 18, 2026.

Source: catlog22/Claude-Code-Workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.