Individual skill

grill-me

Interview the user relentlessly about a plan or design until every branch of the decision tree has an explicit recorded decision and no open questions remain. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

skills/grill-me/SKILL.md

Read pinned source

Source commit d9d87d04cd9b932469c488a1de79b3260e7435c8

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 104
Repository last updated: Nov 9, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
ai-agents Repository topic
design Derived category
testing Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 3,336 bytes
agents/openai.yamlasset · 42 bytes

Read excerpt


# Grill Me

This skill is coordination-exempt: skip the ai-coord gate for its declared work.

Stress-test the plan in question rounds until every material branch is resolved and the user confirms shared
understanding. User instructions take precedence over this skill.

## Workflow

1. Extract the current objective, constraints, assumptions, and already-made decisions. Map the design tree: each
   decision branches into dependent decisions. Investigate facts discoverable from the codebase, environment, or
   supplied evidence instead of asking the user. Put decisions to the user and wait for their answers.
2. Maintain a running decision record with: decision, chosen option, rationale, dependencies, and consequences. Update
   it after every answer. Reopen a recorded decision only when new evidence conflicts with it or the user corrects it.