This skill should be used when the user asks to "collaborate with Codex", "use Codex for planning", "get Codex review", "delegate to Codex", "code review", "PR review", "review this code", "review this PR", "Codexใจๅ่ชฟ", "Codexใซใฌใใฅใผ", "Codexใซ่จ็ปใไฝๆใใใใ", "Codexใซไปปใใ", "Codexใซๅงไปป", "Codexใจ้ฃๆบ", "Codexใซ็ธ่ซ", "Codexใฎๆ่ฆ", "Claude plans", "Claude-led", "Claudeใ่จ็ป", "Claudeไธปๅฐ", "Codexใซๅฎ่ฃ ใใใ", "Codexใซๅฎ่ฃ ใไปปใใ", "Claudeใใฌใใฅใผ", "ใณใผใใฌใใฅใผใใฆ", "PRใใฌใใฅใผใใฆ", "ใณใผใใใฌใใฅใผใใฆ", "ใใฎใณใผใใใฌใใฅใผ", or mentions coordinating tasks between Claude Code and Codex CLI. NOTE: This is the default skill for generic code/PR review requests. Use devils-advocate only when the user explicitly asks for adversarial/red-team critique of a design or proposal.
This skill should be used when the user wants to "synthesize two competing solutions without averaging", "resolve a design/value disagreement by lifting to a higher frame", "ๆญขๆ / ใขใฆใใใผใใณ", "็็พใๆญขๆ", "็ฌ็ซๆกใ็ตฑๅ", "ๅนณๅๅใใ็ตฑๅ", "contradiction lift", "sublate competing designs", or has two good-but-divergent answers to the same question and wants a higher-order resolution (a selection mechanism) or an honest aporia โ not a compromise. NOTE: Use this when two independent solutions diverge and you want to PRESERVE both truth-moments while lifting to a higher frame. Use devils-advocate to stress-test ONE proposal with an assigned opponent, strong-inference to find an unknown cause, and dialectic-loop to validate a claim against a real corpus.
This skill should be used when the user wants to "test a claim against data", "validate an empirical hypothesis", "refine a model/theory with evidence", "characterize a pattern and verify it", "ๆผ็นนใจๅธฐ็ดใงๆค่จผ", "ไปฎ่ชฌใใใผใฟใงๆค่จผใใฆๆดๆฐ", "ๅฎไพใจๅไพใง็ขบใใใ", "ๅผ่จผๆณใซใผใ", "ไธปๅผตใ็พ็ฉใง่ฃๅใ", "ๅพๅๅๆใๆค่จผใใฆ็ฒพ็ทปๅ", or mentions iteratively updating a hypothesis by deriving predictions and testing them against a real corpus. NOTE: Use this for VALIDATING/REFINING an empirical claim or model against real data through a deriveโtestโupdate loop. Use strong-inference for debugging an UNKNOWN cause, and devils-advocate for adversarially stress-testing a DESIGN proposal.
Consult Claude Code from Codex for a second opinion while Codex remains responsible for implementation and verification. Use when the user asks Codex to collaborate with Claude, consult Claude, ask Claude for a plan, get a Claude review, delegate analysis to Claude, or says "Claudeใจไธ็ทใซ", "Claudeใซ็ธ่ซ", "Claudeใซใฌใใฅใผใใฆใใใ", "Claudeใฎๆ่ฆใ่ใ", or "Claudeใจ่จ็ปใ็ซใฆใ". Also use when an explicit independent planning or review pass from Claude would materially reduce risk on a complex coding task.
This skill should be used when the user wants to "plan with Codex", "create a plan", "draft implementation plan", "help me plan", "plan before implementing", "refine a plan", "review my plan idea", "Codexใจ่จ็ปใ็ซใฆใ", "ๅฎ่ฃ ่จ็ปใไฝๆ", "่จ็ปใ็ซใฆใใ", "่จ็ปใไธ็ทใซ่ใใฆ", "ๅฎ่ฃ ๆน้ใ็ธ่ซ", "Codexใจ่จญ่จใ็ทดใ", "่จ็ปใ ใไฝใใใ", "ๅฎ่ฃ ๅใซ่จ็ปใ็ซใฆใใ", "่จ็ปใใฌใใฅใผใใฆใปใใ", or mentions creating/refining an implementation plan as the deliverable without proceeding to implementation. NOTE: This is for PLAN-ONLY workflows that produce a plan document as the deliverable. Do NOT use when the user wants implementation (use codex-collab instead). Do NOT use for adversarial design critique (use devils-advocate instead). Do NOT use for debugging (use strong-inference instead).
This skill should be used when the user wants to "stress-test a design", "challenge an idea", "red team a proposal", "get critical feedback on a design", "validate a design", "adversarial architecture review", "risk assessment", "่จญ่จใๆค่จผใใฆ", "ๅ่ซใใใใใใ", "่จญ่จใๆนๅค็ใซใฌใใฅใผ", "ใใใซใบใขใใใฑใผใ", "ในใใฌในใในใ", "ๅผฑ็นใๆๆใใฆ", "็ฉดใ่ฆใคใใฆ", "ใใฎ่จญ่จใง่ฏใใ", "ใชในใฏ่ฉไพก", "่จญ่จใฎใขใผใญใใฏใใฃใฌใใฅใผ", or mentions structured adversarial review of a proposal or design. NOTE: Use this for validating PROPOSALS and DESIGNS through adversarial debate, NOT for generic code review, PR review, or normal review requests (use codex-collab for those). Also NOT for investigating unknown bugs (use strong-inference for that).
This skill should be used when the user wants to "investigate a bug", "debug an issue", "figure out why something is happening", "find the root cause", "troubleshoot", "ๅผทใๆจ่ซใง่ชฟๆป", "ไปฎ่ชฌใ็ซใฆใฆๆค่จผ", "ๅๅ ใ็นๅฎ", "ใใฐใฎๅๅ ่ชฟๆป", "ใชใๅใใชใใ่ชฟในใฆ", "ๅ้กใๅใๅใ", "ๅๅ ไธๆ", "ใใใใฐ", or mentions systematic hypothesis-driven debugging. NOTE: Use this for investigating UNKNOWN causes, not for validating design proposals (use devils-advocate for that).