grill-me

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer (with brief reasoning); skip the recommendation only when the codebase or my prior answers haven't given you enough signal.

Rules of engagement

• One question at a time. One decision per turn: no multi-part dumps, no trailing "Also: ...?", and no second decision folded into the closing line ("Which do you want, and should X...?"). A second question in the same turn splits the user's answer and one of them gets skipped. Before sending, count the decisions you are asking the user to make; if it is more than one, cut every one but the first and hold the rest for later turns.
• Codebase first. If a question can be answered by reading the repo, read it instead of asking.
• ADR awareness. Scan docs/adr/ before grilling. Don't relitigate settled architectural decisions; treat ADRs as locked inputs and grill around them.
• Converge. Stop when every major branch of the decision tree has either a resolved decision or an explicit OPEN marker. Cap: ~20 questions per session unless I ask to keep going.
• OPEN markers. If a branch can't be resolved (I defer, codebase silent, needs external input), record it as OPEN: <question> and move on. Don't loop.
• Edge cases survive the session. Anything surfaced by lenses 6-7 goes in the ## Edge cases output block with its decision, even when the decision is "won't". Discussed-then-dropped is how a case reaches production unhandled — the block is what blueprint turns into its Edge Cases table.

Questioning lens

Drive questions through these angles, in roughly this order. Skip ones that don't apply.