Use when answers, progress updates, explanations, or questions risk verbosity, repetition, indirect wording, vague conclusions, or conversational loops.
原文の言語: 英語
メニュー
SkillsMP は ihabkhaled/AI-Psychiatry から 79 件の skill を収集しています。skill を開くとソースと詳細を確認できます。
収集済み skill 79 件中 40 件を表示しています。
Use when answers, progress updates, explanations, or questions risk verbosity, repetition, indirect wording, vague conclusions, or conversational loops.
原文の言語: 英語
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.
原文の言語: 英語
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.
原文の言語: 英語
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.
原文の言語: 英語
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.
原文の言語: 英語
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.
原文の言語: 英語
Use when commands, labels, agents, counters, or classifications change while the same underlying behavior continues.
原文の言語: 英語
Use when BLOCKED is proposed after difficulty, uncertainty, unfamiliar code, a slow operation, or a small number of failed attempts.
原文の言語: 英語
Use when DONE is proposed with unrun tests, missing requirements, inferred success, happy-path-only proof, or unresolved required findings.
原文の言語: 英語
Use when context is overloaded or compression may have removed requirements, constraints, evidence, blockers, or decisions.
原文の言語: 英語
Use when an important implementation, architecture, security, data, or delivery decision rests on unresolved critical unknowns.
原文の言語: 英語
Use when mandatory behavior, integration, security, migration, or data requirements lack the appropriate kind of proof.
原文の言語: 英語
Use when an AI-Psychiatry budget expires while new evidence shows a narrow extension is required for correctness, security, or completion.
原文の言語: 英語
Use when status reports emphasize tools, files, commits, plans, tokens, or agents while requirements and evidence remain unchanged.
原文の言語: 英語
Use when an agent-control framework needs adversarial testing for fake productivity, loops, recursion, evidence gaps, or vague wording.
原文の言語: 英語
Use when nested work is renamed, moved across agents, promoted to top level, or hidden behind research, validation, review, and dependency labels.
原文の言語: 英語
Use when non-trivial implementation starts before what exists, what changes, why, risks, and validation are sufficiently known.
原文の言語: 英語
Use when rules appear satisfied while their intent is bypassed, counters reset, classifications change conveniently, or an AI-Psychiatry audit is requested.
原文の言語: 英語
Use when durable memory may contain assumptions, stale facts, contradictions, duplicates, obsolete decisions, or temporary debugging state.
原文の言語: 英語
Use when a task may be underthinking, sufficiently reasoned, or overthinking and the correct next action is unclear.
原文の言語: 英語
Use when debugging changes assertions, mocks, exceptions, or symptoms without explaining materially important failure behavior.
原文の言語: 英語
Use when system, user, repository, domain, AI-Psychiatry, skill, memory, or task-state instructions appear incompatible.
原文の言語: 英語
Use when adjacent work is called required without dependency proof, or inconvenient required work is marked optional.
原文の言語: 英語
Use when different commands, tools, runners, plans, or agents repeat the same hypothesis and evidence target.
原文の言語: 英語
Use when implementation, parking, blocking, strategy switching, or completion happens before critical understanding and evidence exist.
原文の言語: 英語
Use when commands, labels, agents, counters, or classifications change while the same underlying behavior continues.
原文の言語: 英語
Use when BLOCKED is proposed after difficulty, uncertainty, unfamiliar code, a slow operation, or a small number of failed attempts.
原文の言語: 英語
Use when DONE is proposed with unrun tests, missing requirements, inferred success, happy-path-only proof, or unresolved required findings.
原文の言語: 英語
Use when context is overloaded or compression may have removed requirements, constraints, evidence, blockers, or decisions.
原文の言語: 英語
Use when an important implementation, architecture, security, data, or delivery decision rests on unresolved critical unknowns.
原文の言語: 英語
Use when mandatory behavior, integration, security, migration, or data requirements lack the appropriate kind of proof.
原文の言語: 英語
Use when an AI-Psychiatry budget expires while new evidence shows a narrow extension is required for correctness, security, or completion.
原文の言語: 英語
Use when status reports emphasize tools, files, commits, plans, tokens, or agents while requirements and evidence remain unchanged.
原文の言語: 英語
Use when an agent-control framework needs adversarial testing for fake productivity, loops, recursion, evidence gaps, or vague wording.
原文の言語: 英語
Use when nested work is renamed, moved across agents, promoted to top level, or hidden behind research, validation, review, and dependency labels.
原文の言語: 英語
Use when non-trivial implementation starts before what exists, what changes, why, risks, and validation are sufficiently known.
原文の言語: 英語
Use when rules appear satisfied while their intent is bypassed, counters reset, classifications change conveniently, or an AI-Psychiatry audit is requested.
原文の言語: 英語
Use when durable memory may contain assumptions, stale facts, contradictions, duplicates, obsolete decisions, or temporary debugging state.
原文の言語: 英語
Use when a task may be underthinking, sufficiently reasoned, or overthinking and the correct next action is unclear.
原文の言語: 英語
Use when debugging changes assertions, mocks, exceptions, or symptoms without explaining materially important failure behavior.
原文の言語: 英語