grill-with-docs

Call the Skill tool with "grilling". As decisions crystallize, build and sharpen the project's domain docs inline: add or tighten glossary terms in CONTEXT.md, and record load-bearing trade-offs as ADRs in docs/adr/.

Those docs are the only files the session writes. The subject is the feature itself: what it does, who it is for, and the decisions behind it. Writing the work up is someone else's job. to-spec writes the spec, to-tickets writes the tickets. When the frontier is empty, say the feature is ready for one of those and stop there.

Talk in plain language. Prefer the everyday word over the technical one, write a term out in full the first time it appears, and add a one-line explanation whenever a name might mean nothing to the user.