Grilling
Run a relentless, structured interview that sharpens a plan, design, feature idea or piece of writing until every decision in it is made and written down. Questions come in short rounds, each with a recommended answer; the interviewer looks up facts in the code and docs itself and only asks the human for decisions. In a repository it also keeps the domain language in a GLOSSARY.md and records hard-to-reverse decisions as ADRs as they land. Draws on Socratic questioning (Paul & Elder), Evans's ubiquitous language, Klein's premortem, Example Mapping and Matt Pocock's grilling skills. Use when th
Install
/plugin marketplace add vnovakovits/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add vnovakovits/claude-skills --skill grillinggit clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/grilling ~/.claude/skills/grillingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Grilling Apply this skill when an idea needs sharpening before anyone builds it: a feature request, a design, a migration plan, an architecture choice, a document. The aim is a set of **decisions**, each made by the person who owns it, with the reasoning written down. The interviewer's job is to find every open question, settle the ones facts can settle, and put the rest to the human one round at a time. It has two modes: - **With docs** — in a repository. Terms go into `GLOSSARY.md` and hard-to-reverse decisions into ADRs as they are settled, so the thinking outlives the conversation. - **Stateless** — anywhere else, or when the user asks for no files. Same interview; the summary at the end is the only record. ## Core Philosophy **Facts are the interviewer's job; decisions are the human's.** Never ask something you can look up. Before each round, read the code, docs, tickets and data that bear on the open questions, and settle what they settle. Ask the human only for choices: priorities, trade-offs, scope, risk appetite, intent. **Every question carries a recommendation.** "Should we X or Y? I'd pick X because Z" is answerable in a word. A bare open question costs the human the thinking you were meant to do. **Rounds, not walls.** Three to five questions per round, most important first. A wall of twenty questions gets skimmed and half-answered.
Details
- Skill name
grilling- Repository
- vnovakovits/claude-skills
- Path
plugins/engineering-practices/skills/grilling/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Grilling skill do?
Run a relentless, structured interview that sharpens a plan, design, feature idea or piece of writing until every decision in it is made and written down. Questions come in short rounds, each with a recommended answer; the interviewer looks up facts in the code and docs itself and only asks the human for decisions. In a repository it also keeps the domain language in a GLOSSARY.md and records hard-to-reverse decisions as ADRs as they land. Draws on Socratic questioning (Paul & Elder), Evans's ubiquitous language, Klein's premortem, Example Mapping and Matt Pocock's grilling skills. Use when th
How do I install the Grilling skill?
Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Grilling popular?
It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.
Related skills
Accidental Cio
5vnovakovits/claude-skills
Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to
Agent Retro
5vnovakovits/claude-skills
Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee
API Design
5vnovakovits/claude-skills
Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.
Marketing Content Strategy
8Freddy-CHEN-ux/00_claude_skills
Content strategy and operations for marketing teams. Positioning, messaging hierarchy, content pillars, editorial calendars, trust-building content, brand architecture, and measurement. Use for content strategy, positioning definition, trust signals, sub-brand connection, or channel-specific briefs.
Google Master
8Freddy-CHEN-ux/00_claude_skills
Shared resource library for Google integration skills. DO NOT load directly - provides common references (setup, API docs, error handling, authentication) and scripts used by gmail, google-docs, google-sheets, google-calendar, and future Google skills.
QA Docs Coverage
8Freddy-CHEN-ux/00_claude_skills
Docs as QA: audit doc coverage and freshness, validate runbooks, and maintain documentation quality gates for APIs, services, events, and operational workflows.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.