Phase-gated bug investigation → root-cause → fix → verify cycle. Enforces root-cause-before-edit, failing-test-first, holistic callsite scan, reopen/redesign gates (SPEC-029), multi-surface done matrix, and self-calibration checklist before any "done" claim. Subcommands: /debug <desc> (full), /debug patch <desc> (fast path), /debug arch <desc> (design-first → /kickoff handoff).
Brutally honest review of staged/modified files — no sugar-coating. Thin wrapper over the council engine with preset `diff-mode`: 5 specialist investigators (logic, security, compliance, quality, simplification) run in parallel, filtered at confidence 80. Blocks commit on critical or compliance findings. Optional path argument saves the review to a file.
Fact-dense rewrite of agent memory prose (tier-0 notes, digests) without losing technical substance. Companion to /memory-distill. Zero external deps.
Adversarial council tribunal engine — reality-checks claims with material evidence. Shared engine for /council and /review-and-commit (diff-mode preset). Blind investigators, evidence-or-silence rule, dual output shapes (verdict[] and finding[]), atomic verdict index at .claude/council/index.json, feedback-memory learning loop. Judge is a dedicated agent with an empty tool allowlist. See specs/core/SPEC-013-adversarial-council-tribunal.md.
Optional host SAST (Semgrep / CodeQL) feed for security review. Fail-open when tools are missing. Agent-internal + review-and-commit / council security flavor. Zero required deps.
Socratic design refinement — structured questioning that forces requirement clarification before any planning or implementation. Use before /kickoff for complex features, or standalone for early-stage ideation. Optional --grill for one-question-at-a-time interviews with recommended answers.
Behavior-preserving polish on recently modified code — clarity only, no logic or API changes. Used by /orchestrate after Tech Lead approve, before QA. Zero external deps (in-plugin; not Anthropic's marketplace plugin).
Full lifecycle orchestrator — fetches issue context, creates worktree, spawns agents end-to-end, enforces tech-lead review loops, and optionally ships a PR. You stay as observer/navigator; agents do all the work. Usage: /orchestrate CDV-1 or /orchestrate