alexion/dev
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(grill): track decisions consistently

Browse Source
This commit is contained in:
alexion
2026-10-20 18:12:41 -04:00
parent 159b1dfcf2
commit 23e24401f5
1 changed files with 10 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
src/skills/grill/SKILL.md
View File

@@ -3,20 +3,20 @@ name: grill
description: Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
---
Interview the user relentlessly until you reach a shared understanding. Map this as a **design tree**: each question branches into the questions it unblocks.
Interview the user relentlessly until you reach a shared understanding. Map this as a **design tree**: each decision branches into the decisions it unblocks.
Maintain the design tree in a new Markdown file. Use the file as the source of truth.
Build the complete **frontier** before the first question.
After each answer, recompute and display every frontier question.
After each answer, recompute and display every frontier decision.
Ask one frontier question per turn.
A clarification leaves that question open.
Ask one frontier decision per turn.
A clarification leaves that decision open.
Format a question like so:
```
❓ **Q1** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>
❓ **D1 — <decision title>**: <question body, might be multiple paragraphs, including multiple choices>
**Options**
@@ -26,7 +26,7 @@ Format a question like so:
---
❓ **Q2** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>
❓ **D2 — <decision title>**: <question body, might be multiple paragraphs, including multiple choices>
**Options**
@@ -38,7 +38,10 @@ Format a question like so:
List every viable answer in an ordered list and mark your recommended answer.
Word each question so "yes" accepts your recommended answer.
Each user answer reshapes the tree: settled decisions push the frontier outward and unblock questions that depended on them. Recompute the frontier in the file and ask the next question. A question whose answer depends on another open question belongs later, not next.
Before asking the next question, account for every decision that the response settles.
Record preferences as constraints.
Settle an implementation decision only after facts establish that it is viable.
A decision with unresolved prerequisites belongs outside the frontier.
Finding _facts_ is your job, never the user's. When a frontier question needs a fact from the environment (filesystem, tools, etc.), find it with available tools; don't ask the user for anything you could look up yourself. The _decisions_ are the user's: put each to them and wait.