duck

# Duck (auto-detect) Auto-detects which mode fits the user's current state and routes to the matching mode skill. Read [`../ducking/engine.md`](../ducking/engine.md) for shared persona, principles, and session-management rules — they apply to every mode. ## Mode Map | Trigger phrase / state | Mode skill | |------|------| | "build this for me" / stated implementation intent, no plan or code yet | `/duck-prebuild` | | Active plan in conversation (or `.claude/orientation.md`-adjacent design doc) | `/duck-prebuild` | | Files recently created/modified in this session | `/duck-verify` | | Uncommitted changes (`git diff --stat` non-empty) | `/duck-review` | | User new to the repo, returning after long break, "where should I even start" | `/duck-orient` | | None of the above | Ask the user which phase they want | ## Detection Order Check in this order — first match wins: 1. **Pre-coding intent** — user just stated they want to build X but no plan/diff/code exists yet → `/duck-prebuild` 2. **Plan in context** — a plan or design doc was produced in this session → `/duck-prebuild` 3. **Uncommitted changes** — `git diff --stat` shows a real diff → `/duck-review` 4. **Recent in-session edits** — files were created or modified earlier in this session but not yet committed → `/duck-verify` 5. **Orientation gap** — user appears unfamiliar with the repo → `/duck-orient` 6. **Ambiguous** — ask the user which phase they want before continuing ## Behavior When the User Picks Their Own Mod...