Skip to content
Back to skills

Codex Brainstorm

ASecurity

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.

  • 192 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 4, 2026
ai-agentsbashnodeexpressawscode-review

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned September 21, 2026

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

Installs into .claude/skills of the current project.

Are you the author of Codex Brainstorm?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Codex Brainstorm
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/sd0xdev-codex-brainstorm-sd0x-harness/badge)](https://www.skillsdirectory.com/skills/sd0xdev-codex-brainstorm-sd0x-harness)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
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
```

Files in this skill

  • SKILL.md4.2 KB
  • references/equilibrium.md3.4 KB
  • references/techniques.md4.3 KB
  • references/templates.md3.5 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.