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

fix(grill): limit frontier wording changes

Browse Source
This commit is contained in:
alexion
2026-10-20 16:59:28 -04:00
parent cf7d66de02
commit 228dcfd674
1 changed files with 22 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -7,21 +7,32 @@ Interview the user relentlessly until you reach a shared understanding. Map this
Maintain the design tree in a new Markdown file. Use the file as the source of truth.
Build the **frontier** before asking a question.
The frontier contains every unresolved decision whose prerequisites are settled.
Build the **frontier** before asking the first question.
The frontier contains every unresolved decision with settled prerequisites.
After each answer, update the design tree.
Display every frontier decision.
Mark the decision selected for this turn.
Mark the selected decision.
Ask one selected decision per turn.
A clarification keeps the selected decision open.
Answer the clarification, then ask the selected decision again.
Ask one selected decision each turn.
A clarification keeps that decision open.
Answer the clarification.
Then ask the decision again.
Format a question like so:
```
❓ **Q1** - **<question title>**: <question body>
❓ **Q1** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>
**Options**
1. <option>
...
<n>. **<recommended option>** — recommended
---
❓ **Q2** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>
**Options**
@@ -30,17 +41,11 @@ Format a question like so:
<n>. **<recommended option>** — recommended
```
List every viable answer in an ordered list.
Mark the recommended answer.
Write each question so that "yes" selects the recommended option.
List every viable answer in an ordered list and mark your recommended answer.
Word each question so "yes" accepts your recommended answer.
After each answer, settle the answered decision.
Add decisions that the answer reveals.
Move every newly ready decision into the frontier.
Keep decisions with unresolved prerequisites outside the frontier.
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.
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.
Finish when the frontier is empty.
Present every settled decision from the design tree.
Wait for user confirmation before acting on the decisions.
The session is done when the frontier is empty: every branch of the design tree visited, nothing left silently assumed. Present every settled decision from the design tree. Do not act on it until the user confirms you have reached a shared understanding.