From 63017f8e33a5637d0d76f6ed7fc826d9398b8140 Mon Sep 17 00:00:00 2001
From: alexion <contact@alexion.dev>
Date: Mon, 19 Oct 2026 02:32:34 -0400
Subject: [PATCH] feat(skills): add grill skill

---
 .pi/skills/grill          |  1 +
 src/skills/grill/SKILL.md | 41 +++++++++++++++++++++++++++++++++++++++
 2 files changed, 42 insertions(+)
 create mode 120000 .pi/skills/grill
 create mode 100644 src/skills/grill/SKILL.md

diff --git a/.pi/skills/grill b/.pi/skills/grill
new file mode 120000
index 0000000..2806aae
--- /dev/null
+++ b/.pi/skills/grill
@@ -0,0 +1 @@
+../../src/skills/grill
\ No newline at end of file
diff --git a/src/skills/grill/SKILL.md b/src/skills/grill/SKILL.md
new file mode 100644
index 0000000..fd57fa9
--- /dev/null
+++ b/src/skills/grill/SKILL.md
@@ -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.