buy-inlisted

# Buy-in — Reviewer Persuasion Doc (The Buy-In Doc) Implementation done, but **others' approval** remains an unknown. Know what reviewers will ask in advance — it becomes known. `/unknowns:quiz` (or `/quiz` for copied installs) validates **my understanding**; buy-in prepares **others' trust**. Origin: The Buy-In Doc — see skills/loop/references/talk-source.md. ## Procedure 1. From `$ARGUMENTS`, identify target work and audience (reviewers, team, decision-makers). No arguments → this session's implemented work, audience = reviewers. Inputs: the plan/spec, the prototype, and IMPLEMENTATION_NOTES.md. 2. **Demo first**: working result at top of doc — execution output, screenshot/GIF, interactive demo operable inside the doc if possible. Target read time: 90 seconds. 3. **Preempt objections**: anticipate ~5 questions/objections reviewers would raise, answer each with **evidence**, and give every answer a reference the reviewer can follow (spec §, IMPLEMENTATION_NOTES.md entry date, metric, test run, file:line). No unsupported rebuttals — no evidence, move it to limitations. 4. **Spec at a glance**: area / decision / ref table, one row per settled decision. 5. **Known limitations and unresolved unknowns**: if IMPLEMENTATION_NOTES.md exists, pull recorded deviations and unresolved risks here. Not hiding is the basis of trust. 6. **Sign-off list**: name people/teams needing to approve, with roles, and assign what each must check. 7. **Rollback plan**: one p