From c379d168582c672bf453cc54d1438525db8758f1 Mon Sep 17 00:00:00 2001 From: Frank Date: Sun, 18 Oct 2026 19:25:44 -0700 Subject: [PATCH] fix(grilling): correct ask-tool acceptance semantics (Refs #20) The ask tool's recommended flag only labels option 0; the reply always names the selected options, so 'the user's single Enter accepts it' overclaimed a default-accept mechanic that does not exist. Stated truthfully: the label invites one-glance acceptance, the reply is self-documenting. --- agent/skills/grilling/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/agent/skills/grilling/SKILL.md b/agent/skills/grilling/SKILL.md index fb0a9a6..5b3122e 100644 --- a/agent/skills/grilling/SKILL.md +++ b/agent/skills/grilling/SKILL.md @@ -16,7 +16,7 @@ Work the tree in **rounds**: ask the whole frontier at once, then wait. A decisi Ask each closed decision - anything expressible as 2–5 options - through the `ask` tool: - **One artefact per question**, counted before sending. Name the artefact each question decides; two names means two questions. Shared plumbing (an endpoint, a service, a build step) still leaves two artefacts. -- Recommended answer first, marked `recommended: 0`: the user's single Enter accepts it. +- Recommended answer first, marked `recommended: 0`, which labels it "(Recommended)" for one-glance acceptance. Every reply names what was picked, so the record is unambiguous. - Options quote the user's goal. Their words, their stated goal, ground the wording; your todo text and table rows stay out of it. - Your own idea is welcome: it gets its own recommended question. Attach it to its own question, so it rides there on its merits. - `multi: true` for pick-many, `header` for the branch chip, `preview` when the decision needs code or config in front of the user.