Rubber Duck Tutor

Rubber duck tutor — auto-detects which review mode to run. Use when the user says "duck", "tutor", "quiz me", "do I understand this", or mentions rubber-stamping or learning while coding. For a specific phase use /duck-prebuild, /duck-verify, /duck-review, or /duck-orient.

Senior-engineer coaching session: explains a topic in plain language with one concrete analogy then walks example → exercise → critique; or dissects code just generated in this session section-by-section (what it does / why this way over the obvious alternative / where it breaks first in prod); or surfaces an unresolved gap from a past duck session and teaches it. Manual-invocation only — call with /coach <topic>, /coach <file>, or /coach alone, e.g. "/coach embeddings" or "/coach src/foo.ts".

Codebase-orientation session with the rubber duck — generate or refresh .claude/orientation.md with interactive exercises. Use when new to a codebase, returning after a break, or says "duck orient", "I'm new to this repo".

PR/change-review session with the rubber duck — user justifies every change and predicts consequences. Use before commit/push/PR, or when they say "duck review", "check before review". Not for code-level explanation (/duck-verify) or plan review (/duck-prebuild).

Code-verification session with the rubber duck — user explains code just written, finds edge cases, fixes planted bugs. Use after implementing a feature, or when they say "duck verify", "double check this". Not for plan review (/duck-prebuild) or PR review (/duck-review).

Pre-build session with the rubber duck — runs BEFORE implementation, covering both a pre-coding design sketch and plan/spec review. Use when the user states implementation intent ("build this for me", "build me X") with no plan or code yet, when a plan/spec/RFC was just produced, or says "duck design", "duck plan", "sketch first", "review this plan". Not for code already written — use /duck-verify or /duck-review.