codex-councillisted

# Codex Council You (Claude) orchestrate one or more `codex exec` agents toward the user's goal. Each role gets a task-specific lens, the same shared context, and its own persisted Codex thread per project and session. A runner script fans the roles out with bounded parallelism, writes each role's reply to disk as soon as it settles, and aggregates everything into one markdown report. You reconcile the replies into one outcome for the user. The skill is general-purpose with a programmatic center of gravity: project implementation, computer science, software and ML/AI engineering, DevSecOps, debugging and testing, and technical research. There is no built-in role catalog; roles come from the work in front of you. Detail lives in three references, one level deep: - [panel-design.md](references/panel-design.md) — sizing examples, writing instructions, model and effort choice, writers and follow-up rounds. - [context-staging.md](references/context-staging.md) — what goes into `context.md`, and fail-closed shell recipes for extracting it from disk. - [runtime-behavior.md](references/runtime-behavior.md) — following a run, reply files, recovery triage, retries, the watchdog, and continuity. ## Disambiguation when the requested agent workflow is unclear Treat the direct slash invocation or a clear use of "codex council," "codex coterie," or "codex team" as Codex Council intent and go to Step 1. Missing those exact names is only an ambiguity signal, never an automatic sto