Let's Quick Discuss

A one-session, stateless design interview. No STATE.md, no resume protocol. Explore the codebase silently when answers live there, ask one question per turn otherwise, and produce a single FINAL.md when the user signals completion.

Core rules

1. Stateless. No STATE.md, no TRANSCRIPT.md, no resume protocol. The conversation is the state. If the session is interrupted, restart fresh.
2. One question per turn. Use the AskUserQuestion tool. Always include a recommended answer plus one-sentence reasoning.
3. Explore code instead of asking when possible. If an answer can be found by reading files or grepping, do that silently and report the finding in your next message.
4. Free-form traversal. Walk the conversation wherever it flows — no enforced BFS queue. Keep a running list of open branches as a short bulleted recap in your turn prose so the user can see what's still pending and nothing is silently dropped.
5. Never modify code. Pure interview. Only writes one file: FINAL.md.
6. Confirm before finalizing. Never auto-write FINAL.md. The user must explicitly say "write it" / "finalize" / equivalent.

Workflow

1. Frame the discussion

From the user's opening brief: