grill-me · Skill Details

Mechanism

When It Triggers · How It Works · What It Produces

Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.

Trigger: User-invoked when a "grilling" session is needed without codebase dependency. /ask-matt classifies it as a standalone skill off the main flow — "the same relentless interview as /grill-with-docs, but for when you have no codebase."
Mechanism: Directly delegates to the /grilling skill with no additional logic. /grilling defines the interview mechanism: one question at a time, wait for answer, look up facts independently, no action until shared understanding is confirmed. /grill-me wraps the constraint "no documentation output."
Output: A user-aligned, thoroughly validated plan or design. Pure conversation with no file changes.

Use Cases

Two Typical Use Cases

Scenario 01

Personal project plan validation

An indie developer has a rough idea for a new side project but isn't sure it's well thought out. Invoking `/grill-me`, the agent asks questions one at a time via /grilling: "Who's the target user?", "What's the minimum set of core features?", "What's the tech stack trade-off?", "How do you measure success?" Each question waits for an answer before continuing, covering all decision branches without producing any documentation.

Scenario 02

Facilitating a discussion without a codebase

A product team discusses a new feature on a whiteboard and needs a "devil's advocate" to challenge assumptions. Invoking `/grill-me`, the agent plays the role of a relentless questioner, challenging ambiguities one at a time: "You assume users will use this — what evidence?", "This plan depends on a third-party API — what's the fallback?", "If only 1% of users use this, is it still worth building?" The team emerges with a more thorough plan.

Skill Relationships

Which Skills I Use · Which Skills Use Me

Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.

Tier 1 · These Skills Use Me

ask-mattWorkflow

Tier 2 · Current Skill

grill-meWorkflow

Tier 3 · I Use These Skills

grillingWorkflow

Full Relationship Graph

Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.

Skill File

SKILL.md

Open in GitHub ↗

SKILL.mdLoading from GitHub…

Skill Composition

Open in GitHub ↗

SKILL.md50.0%
other50.0%

▸skills/grill-me/
▸grill-me
- ·SKILL.md
- ▸agents
  - ·openai.yaml

Per the Agent Skills spec, SKILL.md is the only required file. The colored bars classify the rest into the three spec-aligned optional directories (scripts / references / assets) and an 'other' bucket. The full directory tree is below.

Related in Skillset

You May Also Need These Skills

ask-matt

A router skill for the entire skillset: when the user can't remember which skill to use or which flow fits their situation, they invoke this to get a recommendation. It describes the main "idea → ship" flow (grill-with-docs → to-spec/to-tickets → implement), plus on-ramps (triage, diagnosing-bugs, wayfinder), codebase health (improve-codebase-architecture), vocabulary layers (domain-modeling, codebase-design), and standalone skills (grill-me, prototype, research, teach). Following its map leads users to the correct workflow entry point.

Workflow

code-review

A two-axis code review skill: reviews a diff (from a fixed point to HEAD) along both Standards (coding standards + Fowler smell baseline) and Spec (faithful implementation of the originating issue/PRD). Both axes run as parallel sub-agents to avoid context pollution. The report aggregates findings without merging conclusions, ensuring "passes standards but implements the wrong thing" and "implements the right thing but breaks conventions" are both surfaced independently.

Workflow

codebase-design

A shared vocabulary skill for deep module design: provides a precise set of design terms (Module, Interface, Depth, Seam, Adapter, Leverage, Locality) guiding agents and developers to design "deep modules" — a lot of behaviour behind a small interface. Includes design principles (the deletion test, the interface is the test surface) and testability guidelines. A reference skill consumed by other skills (e.g., improve-codebase-architecture, tdd) and invoked directly by engineers.

Style Guide

diagnosing-bugs

A disciplined diagnosis loop for hard bugs and performance regressions. The core idea is to first build a tight feedback loop — no hypothesis phase without one. Six phases: build feedback loop → reproduce + minimise → generate 3-5 falsifiable hypotheses → instrument by prediction → fix + regression test → cleanup + post-mortem. If the codebase architecture can't lock down the bug, it recommends handing off to the improve-codebase-architecture skill.

Workflow