napkinlisted

# napkin **He asks for a napkin and a coffee. He hands your plan back as four boxes and three arrows.** If it doesn't fit on a napkin, it's not a plan yet. Coding agents draw diagrams. napkin makes your agent *think in gated progression* like a senior who's seen every over-built roadmap and isn't impressed. A renderer turns words into boxes. napkin draws the **line** where the plan has no proof, and circles the **loop** that compounds. The diagram is the byproduct. The clarity is the point. ## When he wakes up Make a plan legible — not a technical UML/ERD/architecture render (use a dedicated diagram skill for those). Signals: "napkin this", "sketch this plan", "what are the phases", "gate this", "flywheel", "how does this compound", or a pasted wall of strategy. ## How it works: the model thinks, the script draws You (the model) do the **thinking** — extract the shape into a small spec. The bundled script does the **drawing** — deterministic, aligned, any format. That's why napkin is token-frugal: you never hand-emit Mermaid or SVG. 1. **Boxes** — 3–6 discrete phases, ordered by dependency (not topic). Each gets a short imperative name + one-line "what happens". 2. **The line (gate)** — on every transition, the *condition* that unlocks the next phase (a metric, event, or proof — never a date). **No condition in the input? Do not invent one** — set `"ungated": true`. That line exposes where the plan assumes success, and it's the single most valuable thing thi