adr
Write an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as…
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.
$ npx -y skills add sd0xdev/sd0x-dev-flow --skill codex-brainstorm --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/codex-brainstormContext preview
The summary Claude sees to decide when to auto-load this skill.
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.
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
⚠️ Independent Research → Adversarial Debate → Nash Equilibrium ⚠️ Nash Equilibrium = Neither party can unilaterally change strategy to achieve a better outcome
| 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 |
**⚠️ 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}
${CONSTRAINTS}
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
1. Research summary (related modules, existing patterns) 2. Your position + supporting arguments 3. Potential risks
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?
| 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 |
| File | Purpose | | ---------------- | ------------------------------ | | `references/templates.md` | Claude/debate/report templates | | `references/techniques.md` | Attack/defense techniques | | `references/equilibrium.md` | Equilibrium determination flow |
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
Language: English | 繁體中文 | 简体中文 | 日本語 | 한국어 | Español The harness layer for Claude Code. Let the model choose the path. Keep "done" verifiable. Full control plane on Claude Code. Skills-only distribution for Codex CLI and other compatible agents.
Repo: sd0xdev/sd0x-dev-flow
Write an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as…
Architecture design and documentation. Produces 3-architecture.md with component diagrams, data flow, integration points, and architecture decisions. Reads…
Context-aware Q&A with auto context gathering. Use when: user has a quick question about codebase, git history, rules, docs, or skills during development. Not…
Industry best practices conformance audit with mandatory adversarial debate. Produces audit artifact: verdict (OK/WARN/FAIL) + gap roadmap + debate proof. Use…
Bug fix workflow. Use when: fixing bugs, resolving issues, regression fixes. Not for: new features (use feature-dev), understanding code (use code-explore).…
Bump package and plugin version in sync. Updates package.json, .claude-plugin/plugin.json, and install-state manifest to the same version. Use when: user says…