Back

Grilling

Testing & QA1.1M installs

What it does

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.

Install

npx skills add https://github.com/mattpocock/skills --skill grilling

Website

www.skills.sh/mattpocock/skills/grilling

Details

From the skill’s SKILL.md or README, by its authors. View the original

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** - ****: 

➡️ 

---

❓ **Q2** - ****: 

➡️

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 with a fresh context window 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.

More Testing & QA skills

See all

  • Testing & QA

    TDD

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

    npx skills add https://github.com/mattpocock/skills --skill tdd
    1.2M installs

  • Testing & QA

    Diagnosing Bugs

    Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

    npx skills add https://github.com/mattpocock/skills --skill diagnosing-bugs
    907.2K installs

  • Testing & QA

    Setup Pre Commit

    Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

    npx skills add https://github.com/mattpocock/skills --skill setup-pre-commit
    535.4K installs

  • Testing & QA

    Migrate To Shoehorn

    Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.

    npx skills add https://github.com/mattpocock/skills --skill migrate-to-shoehorn
    521.6K installs

Skills are shared by members and not reviewed by us. Read a skill’s code before you install it.