Execute one bounded plan item or checklist slice with a worker, checks, review, and commit handoff. Use only when there is an explicit plan to work through in iterations.
Run an independent clean-context review for a refactor iteration, risky change, or pre-commit gate. Use when the user wants a skeptical second pass that sees only the iteration goal, diff, changed files, and test results, without implementation backstory.
Prepare a clean, scoped git commit from the current repo changes. Use when the user wants help analyzing what changed, grouping files into a coherent commit, generating a short commit message, and optionally performing the commit after approval.
Scan a codebase for deepening opportunities, present them as a report, then grill through whichever one the user picks.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.