Menu
Final go/no-go gate combining /verify (against SPEC) + /review (of the diff). Does NOT commit unless user explicitly authorizes. The last check before merge.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
| name | ship |
| description | Final go/no-go gate combining /verify (against SPEC) + /review (of the diff). Does NOT commit unless user explicitly authorizes. The last check before merge. |
The last gate before merge. Combines /verify (SPEC met?) + /review (diff quality?) into one go/no-go decision.
verdict: ship | hold | block
verify_result: verified | partial | failed
review_result: approve | request-changes | reject
blockers:
- <thing that must be fixed before ship>
recommendations:
- <thing that should be fixed but isn't blocking>
cmax ship --commit or follow-up confirmation.verify_result === failed → automatic block.review_result === reject → automatic block.verify === partial AND review === approve → hold (proceeds only on user confirm).