mattpocock/batch-grill-me
skills/in-progress/batch-grill-me/SKILL.md
A relentless interview that asks every frontier question at once, round by round.
$ install --global
skillsauthnpx skillsauth add mattpocock/skills batch-grill-meInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 21, 2026, 2:30 AM144.9s2 files scanned
SKILL.md
- name:
- batch-grill-me
- description:
- A relentless interview that asks every frontier question at once, round by round.
- disable-model-invocation:
- true
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.
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.
Related Skills
mattpocock/to-tickets
tools
VerifiedTrustedCommunity
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
180,917SKILL.mdUpdated Jul 9, 2026
mattpocock/to-questionnaire
testing
VerifiedTrustedCommunity
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
170,916SKILL.mdUpdated Jul 15, 2026
mattpocock/setup-ts-deep-modules
development
VerifiedTrustedCommunity
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
168,867SKILL.mdUpdated Jul 11, 2026
mattpocock/wayfinder
testing
VerifiedTrustedCommunity
Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
168,867SKILL.mdUpdated Jul 9, 2026