Consult Fable (primary oracle) for expert second opinions; escalate to GPT-5.6 Sol (via Codex CLI) or GPT-5.5-Pro (via PAL) only for extremely important or complex tasks (always paired with Fable). Use for complex decisions, architecture choices, debugging…
Run 2x oracle sessions (FOR + AGAINST stances) to validate design decisions, plans, or bead readiness. Default = two Fable subagents; escalate to GPT-5.6 Sol via Codex CLI or PAL 2x GPT-Pro (always paired with Fable) for extremely important or complex…
Use the local Codex CLI as an independent second agent. Two branches — (1) proactively run `codex review` for a second opinion after completing a substantive change, before presenting it as done or committing; (2) delegate a well-defined implementation task…
Get a second opinion on an image by asking the OpenAI Codex CLI to look at it. Use when the user wants Codex (GPT) to analyze an image they (or you) just looked at, asks for "a second opinion on this image", says "have codex look at it", or wants cross-model…
When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back…
Review changed code for naming, stale references, unnecessary complexity, and comment quality. Use after completing implementation work, before committing, or when the user asks to review or audit code.
Run [implement-spec](../implement-spec/SKILL.md) with Codex doing the implementation passes while you orchestrate, integrate, and review. Use when the user asks to implement a spec with Codex, or to run implement-spec with Codex as the implementer.
Refactor cleanly instead of layering sediment. Use when a change reveals duplicated concepts, local adapters, obsolete owners, compatibility wrappers, parallel abstractions, an over-large module that has accreted many responsibilities, or "just tack this on"…