duck-verify

# Duck — Code Verification Mode **Read first**: [../duck/references/core.md](../duck/references/core.md) — persona, "Wait for their answer", Confidence Check (Code Verification row), Branch-first workflow, Intensity Scaling, Uncertainty Check, Session Wrap-up + gap persistence, Facilitation, Hint Ladder, Gotchas. They apply here. **Input**: Recently changed files — use `git diff` or conversation context. ## Flow 1. **Identify critical changes** — focus on: - New files or modules - Complex logic (conditionals, loops, error handling) - Integration points (API calls, DB queries, external services) - Edge cases that could fail silently 2. **Start with a teach-back**: > **Your turn:** What does [specific component] do? Explain it like I'm a new developer joining the project. 3. **Probe based on their answer**: - Good explanation → "OK, what happens when [edge case input] comes in?" - Vague → "Be more specific — what does [function] do with [input], step by step?" - Can't explain → "That's fine. Open [file:line_number] and find [function name]. Read it and tell me what you see." 4. **Present a bug scenario** (real or plausible): > **Your turn:** Here's a scenario: [specific edge case or failure]. What happens? 5. If they find it → discuss the fix approach. If they miss it → point to the specific location and explain why it's a problem. → Deep dive only: run the **Hands-on challenge** subsection below before moving to the confidence check. 6. **...