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-10
- Stars
- ★ 2
- Forks
- 1
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 资源文件 1
- 许可证LICENSE.txt1.0 KB
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>
Word each question so "yes" accepts 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
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
tdd
Test-driven development for ASP.NET Core and EF Core with xUnit. Use when building a feature or fixing a bug test-first, when the user mentions TDD or red-green-refactor, or when adding integration tests for endpoints or data access.
retro
Conduct a retrospective on a coding session.
pr
Use when writing a PR body.
postgresql
PostgreSQL gotchas and version-gated facts - indexing (B-tree, GIN, GiST, BRIN, partial, expression), JSONB, EXPLAIN ANALYZE and tuning, row-level security and multi-tenancy, full-text search, partitioning, connection pooling, extensions, logical replication, pgvector and RAG. Use when designing tables or indexes for PostgreSQL, writing or reviewing raw SQL, diagnosing a slow query, or choosing a PostgreSQL feature. For EF Core query performance use the optimizing-ef-core-queries skill; for migrations follow the ef-migrations rule.
improve-codebase-architecture
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.