agentleFS
sd0xdevsd0xdev/sd0x-dev-flow/skills/codex-brainstorm/SKILL.md

codex-brainstorm

Skill192 starsChanged 36 days agoMITView on GitHub

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.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Only need code review (use /codex-review)

    line 17
  2. Distinctive:

    Before forming conclusions, you must first:

    line 59
  3. Very specific:

    Search related code: grep -rn "keyword" .

    line 61
  4. Distinctive:

    Read relevant files to confirm existing implementations

    line 62

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

PhaseActionOutput
1Claude independent research + analysis, forms Position AClaude's optimal hypothesis
2Codex independent research + analysis, forms Position BCodex's optimal hypothesis
3Multi-round adversarial debate, mutual attacksDebate exchange record
4Check equilibrium, no further improvements possibleEquilibrium or divergence
5Output final reportNash 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

ConditionDescriptionResult
Nash EquilibriumNeither side can raise new attacksOutput equilibrium
ConvergenceBoth positions convergeOutput consensus
Max rounds5 rounds reached with remaining divergenceOutput 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

FilePurpose
references/templates.mdClaude/debate/report templates
references/techniques.mdAttack/defense techniques
references/equilibrium.mdEquilibrium 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.