grill-me
Surface what the user has NOT anticipated, before any plan or code exists.
Step 0: decide, out loud
Do not judge whether to invoke this skill; you already did. Judge here, once, and say the
answer.
Apply the same test that ends the grilling, at its start: could you write the
orchestrator dispatch prompt right now without guessing at scope-out, acceptance, or
which existing behavior this touches?
- Yes -> say so in one line, naming what makes it precise ("scope already precise:
one field, acceptance stated, no existing behavior touched"), then dispatch. Done.
- No -> grill, starting with whichever area below is emptiest.
Never skip silently. The one-line exit is what tells the user why no questions came.
Without it, "already precise" and "the skill never ran" look identical from the outside,
and only one of them is fine.
How to grill
- One question at a time, in prose. Never a multiple-choice menu, never a batch of
five at once.
- Read the answer, then ask the next most valuable question given it.
- Stop as soon as the scope is answerable by the Step 0 test. Do not interrogate for
its own sake.
Cover, at minimum
- Scope-out: what is explicitly NOT in scope? What might look included but isn't?
- Edge cases: empty / invalid input, network or backend error, two users at once.
- Existing interactions: does this touch behavior already in place (permissions,
RLS, cached data, shared views, another resource)?
- Definition of done: what manual check confirms it works? Who validates before merge?
- Reversibility: if it turns out wrong, how hard is it to undo?
If the user answers "I don't know" to a structural question, propose an explicit
hypothesis and ask them to confirm rather than silently choosing.
After grilling
Fold the answers into the orchestrator dispatch prompt: scope-out and acceptance become
ticket constraints.
1---2name: grill-me3description: Scope a4---56# grill-me78Surface what the user has NOT anticipated, before any plan or code exists.910## Step 0: decide, out loud1112Do not judge whether to invoke this skill; you already did. Judge here, once, and say the13answer.1415Apply the same test that ends the grilling, at its start: **could you write the16orchestrator dispatch prompt right now without guessing** at scope-out, acceptance, or17which existing behavior this touches?1819- **Yes** -> say so in one line, naming what makes it precise ("scope already precise:20 one field, acceptance stated, no existing behavior touched"), then dispatch. Done.21- **No** -> grill, starting with whichever area below is emptiest.2223**Never skip silently.** The one-line exit is what tells the user why no questions came.24Without it, "already precise" and "the skill never ran" look identical from the outside,25and only one of them is fine.2627## How to grill2829- **One question at a time**, in prose. Never a multiple-choice menu, never a batch of30 five at once.31- Read the answer, then ask the next most valuable question given it.32- **Stop as soon as the scope is answerable** by the Step 0 test. Do not interrogate for33 its own sake.3435## Cover, at minimum36371. **Scope-out**: what is explicitly NOT in scope? What might look included but isn't?382. **Edge cases**: empty / invalid input, network or backend error, two users at once.393. **Existing interactions**: does this touch behavior already in place (permissions,40 RLS, cached data, shared views, another resource)?414. **Definition of done**: what manual check confirms it works? Who validates before merge?425. **Reversibility**: if it turns out wrong, how hard is it to undo?4344If the user answers "I don't know" to a structural question, propose an explicit45hypothesis and ask them to confirm rather than silently choosing.4647## After grilling4849Fold the answers into the orchestrator dispatch prompt: scope-out and acceptance become50ticket constraints.
marmelab