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

refactor(skills): simplify grill state

Browse Source
This commit is contained in:
alexion
2026-10-18 16:58:59 -04:00
parent 5f8a0c92aa
commit 85e820ed93
1 changed files with 10 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -5,28 +5,22 @@ description: Grill the user relentlessly about a plan, decision, or idea. Use wh
Interview the user relentlessly until you reach a shared understanding. Map this as a **design tree**: every decision branches into the decisions that hang off it. Interview the user relentlessly until you reach a shared understanding. Map this as a **design tree**: every decision branches into the decisions that hang off it.
Create a new tracked Markdown design record for each session. Infer its path and file name from the context. Report its path after creating it. Maintain the design tree in a new Markdown file. Infer its path and file name from context. Report its path after creating it. Use the file as the source of truth.
Work the tree one question at a time. The **frontier** is every decision whose prerequisites are already settled: the questions you can ask now without guessing at answers you have not heard yet. Work the tree one question at a time. The **frontier** is every decision whose prerequisites are already settled: the questions you can ask now without guessing at answers you have not heard yet. Record the next frontier question in the file, then ask it and wait for the user's answer.
Before asking a frontier question, record it and its options. Give each question as many options as it needs. Include the recommended answer as an option. Word each question so "yes" accepts that option. Format a question like so:
Record settled questions under **Decisions** with their question, options, and decision. Keep unanswered questions in **Frontier** and **Non-frontier**. Record a dependency only when it helps order questions.
Format each question like so:
``` ```
❓ **Q1** - **<question title>**: <question body> ❓ **Q1** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>
**Options** ➡️ <your recommended answer>
1. <option>
...
<n>. <recommended option>
``` ```
Each user answer reshapes the tree: move the answered question to **Decisions**, then recompute the frontier and non-frontier. A question whose answer depends on an open question belongs in the non-frontier. Word each question so "yes" accepts your recommended answer.
Finding _facts_ is your job, never the user's. When a question needs a fact from the environment, use available tools to find it. Do not ask the user for anything you can look up yourself. The _decisions_ are the user's: put each to them and wait. Each user answer reshapes the tree: settled decisions push the frontier outward and unblock questions that depended on them. Update the design tree in the file before asking the next question. A question whose answer depends on another open question belongs in the non-frontier, not the frontier.
The session is done when the frontier and non-frontier are empty: every branch of the design tree visited, nothing left silently assumed. Present the completed record. Do not act on it until the user confirms you have reached a shared understanding. Finding _facts_ is your job, never the user's. When a question needs a fact from the environment, 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.
The session is done when the frontier is empty: every branch of the design tree visited, nothing left silently assumed. Do not act on it until the user confirms you have reached a shared understanding.