Frank
08f90c6df3
Retroactive provenance: the 10 pi-era skill snapshots were byte-identical to upstream. Canonical installs now live in ~/.agents/skills tracked by ~/.agents/.skill-lock.json (mattpocock/skills x38 after grilling removal, find-skills from vercel-labs/skills). Repo tier is authored overrides only: clear all 10 tracked upstream snapshots; omp loads the store directly through the agents provider (skills.enableAgentsUser, default on). grilling returns as a real directory — extracted from the store (CLI + lockfile pruned) so Frank can customize it without skills update resurrecting a twin. Docs: skill-store-wiring.md (+index). Pre-cutover snapshot of the old tracked dirs at /tmp/agent-skills-snap-20261018.
2.4 KiB
name, description
| name | description |
|---|---|
| grilling | 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. |
Authored override. Extracted 2026-10-18 from
mattpocock/skills(identical to upstream at extraction) into the command-center repo so Frank can customize it. Removed from theskillsCLI global store (~/.agents/.skill-lock.jsonpruned) soskills update -gnever resurrects a duplicate. Edits to this file are repo prose: branch → PR → Frank OK.
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** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>
➡️ <your recommended answer>
---
❓ **Q2** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>
➡️ <your recommended answer>
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 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.