Skill Claude CodeCodex
Use after a non-trivial, recurring, or expensive failure when a concise evidenced lesson could prevent future repeated investigation.
Skill Claude CodeCodex
Use after a non-trivial, recurring, or expensive failure when a concise evidenced lesson could prevent future repeated investigation.
Skill Claude CodeCodex
Use when status reports emphasize tools, files, commits, plans, tokens, or agents while requirements and evidence remain unchanged.
Skill Claude CodeCodex
Use when an agent-control framework needs adversarial testing for fake productivity, loops, recursion, evidence gaps, or vague wording.
Skill Claude CodeCodex
Use when the requested outcome is unclear, silently changing, being reinterpreted by discoveries, or disconnected from the active implementation.
Skill Claude CodeCodex
Use when work moves to another agent, session, person, or environment and the recipient needs enough state to continue without a sprawling narrative.
Skill Claude CodeCodex
Use when nested work is renamed, moved across agents, promoted to top level, or hidden behind research, validation, review, and dependency labels.
Skill Claude CodeCodex
Use when non-trivial implementation starts before what exists, what changes, why, risks, and validation are sufficiently known.
Skill Claude CodeCodex
Use when repository architecture, rules, skills, commands, context routing, manifests, or generated AI knowledge change and dependent sources may become stale.
Skill Claude CodeCodex
Use when activity is high but requirements, blockers, tests, and deliverables remain unchanged across repeated edit, search, test, review, or planning cycles.
Skill Claude CodeCodex
Use when commands, searches, file reads, edits, tests, critics, plans, context reloads, or strategies repeat without new evidence or acceptance progress.
Skill Claude CodeCodex
Use when rules appear satisfied while their intent is bypassed, counters reset, classifications change conveniently, or an AI-Psychiatry audit is requested.
Skill Claude CodeCodex
Use when deciding whether task discoveries, decisions, preferences, architecture, failures, or lessons deserve durable repository memory.
Skill Claude CodeCodex
Use when durable memory may contain assumptions, stale facts, contradictions, duplicates, obsolete decisions, or temporary debugging state.
Skill Claude CodeCodex
Use when two or more agents work concurrently, delegation may recurse, responsibilities overlap, dependencies can deadlock, or a coordinator must preserve scope and termination.
Skill Claude CodeCodex
Use when the user explicitly requests maximum autonomous execution, no unnecessary questions, persistent recovery, independent decision-making, and continuous work until the full Definition of Done is proven.
Skill Claude CodeCodex
Use when status is unclear, activity is high, completion estimates feel unreliable, or the agent may be mistaking reading, reasoning, tools, or churn for progress.
Skill Claude CodeCodex
Use when a task may be underthinking, sufficiently reasoned, or overthinking and the correct next action is unclear.
Skill Claude CodeCodex
Use when packages, services, ownership boundaries, entrypoints, tests, commands, or dependencies changed and the compact repository map needs a focused update.
Skill Claude CodeCodex
Use when continuing work from saved task state, a compacted session, a handoff, or a new agent without rereading the entire repository.
Skill Claude CodeCodex
Use when debugging changes assertions, mocks, exceptions, or symptoms without explaining materially important failure behavior.
Skill Claude CodeCodex
Use when system, user, repository, domain, AI-Psychiatry, skill, memory, or task-state instructions appear incompatible.
Skill Claude CodeCodex
Use when newly discovered work, technical debt, refactors, audits, optimizations, or reviewer suggestions threaten to expand the user-authorized task.
Skill Claude CodeCodex
Use when adjacent work is called required without dependency proof, or inconvenient required work is marked optional.
Skill Claude CodeCodex
Use when different commands, tools, runners, plans, or agents repeat the same hypothesis and evidence target.