القائمة
Multi-source root-cause analysis for a specific bug or failure. Depth-first on one symptom. Use when something is broken and you need the actual cause, not a workaround.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | investigate |
| description | Multi-source root-cause analysis for a specific bug or failure. Depth-first on one symptom. Use when something is broken and you need the actual cause, not a workaround. |
Depth-first on one symptom. The investigator's job is to find the actual cause, not patch the symptom.
/audit — breadth-first across many holes. Investigate is depth-first on one./debug-hard task class — the router escalates debug-hard to Opus automatically; /investigate is the user-invokable skill.Ask. Achieve. The canonical user-facing entry to claudemax — describe your goal, the SOTA-2026 pipeline (deepresearch → multispec → parallel /goal → verify) handles the rest. Same engine as /cmax with a friendlier verb. CLI equivalent is `cmax ask "<goal>"`.
The default FAT umbrella. Auto-runs deepresearch + multispec decomposition + parallel /goal + verify. Opus for planning/judgment/verification; Sonnet for sub-Spec execution (escalates per router). Multispec engine selects Mode A (SDK subagents) or Mode B (Claude Code Agent Teams) automatically based on work size. Your default daily-driver.
Max-effectiveness umbrella. Opus for EVERYTHING — planning, decomposition, sub-Spec /goal execution, verification. Use for novel domains, security/auth/payments, or when you want the highest ceiling regardless of cost.
Show the model-routing decision for a task (Fable/Opus/Sonnet/Haiku) with reasoning. Use before launching a packet to sanity-check the tier and to override when you have stronger judgment than the heuristic.
Reviews a proposed diff for correctness, security, style, taste alignment. Distinct from /audit (which reviews existing code, not diffs) and /verify (which checks SPEC completion).
Spec quality gate. Every completion condition must have a mechanically-checkable verifyHint (file path, command, test name, behavior). Blocks /goal handoff if the spec wouldn't be verifiable.