ihabkhaled/AI-Psychiatry

direct-communication

Use when answers, progress updates, explanations, or questions risk verbosity, repetition, indirect wording, vague conclusions, or conversational loops.

all-the-medicine

Use when the user explicitly requests the complete AI-Psychiatry framework through one all-in-one command that evaluates and orchestrates every available skill until the task is proven complete.

all-the-medicine

Use when the user explicitly requests the complete AI-Psychiatry framework through one all-in-one command that evaluates and orchestrates every available skill until the task is proven complete.

never-stop

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.

install-framework

Use when installing, upgrading, or auditing AI Psychiatry; adding attention, compulsive-checking, overthinking, underthinking, semantic anti-bypass, recursion, evidence, context, memory, or delivery controls to a repository.

never-stop

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.

anti-gaming

Use when commands, labels, agents, counters, or classifications change while the same underlying behavior continues.

blocker-validator

Use when BLOCKED is proposed after difficulty, uncertainty, unfamiliar code, a slow operation, or a small number of failed attempts.

completion-evidence

Use when DONE is proposed with unrun tests, missing requirements, inferred success, happy-path-only proof, or unresolved required findings.

context-balance

Use when context is overloaded or compression may have removed requirements, constraints, evidence, blockers, or decisions.

decision-readiness

Use when an important implementation, architecture, security, data, or delivery decision rests on unresolved critical unknowns.

evidence-floor

Use when mandatory behavior, integration, security, migration, or data requirements lack the appropriate kind of proof.

executive-override

Use when an AI-Psychiatry budget expires while new evidence shows a narrow extension is required for correctness, security, or completion.

false-progress-detector

Use when status reports emphasize tools, files, commits, plans, tokens, or agents while requirements and evidence remain unchanged.

framework-red-team

Use when an agent-control framework needs adversarial testing for fake productivity, loops, recursion, evidence gaps, or vague wording.

hidden-recursion-detector

Use when nested work is renamed, moved across agents, promoted to top level, or hidden behind research, validation, review, and dependency labels.

investigation-floor

Use when non-trivial implementation starts before what exists, what changes, why, risks, and validation are sufficiently known.

loophole-hunter

Use when rules appear satisfied while their intent is bypassed, counters reset, classifications change conveniently, or an AI-Psychiatry audit is requested.

memory-validator

Use when durable memory may contain assumptions, stale facts, contradictions, duplicates, obsolete decisions, or temporary debugging state.

reasoning-balance

Use when a task may be underthinking, sufficiently reasoned, or overthinking and the correct next action is unclear.

root-cause-validator

Use when debugging changes assertions, mocks, exceptions, or symptoms without explaining materially important failure behavior.

rule-conflict-resolver

Use when system, user, repository, domain, AI-Psychiatry, skill, memory, or task-state instructions appear incompatible.

scope-laundering-detector

Use when adjacent work is called required without dependency proof, or inconvenient required work is marked optional.

strategy-laundering-detector

Use when different commands, tools, runners, plans, or agents repeat the same hypothesis and evidence target.

underthinking-detector

Use when implementation, parking, blocking, strategy switching, or completion happens before critical understanding and evidence exist.

anti-gaming

Use when commands, labels, agents, counters, or classifications change while the same underlying behavior continues.

blocker-validator

Use when BLOCKED is proposed after difficulty, uncertainty, unfamiliar code, a slow operation, or a small number of failed attempts.

completion-evidence

Use when DONE is proposed with unrun tests, missing requirements, inferred success, happy-path-only proof, or unresolved required findings.

context-balance

Use when context is overloaded or compression may have removed requirements, constraints, evidence, blockers, or decisions.

decision-readiness

Use when an important implementation, architecture, security, data, or delivery decision rests on unresolved critical unknowns.

evidence-floor

Use when mandatory behavior, integration, security, migration, or data requirements lack the appropriate kind of proof.

executive-override

Use when an AI-Psychiatry budget expires while new evidence shows a narrow extension is required for correctness, security, or completion.

false-progress-detector

Use when status reports emphasize tools, files, commits, plans, tokens, or agents while requirements and evidence remain unchanged.

framework-red-team

Use when an agent-control framework needs adversarial testing for fake productivity, loops, recursion, evidence gaps, or vague wording.

hidden-recursion-detector

Use when nested work is renamed, moved across agents, promoted to top level, or hidden behind research, validation, review, and dependency labels.

investigation-floor

Use when non-trivial implementation starts before what exists, what changes, why, risks, and validation are sufficiently known.

loophole-hunter

Use when rules appear satisfied while their intent is bypassed, counters reset, classifications change conveniently, or an AI-Psychiatry audit is requested.

memory-validator

Use when durable memory may contain assumptions, stale facts, contradictions, duplicates, obsolete decisions, or temporary debugging state.

reasoning-balance

Use when a task may be underthinking, sufficiently reasoned, or overthinking and the correct next action is unclear.

root-cause-validator

Use when debugging changes assertions, mocks, exceptions, or symptoms without explaining materially important failure behavior.