메뉴
Drift detection. Re-runs /taste against current code and reports what changed between the recorded taste.vision and the repo's current state. Use periodically (monthly?) or after large refactors.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | deepretaste |
| description | Drift detection. Re-runs /taste against current code and reports what changed between the recorded taste.vision and the repo's current state. Use periodically (monthly?) or after large refactors. |
Same engine as /taste, but its job is to surface drift.
taste.md + taste.vision.drift_summary: <one paragraph>
drifted_principles:
- <principle> — was: <old>; now: <new>; cause: <evidence>
new_findings:
- <SOTA change that invalidates prior assumption>
recommendation: regenerate | patch | no-action
cmax taste drift — runs /deepretaste and prints the report. Does NOT auto-rewrite taste.md unless --apply is passed.
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.