diff --git a/.changeset/grilling-question-format.md b/.changeset/grilling-question-format.md new file mode 100644 index 0000000..f3ca1f6 --- /dev/null +++ b/.changeset/grilling-question-format.md @@ -0,0 +1,5 @@ +--- +"mattpocock-skills": patch +--- + +Pin the question format in **`grilling`**. Every question in a round is now emitted in one fixed shape — `**Q1** - `, then the body (prose or multiple choices), then a `➡️ **Recommendation:**` line. A round reads as a scannable numbered list with each recommendation visually separated from the question, so you can answer by number instead of quoting questions back. diff --git a/docs/productivity/grilling.md b/docs/productivity/grilling.md index b6fd398..b5c54a3 100644 --- a/docs/productivity/grilling.md +++ b/docs/productivity/grilling.md @@ -14,7 +14,7 @@ npx skills update grilling `grilling` is the relentless interview that stress-tests a plan or design before you build it. It maps the plan as a **design tree** — every decision branches into the decisions that hang off it — and works that tree in **rounds** until you and the agent share the same understanding. -Each round asks the whole **frontier**: every decision whose prerequisites are already settled — the questions it can put to you *now* without guessing at answers it hasn't heard yet. Your answers reshape the tree, pushing the frontier outward, and the next round asks whatever that unblocks. Thirteen questions land in a handful of rounds instead of thirteen. Every question comes with the agent's own recommended answer; any *fact* the environment can settle it dispatches to a background sub-agent rather than asking you — and it doesn't block on that research, only the questions downstream of it wait. It won't act on the plan until you confirm the shared understanding has been reached. +Each round asks the whole **frontier**: every decision whose prerequisites are already settled — the questions it can put to you *now* without guessing at answers it hasn't heard yet. Your answers reshape the tree, pushing the frontier outward, and the next round asks whatever that unblocks. Thirteen questions land in a handful of rounds instead of thirteen. Every question arrives in a fixed shape — numbered and titled (`**Q1** - Storage backend`), then the body, then a `➡️ **Recommendation:**` line — so a round reads as a scannable list and you can answer it by number rather than by quoting it back; any *fact* the environment can settle it dispatches to a background sub-agent rather than asking you — and it doesn't block on that research, only the questions downstream of it wait. It won't act on the plan until you confirm the shared understanding has been reached. ### Prefer one question at a time? diff --git a/skills/productivity/grilling/SKILL.md b/skills/productivity/grilling/SKILL.md index a899055..078c660 100644 --- a/skills/productivity/grilling/SKILL.md +++ b/skills/productivity/grilling/SKILL.md @@ -7,6 +7,14 @@ Interview the user relentlessly until you reach a shared understanding. Map this Work the tree in **rounds**. The **frontier** is every decision whose prerequisites are already settled — the questions you can ask _now_ without guessing at answers you haven't heard yet. Ask the whole frontier in one round: number each question and give your recommended answer. Then wait for the user's answers before the next round. +Each question should be formatted like so: + +``` +**Q1** - <question title>: <question body, might be multiple paragraphs, including multiple choices> + +➡️ **Recommendation:** <your recommended answer> +``` + Each round the user answers reshapes the tree — settled decisions push the frontier outward and unblock questions that depended on them. Recompute the frontier and ask the next round. A question whose answer depends on another question still open in this round belongs to a _later_ round, not this one. Finding _facts_ is your job, never the user's. When a frontier question needs a fact from the environment (filesystem, tools, etc.), dispatch a sub-agent to find it — don't ask the user for anything you could look up yourself. Don't block on it: a running exploration is an unsettled prerequisite, so only the questions downstream of it wait for the sub-agent to report — ask the rest of the frontier now. The _decisions_ are the user's — put each to them and wait.