doublechecklisted

**Version**: 2.1 **Created**: 2026-03-13 **Last Updated**: 2026-03-17 **Authors:** Ömer Ufuk --- # /doublecheck — Critical Verification Pass **Usage**: `/doublecheck $ARGUMENTS` ## Current State - Recent changes: !`git diff HEAD --stat | tail -5` - Recent commits: !`git log --oneline -5` - Tool versions: !`grep 'var version' cmd/*/main.go 2>/dev/null` **Examples**: ``` /doublecheck # verify whatever was just implemented (tool inferred from context) /doublecheck morpheus # verify morpheus implementation /doublecheck oracle # verify oracle implementation /doublecheck trinity # verify trinity implementation /doublecheck neo # verify neo implementation /doublecheck plan oracle # attack a plan before implementation begins ``` --- ## What This Command Does Runs an adversarial verification pass on a tool implementation or plan in the Go monorepo. This is NOT a confirmation pass — it is a structured search for problems. Four subagents attack from different angles simultaneously. **This command is different from `/audit`.** - `/audit` asks: "Are the context files accurate against ground truth?" - `/doublecheck` asks: "Is the implementation itself complete, correct, and production-ready?" > **Critical**: "Looks good" and "seems correct" are forbidden. Every agent must produce specific findings or justify exactly why each check passed. Absence of findings is suspicious — look harder. --- ## The Mindset Assume at