grill-visuallisted

# Grill Visual Interview the user relentlessly about every aspect of this plan until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one by one. **For every question, provide your recommended answer.** If a question can be answered by exploring the codebase, explore the codebase instead of asking. The difference from terminal grilling: questions go to a local web page as rendered HTML, so a fork in the design can be *drawn* rather than described. The user invokes this once and then types nothing in the terminal — every answer arrives through the browser. **Static assets are on disk. Use them as-is.** `client.html`, `server.mjs`, and the class kit below are committed files in this skill directory. Never regenerate, template, inline, or re-emit them per session. The only per-session artifacts are the round files you write, `~/.claude/grill-visual/<session-id>/`, and the exported ledger. ## Delegate the bootstrap On first invocation, hand the setup to a subagent: start the server via `bin/push-round`, confirm the tab opened and the page rendered, debug anything that did not. Infrastructure noise does not belong in the interview context. Keep your own context on design content. ## The batching rule This replaces "one question at a time." Push **1–4 questions per round, typically 2–3, hard cap 4** (the pusher rejects a fifth). Admit a question into the round only if it passes the **independence test**: