grilling

GitHub

通过追问压力测试用户计划或决策,构建设计树并分轮次探索,自动查找事实以厘清依赖,最终达成共同理解。

.pi/skills/grilling/SKILL.md wtfzambo/speak-like-you-eat

Trigger Scenarios

希望压力测试思维 使用 'grill' 相关触发词

Install

npx skills add wtfzambo/speak-like-you-eat --skill grilling -g -y
More Options

Non-standard path

npx skills add https://github.com/wtfzambo/speak-like-you-eat/tree/main/.pi/skills/grilling -g -y

Use without installing

npx skills use wtfzambo/speak-like-you-eat@grilling

指定 Agent (Claude Code)

npx skills add wtfzambo/speak-like-you-eat --skill grilling -a claude-code -g -y

安装 repo 全部 skill

npx skills add wtfzambo/speak-like-you-eat --all -g -y

预览 repo 内 skill

npx skills add wtfzambo/speak-like-you-eat --list

SKILL.md

Frontmatter
{
    "name": "grilling",
    "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.

Work the tree in rounds. The frontier is every decision whose prerequisites are already settled: the questions you can ask now without guessing at answers you haven't heard yet. Ask the whole frontier in one round: number each question and give your recommended answer. Then wait for the user's answers before the next round.

Each question should be formatted like so:

❓ **Q1** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>

➡️ <your recommended answer>

Each round the user answers reshapes the tree: settled decisions push the frontier outward and unblock questions that depended on them. Recompute the frontier and ask the next round. A question whose answer depends on another question still open in this round belongs to a later round, not this one.

Finding facts is your job, never the user's. When a frontier question needs a fact from the environment (filesystem, tools, etc.), dispatch a sub-agent to find it; don't ask the user for anything you could look up yourself. Don't block on it: a running exploration is an unsettled prerequisite, so only the questions downstream of it wait for the sub-agent to report; ask the rest of the frontier now. 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.

Version History

  • 60b69b0 Current 2026-08-27 09:10

Metadata

Files
0
Version
60b69b0
Hash
d2498125
Indexed
2026-08-27 09:10

inicio - Wiki
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-08-27 20:58
浙ICP备14020137号-1 $mapa de visitantes$