dissect

Evidence-driven dissection of an existing service, written plan, or codebase area. Interrogates every entity (table, field, component, endpoint, module, boundary) against ground truth from multiple sources at once, red-teams each verdict devil's-advocate style, and arrives at the minimal-build optimization plan. Runs as a staged pipeline with human checkpoints and parallel read-only sub-agents so each investigation stays laser-focused. Use when the user invokes /dissect, or asks to audit / optimize / challenge / "tear apart" an existing system, schema, or plan. If the session is in Cursor or Claude Plan Mode, update the existing plan in place — never rewrite it.