AGENT SKILL

grilling

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.

License 许可
MIT
最近更新
2026-11-11
Stars
★ 0
Forks
0

01 前言 Front Matter

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.

02 资源文件 2

03 SKILL.md 正文

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.

Format a round like so:

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

➡️ <your recommended answer>

---

❓ **Q2** - **<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.

04 同仓库更多 Skills

parksangick-lgtm
parksangick-lgtm/-foodbell-site

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

★ 0
parksangick-lgtm
parksangick-lgtm/-foodbell-site

to-spec

Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed. 한국어 요청 예 — '명세서로 정리해줘', '지금까지 얘기한 거 스펙으로 만들어줘'.

★ 0
parksangick-lgtm
parksangick-lgtm/-foodbell-site

teach

Teach the user a new skill or concept, within this workspace. 한국어 요청 예 — "○○ 수업해줘", "여러 날에 걸쳐 가르쳐줘", "수업 만들어줘". 짧은 질문("○○ 가 뭐야?")에는 쓰지 않는다. 수업 파일이 사이트에 올라가므로 c:\galleypark 폴더에서는 쓰지 않는다.

★ 0
parksangick-lgtm
parksangick-lgtm/-foodbell-site

setup-matt-pocock-skills

Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills. 한국어 요청 예 — '맷 포콕 스킬 설정해줘', '맷 포콕 스킬 처음 설정'.

★ 0
parksangick-lgtm
parksangick-lgtm/-foodbell-site

redesign-existing-projects

Upgrades existing websites and apps to premium quality. Audits current design, identifies generic AI patterns, and applies high-end design standards without breaking functionality. Works with any CSS framework or vanilla CSS.

★ 0
parksangick-lgtm
parksangick-lgtm/-foodbell-site

improve-codebase-architecture

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick. 한국어 요청 예 — "코드 구조 점검해줘", "코드 구조 개선할 곳 찾아줘".

★ 0