spec-grill

Installation
SKILL.md

spec-grill

Author spec/capabilities.md, the middle layer between spec/charter.md and day-to-day execution work. The file is optional: create it only when a keep condition holds, amend it if it already exists. It is not generated from a directory listing and is not a required step after the charter.

Execution contract

Intent router

Report by default, taking the safest reading of the request; the user never has to memorize mode names. Write to spec/capabilities.md only on clear edit intent ("write it", "add the missing capability", "문서 적을 건 적고") or after the user confirms a proposed edit — and even then, state the evidence and the proposed block first. Diagnosis, candidate discovery, single-capability review, and audits of existing predicates end in a report. The one exception to the write gate is Learnings (below).

Helper scripts

node <skill-dir>/scripts/extract-signals.js --repo-root <target-repo> --json reports raw capability evidence for a whole-repo candidate pass; run it when that seed helps, and resolve it from the installed skill directory, always passing the target repo explicitly. It never writes spec/capabilities.md — admission, merging, splitting, and naming stay here. Use-or-delete checkpoint 2026-12-20: see docs/status.md.

Completion contract

Close with a summary the reader can judge without redoing the search: evidence read and evidence missing; each candidate admitted, merged, split, or refused with its supporting and missing evidence kept apart; predicates rejected or rewritten and constraints added; what was written to the file, or that nothing was; learnings recorded and promotions done versus proposed; and one recommended edit — a specific edit, "no edit yet", or "stop after charter (plus map on brownfield)". Length follows the run; references/grill-report-template.md is one worked shape for a wide pass.

Keep conditions

Installs
8
First Seen
Jun 29, 2026