/gather-requirements — Decision-Grade Question interview

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.

Ask the questions one at a time.

If a question can be answered by exploring the codebase, explore the codebase instead.

This is the /grill-me engine, pointed at a stakeholder data ask. The <what-to-do> block above is the whole interview loop — run it as written. "The plan" is the ask you're interrogating; shared understanding is reached when you can write a Decision-Grade Question (DGQ) that survives the action-change kill-switch. Everything below tells you what the grill must resolve, the one place it must not recommend an answer, and what to write when understanding lands. It is an interview, not a template — a generic requirements form fills in blanks; this skill recommends killing the ask when the kill-switch trips.

Soul: the action-change kill-switch

The one branch this skill exists to force: