Codex Issue Coordinator

Explains how an existing system works today. Use for architecture maps, audits, or ARCHITECTURE.md. Return a chat report unless the user ask...

Reviews a technical proposal before implementation. Use for designs, RFCs, ADRs, architecture proposals, and issues that define how a system...

Writes a clear design for a proposed feature or system change. Use when important product or technical choices must be settled before coding...

Generates a polished, static HTML reading view from an existing Markdown PRD or technical design. Use when a user asks to render, present, v...

Makes existing code easier to understand without changing behavior. Use to simplify structure, remove duplication or dead code, improve name...

Turns an approved design or decided brief into ordered tasks for separate agent runs. Use for implementation tasks, tracker tickets, or usef...

Uses a fresh agent to review an implementation change without editing it. Checks behavior, security, regressions, complexity, tests, docs, a...

Completes one or more tasks. Creates one tested and reviewed pull request for each task. Use to implement, build, fix, or deliver tasks, tic...

Proves that a code change meets its acceptance criteria. Uses focused automated checks and a real browser for browser-facing work. Use to te...

Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests,...

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold e...

Use when you need to resolve an in-progress git merge/rebase conflict.

A relentless interview that asks every frontier question at once, round by round.