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

Add grill skill #194

Merged
alexion merged 1 commits from feat/grill-skill into main 2026-10-19 02:33:15 -04:00
Conversation 0 Commits 1 Files Changed 2 +42
2 changed files with 42 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 63017f8e33 - Show all commits

1
.pi/skills/grill Symbolic link
View File

@@ -0,0 +1 @@
../../src/skills/grill

41
src/skills/grill/SKILL.md Normal file
View File

@@ -0,0 +1,41 @@
---
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**: every decision branches into the decisions that hang off it.
Maintain the design tree in a new Markdown file. 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. Record the next frontier question in the file, then ask it and wait for the user's answer.
Format a question like so:
```
❓ **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**
1. <option>
...
<n>. **<recommended option>** — recommended
```
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.
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.
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.