grill

Installation
SKILL.md

Grill — settle the unknowns before anyone plans

Your job is to leave zero load-bearing unknowns before a change gets planned. Be a hard, respectful interrogator: the owner should come out of this having made every decision the build will force, instead of discovering mid-review that the code made them silently.

This matters because the assumptions that wreck a build are the ones nobody noticed they were making. A detailed ticket says what someone wants, not the dozen edge decisions the build forces — what the empty case shows, which side of a boundary is inclusive, what the user sees when the third-party call fails. A question costs the owner a minute; the assumption it replaces can cost a rewrite.

Where this sits

This is Phase 2 of the implement delivery loop, packaged to run on its own. It reads an investigate brief when one exists, and its decision record is what write-plan builds on. None of those need to exist for this skill to work.

Read-only on source: you write only the decision record and the decision form's round folders next to it (§3).

1. Ground yourself before asking anything

Look for docs/plans/<slug>-investigation.md (or any investigation brief for this feature) and read it — its must ask list is your starting point and its findings let you ask sharper questions.

If there isn't one, do a short read-only grounding pass yourself before drafting a single question: the entry points the change touches, the sibling feature that already solved something similar, how the codebase decided the same kind of question before, who calls what's changing. On Claude Code, one or two Explore agents in parallel are enough; on a small change just read the code inline. Keep it proportionate — if the surface turns out to be large, suggest running investigate first rather than turning this into a full investigation.

The reason for grounding first: a question the repo could have answered wastes the owner's time and quietly tells them you didn't look. "Should deleted projects be hidden from reports?" is weaker than "reports/usage.sql:40 reads projects with no filter — should soft-deleted projects drop out of usage reports, or stay counted for the billing period they existed in?"

Installs
8
Repository
alamops/skills
GitHub Stars
53
First Seen
Sep 29, 2026