zetetic-team-subagents

16 commands across 6 categories. Commands are operational shortcuts that invoke tools, skills, and agents.

List all zetetic agents with their types, roles, and trigger conditions.

Spawn an agent as a standalone Claude Code session in an isolated git worktree.

Check status of running agent worktrees — active branches, last commit, uncommitted changes.

Load multiple genius agents in sequence, apply each to the problem, and pass output forward.

Frontier-model consultant for the Advisor loop — reviews plans at decision points and verifies completion while a cheaper model executes

Proactively analyze structural changes, decomposition decisions

Proactively review code changes for Clean Architecture, SOLID, size limits

Data scientist specializing in profile-first EDA, distribution-aware modeling, missingness classification

Database specialist adapting to any engine (PostgreSQL, MySQL, SQLite, MongoDB, etc.) — schema design

The question itself may be the bug. Use when a debate goes in circles, both options of a binary feel wrong, improving one parameter degrades another, "we're stuck" on a problem that resists direct attack, a metaphor is doing hidden work in the architecture, or a trade-off is being denied rather than made.

Draw the line where it costs least. Use for build-vs-buy calls, "where does this module/team/service boundary belong?", APIs and abstractions forcing users into implementation vocabulary, tools that should augment rather than automate, hardcoded decisions that belong at runtime, or information nobody can find.

Correlation walked in; make it prove causation. Use when someone claims "X causes Y" from observational data, asks "did the change actually cause the improvement?", "is this confounded?", "what would have happened if we hadn't shipped it?", plans an A/B test, or investigates why an incident/outbreak spread the way it did.

Audit the decision before it ships. Use for "are we sure about this?", high-stakes choices made on fast intuition, plans with no failure scenario, estimates that are suspiciously optimistic, metrics being gamed (Goodhart), unfalsifiable claims, negotiation prep, or strategies that break in extreme conditions.

Bound it before you build it. Use when a decision is blocked by "we don't have data", an estimate looks suspiciously precise, someone asks "is this even feasible?", "how much capacity do we need?", "will this scale?", or a claimed number has never been cross-checked by a second method.

19 hooks across 6 events