Explicit ultra-compressed communication mode. Use only when the user invokes /caveman, says "caveman mode", "talk like caveman", or "use caveman". Keeps technical accuracy while dropping filler and pleasantries.
Plan implementation after a design or spec is approved. Use when the user asks to create or write an implementation plan, when grill/superGrill is ready to transition resolved decisions into code tasks, or when another skill needs TODO-ready, TDD-shaped, parallelizable task slices before implementation.
Grill a design, idea, or decision tree one question at a time. Use when the user wants a sharp stress-test, when a workflow needs clarifying questions with recommendations and self-critique, or when prior docs/_rules contracts should shape design decisions without writing new files.
Guardrails for careful coding work. Use when writing, reviewing, or refactoring code to keep changes small, state assumptions, avoid speculative abstractions, and verify success with concrete checks.
Manual-only post-session contract writer. Invoke only when the user explicitly names retro-man or asks to run retro-man; then record durable rules, contracts, and short specs into docs/_rules for future grill-design review.
Outsider review for a plan, PR, diff, design doc, or code change. Use on /scrutinize or when the user asks to review, audit, sanity-check, or get a second opinion; question whether the change should exist, trace real code paths, and report actionable findings with rationale.
Manual testing workflow controller — discovery → plan → browser execution → report.