Menu
The same relentless interview as grill-with-docs, but for when you have no codebase. Stateless — it saves nothing locally, builds no CONTEXT.md.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Ask which skill or flow fits your situation. A router over the skills in this repo.
Implement a piece of work based on a spec or set of tickets.
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
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.
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
| name | grill-me |
| description | The same relentless interview as grill-with-docs, but for when you have no codebase. Stateless — it saves nothing locally, builds no CONTEXT.md. |
Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
Ask the questions one at a time, waiting for feedback on each question before continuing. Asking multiple questions at once is bewildering.
This skill is stateless — it does not read or write to CONTEXT.md, docs/adr/, or any other project file. Use it for sharpening a plan that doesn't live in a repo, or before a codebase exists.
COMPLETION PROTOCOL: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
