Suede Codex Fleet

Suede Fable Fleet

The Suede Fable Fleet: a high-end Claude model is the admiral — it decomposes, briefs, and reviews — and parallel OpenAI Codex CLI workers are the fleet. The skill id and command stay suede-codex-fleet on purpose: GitHub search, skill marketplaces, and MCP catalogs match the terms people actually type — Codex CLI orchestration, codex exec, multi-agent worker fleet — not the brand name. Do not rename the folder or frontmatter name to match the brand.

When to use this skill instead of related skills

• suede-codex-fleet (this skill): offload high-volume, well-specified generation to Codex CLI workers; Claude plans, briefs, and reviews
• suede-agent-teams: multi-lane Claude agents coordinating one complex code change with gates and handoffs
• suede-copy / johnny-suede-write: Claude writes the copy itself; right choice when volume is low and judgment density is high

Core principle: Claude tokens buy judgment, Codex tokens buy volume. Clear spec + high volume goes to Codex. Fuzzy spec or expensive-if-wrong stays with Claude. Nothing ships unreviewed.

Preflight (run before first spawn)

1. which codex && codex --version — CLI present (validated against codex-cli 0.138.0).
2. codex login status — must show logged in (your ChatGPT subscription pays for the run).
3. Workspace has an AGENTS.md at its root. Codex auto-loads it; it carries voice, context, hard bans, and output conventions so briefs stay short. If missing, write it first — that is the highest-leverage file in the system.
4. Workspace has briefs/ and out/ directories (create as needed).

The loop

1. Decompose. Split the job into independent worker-sized tasks. Independent means: no worker needs another worker's output.
2. Brief. One markdown file per task in briefs/. Codex never sees the Claude conversation, so each brief is self-contained: job, inputs (file paths), exact deliverable, acceptance criteria it must self-check, and the exact output path in out/.
3. Spawn. One codex exec per brief, in parallel, in the background:

codex exec -C  --sandbox workspace-write --skip-git-repo-check \
  -o /out/-final-message.txt \
  "Read AGENTS.md at the workspace root, then execute the brief at briefs/.md exactly. Write the deliverable to the output file the brief names, run the brief's acceptance-criteria self-check, and state pass/fail per criterion in your final message."

• -C sets the worker's root; --skip-git-repo-check is required outside git repos.
• --sandbox workspace-write only. Never danger-full-access. Workers write files; they do not push, deploy, or touch secrets.
• Leave the model default unless explicitly asked to override with -m.

1. Review gate (Claude, mandatory). Read every out/ file. Check against the brief's acceptance criteria and the AGENTS.md hard bans. Worker self-checks are evidence, not verdicts. Fix small defects directly; do not respawn for a comma.
2. Delta, don't regenerate. For real misses, send a one-line correction: codex exec resume "" (session id is printed at run start; resume --last is ambiguous with parallel runs), or respawn with the delta appended to the brief. Regenerating from scratch wastes the subscription and loses what was right.
3. Ship. Claude assembles the reviewed survivors into the final deliverable. Report what was spawned, what passed, what got fixed.

Brief template

# Brief  — 

Read `AGENTS.md` in the workspace root first. This brief only adds the task.

## Job

## Inputs

## Deliverable

## Acceptance criteria (self-check before finishing)

## Output
Write to `out/.md`. 

Fleet workspaces

Keep a persistent workspace per recurring fleet job (a social-content fleet, a test-generation fleet, a refactor fleet) instead of rebuilding context every run. The workspace root holds the AGENTS.md contract, briefs/, and out/. When a brief produces output that passes review cleanly, keep it — proven briefs are the templates for the next run of the same shape.

Hard boundaries

• Never ship worker output without the Claude review gate.
• Workers never run git push, deploys, or credentialed commands; content and code-edit tasks only, inside the sandbox.
• Secrets never go into briefs or AGENTS.md; workers get file paths, not tokens.
• If a worker's output violates claim boundaries or hard bans, the fix is Claude's edit or a delta run, never "close enough".

Troubleshooting

• codex exec refuses to start outside a repo: add --skip-git-repo-check.
• Not logged in / usage errors: codex login status, then run codex login interactively.
• Worker wrote nothing to out/: read the -o final-message file and the task output log; usually a sandbox denial or a brief pointing at a wrong path.
• Parallel runs are independent processes; spawn each with its own background shell call and collect on completion.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: JasonColapietro
• Source: JasonColapietro/suede-creator-skills
• License: MIT
• Homepage: https://jasoncolapietro.github.io/suede-creator-skills/

Install and usage instructions live in the source repository linked above.