refactor(skills): preserve grill source structure

This commit is contained in:
2026-10-18 16:49:49 -04:00
parent 157da4be83
commit 5f8a0c92aa

View File

@@ -3,71 +3,30 @@ 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. 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. 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.
Map each decision as a **design tree**.
Create a new tracked Markdown design record for every session. 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.
Infer its path and file name from the context.
Report the path after creating the record.
Use this record structure: 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.
```markdown 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.
# <topic>
## Decisions 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.
### Question 1: <question> Format each question like so:
```
❓ **Q1** - **<question title>**: <question body>
**Options** **Options**
1. <option> 1. <option>
... ...
<n>. <recommended option> <n>. <recommended option>
**Decision:** <chosen option>
## Frontier
### Question 2: <question>
**Options**
1. <option>
...
<n>. <recommended option>
## Non-frontier
### Question 3: <question>
**Options**
1. <option>
...
<n>. <recommended option>
**Blocked by:** <unresolved decision>
``` ```
The **frontier** contains questions whose prerequisites are settled. 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.
The **non-frontier** contains questions with unresolved prerequisites.
Record dependencies only when they help order questions.
Investigate environment facts with available tools before asking a dependent question. 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.
Ask the user only for decisions.
Ask one frontier question at a time. 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.
Write its question and options in the record before asking it.
List as many options as the decision needs.
Include the recommended answer as an explicit option.
Word the question so "yes" selects that option.
After each answer, move the question to **Decisions**.
Record the selected option.
Recompute the design tree.
Update the frontier and non-frontier before asking the next question.
The session ends when both question lists are empty.
Present the completed record.
Do not act until the user confirms the shared understanding.