Skip to content
Development
Skill

/codex-brainstorm

Adversarial brainstorming via Claude+Codex debate. Use when: exploring solutions, feasibility analysis, exhaustive enumeration. Not for: implementation (use feature-dev), architecture only (use codex-architect). Output: Nash equilibrium consensus + action items.

From plugin
sd0x-dev-flow
195102 skills16 agents5 hooks

Claude Code

$ npx -y skills add sd0xdev/sd0x-harness --skill codex-brainstorm --agent claude-code

SKILL.md

codex-brainstorm.SKILL.md
name: codex-brainstorm
description: "Adversarial brainstorming via Claude+Codex debate. Use when: exploring solutions, feasibility analysis, exhaustive enumeration. Not for: implementation (use feature-dev), architecture only (use codex-architect). Output: Nash equilibrium consensus + action items."
allowed-tools: Read, Grep, Glob, Bash(ls:*), Bash(find:*), Bash(node:*), Write

Codex Brainstorm Skill

Trigger

  • Keywords: brainstorm, exhaust possibilities, explore solutions, deep discussion, feasibility analysis, solution exploration, Nash equilibrium

When NOT to Use

  • Simple technical Q&A (answer directly)
  • Already have a clear solution (implement directly)
  • Only need code review (use `/codex-review`)

Core Principle

⚠️ Independent Research → Adversarial Debate → Nash Equilibrium ⚠️

Nash Equilibrium = Neither party can unilaterally change strategy to achieve a better outcome

Workflow

| Phase | Action | Output | | ----- | ------------------------------------------------------- | --------------------------- | | 1 | **Claude independent research** + analysis, forms Position A | Claude's optimal hypothesis | | 2 | **Codex independent research** + analysis, forms Position B | Codex's optimal hypothesis | | 3 | Multi-round adversarial debate, mutual attacks | Debate exchange record | | 4 | Check equilibrium, no further improvements possible | Equilibrium or divergence | | 5 | Output final report | Nash Equilibrium report |

Phase 2: Codex Independent Research (Critical)

**⚠️ Must let Codex research independently; do NOT feed Claude's analysis results ⚠️**

Dispatch this body per `@skills/codex-code-review/references/codex-transport.md` § Start — a **fresh** thread for Phase 2. The transport pins the sandbox and the approval policy, so nothing is chosen here. **Save the returned `threadId`**; the Phase 3 debate rounds continue that same thread per its § Resume (`references/techniques.md`). Bind every placeholder before writing `prompt.md` — nothing evaluates an expression in a body-only template.

You are a senior architect. Conduct an **independent analysis** of the following topic.

Topic

${TOPIC}

Constraints

${CONSTRAINTS}

⚠️ Important: You must research independently ⚠️

Before forming conclusions, you **must** first: 1. Discover the directory structure: `ls` at the repository root, then list the directories it actually shows — do not assume a `src/` or `test/unit/` layout; many repositories, this one included, have neither 2. Search related code: `grep -rn "keyword" . -l | head -10` — rooted at the repository, or at a directory the discovery step above actually surfaced; never at an assumed `src/` 3. Read relevant files to confirm existing implementations

Output Requirements

1. Research summary (related modules, existing patterns) 2. Your position + supporting arguments 3. Potential risks

Phase 3: Adversarial Debate

Structure per round:

1. Claude attacks flaws in Codex's proposal 2. Codex rebuts or updates position 3. Equilibrium check: Can either side raise new attacks?

Termination Conditions

| Condition | Description | Result | | ----------------- | ---------------------------------------- | ------------------- | | Nash Equilibrium | Neither side can raise new attacks | Output equilibrium | | Convergence | Both positions converge | Output consensus | | Max rounds | 5 rounds reached with remaining divergence | Output divergence report |

Verification

  • [ ] Claude formed an independent position (not following Codex)
  • [ ] Codex performed code research (not speculating)
  • [ ] At least 3 rounds of adversarial debate
  • [ ] Each round has clear attack/defense records
  • [ ] Final report indicates equilibrium status

References

| File | Purpose | | ---------------- | ------------------------------ | | `references/templates.md` | Claude/debate/report templates | | `references/techniques.md` | Attack/defense techniques | | `references/equilibrium.md` | Equilibrium determination flow |

Example

Input: What implementation approaches are available for this requirement?

Phase 1: Claude independent research → Position A (Solution X is optimal)
Phase 2: Codex independent research → Position B (Solution Y is optimal)
Phase 3: Adversarial debate
  - R1: Claude attacks Y's scalability / Codex attacks X's complexity
  - R2: Claude rebuts / Codex concedes and updates position
  - R3: Both converge to Solution Z, no further attacks → Equilibrium
Phase 4: Output Nash Equilibrium = Solution Z
Read more
@sd0xdev
Ships withsd0x-dev-flow

Language: English | 繁體中文 | 简体中文 | 日本語 | 한국어 | Español The harness layer for Claude Code. Let the model choose the path. Keep "done" verifiable. Claude has discretion inside a closed, test-pinned anchor set.

195102 skills16 agents
Get the whole plugin

Stars on GitHub

Momentum

stars in total
195
Star history of sd0xdev/sd0x-dev-flow on GitHub, a chart by star-history.com

Other skills on sd0x-dev-flow.

adr

adr

Write an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as…

agentctl-setup

agentctl-setup

Install and set up the optional agentctl mod (task scope, refusal before execution, evidence that goes stale, model-free…

architecture

architecture

Architecture design and documentation. Produces 3-architecture.md with component diagrams, data flow, integration points, and…

ask

ask

Context-aware Q&A with auto context gathering. Use when: user has a quick question about codebase, git history, rules, docs, or…

best-practices

best-practices

Industry best practices conformance audit with mandatory adversarial debate. Produces audit artifact: verdict (OK/WARN/FAIL) +…

bug-fix

bug-fix

Bug fix workflow. Use when: fixing bugs, resolving issues, regression fixes. Not for: new features (use feature-dev),…

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

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

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills2w309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc2w293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react5d252k
@facebook@facebookInstall Skill

Questions about codex-brainstorm.

Which coding agents can use codex-brainstorm?
codex-brainstorm installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.