Use when the user invokes /documentation or asks to update the RedDragon project docs. Updates README, ADRs, IR lowering gaps, VM/IR design docs, frontend design docs, and HTML presentations to reflect current codebase state.
Injects domain-type migration strategies during brainstorming and planning phases. Auto-triggers when the task involves replacing primitives (str, int) with domain types across a codebase, propagating wrapper types through dict keys and function signatures, or any large-scale type migration. Use this whenever you see keywords like "migrate", "domain type", "replace str with", "wrapper type", "propagate type", "rename across codebase", or when a brainstorming/planning session involves changing a field type on a widely-used class. Even if the user doesn't mention "migration" explicitly, trigger if the task is structurally a type propagation (e.g., "make field names typed", "add a CodeLabel wrapper").
Use when auditing test files for assertion-vs-name mismatches, verifying test assertions actually test what the test name claims, or running periodic test quality sweeps
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".