Evidence-first codebase audit for correctness, security, privacy, data, integration, operational, test, and docs-vs-reality risks. Use when the user asks for a Fable-5 audit, exhaustive audit, bug hunt, risk review, codebase audit, security/integration audit, or asks Codex to find issues before changing code.
Fable-5 deep code review for pull requests, branches, diffs, or proposed patches. Use when the user asks for deep review, PR review, branch review, review comments, regression review, or independent verification of a change.
Evidence-grounded design option generation for technical architecture, migrations, APIs, data models, safety controls, operational changes, and implementation plans. Use when the user asks for options, tradeoffs, design review, migration strategy, or a decision memo grounded in the current codebase.
Claim-by-claim verification of docs, status reports, launch claims, changelogs, READMEs, runbooks, and "done/tested/working/live" assertions against source, tests, artifacts, and runtime evidence. Use when the user asks Codex to fact-check, verify claims, audit truthfulness, or compare docs to reality.
Repo-wide implementation workflow for renames, migrations, consistency updates, generated-surface sync, docs/tests updates, and cross-cutting cleanup. Use when the user asks for a Fable-5 sweep, broad rename, consistency pass, migration, or "find every place and update it" task.
Source-grounded codebase understanding for behavior, architecture, boot flow, data flow, integration wiring, or "how does this work" questions. Use when the user asks Codex to explain a system, trace a path, map a subsystem, or answer behavior questions with citations and unknowns.