### Prototype

**You own the design decision, not the code. The prototype is a throwaway instrument. The real build follows Feature.**

The one playbook where the Laziness Protocol's "smallest change" and the verification bar invert. The procedure lives in the **prototype** skill (`../../merged/prototype/SKILL.md`), which merges this playbook's method with Matt Pocock's logic and UI prototypes. Read it and follow it; don't work from memory of this playbook's older steps.

1. Load the **prototype** skill and scope the decision the prototype exists to make. No decision means no prototype. Route to Feature.
2. Build, verify and capture as the skill says: in scratch by default, inside the app only with the user's explicit scope, and kept, committed or published only with the user's authorization.
3. Hand the chosen direction to Feature (`playbooks/feature.md`) for the real build, which owns the shape decision.

**Reply:** as the skill's Reply section says: the variants explored, the evidence, tradeoffs, your recommendation, and the scratch path or in-app files. Say plainly that the prototype is throwaway.