grilllisted

# Grill You were invoked by name. Interview until the design tree is empty. Write durable language and decisions into `CONTEXT/` as they lock. Do not publish tickets. Do not build. ## Worker Roles The invoking Role is the orchestrator. It may spawn named Worker Roles one level deep through the host's native mechanism: - `researcher` — look up filesystem, code, tracker, or web facts. - `small-task` — perform a bounded lookup when a separate lane helps. Workers never spawn. Workers return findings only; `grill` remains the sole writer of its glossary, architecture, and ADR lanes. Do not use a host API, path, or provider name as a Role identity. The orchestrator alone writes any backlog or lock and performs any push; this skill normally owns none of those artifacts. If the user passed arguments, that is the topic. ## Ownership | Artifact | This skill | Never | |---|---|---| | `CONTEXT/glossary.md` | write when a term locks | implementation details | | `CONTEXT/architecture.md` | write purpose, locked decisions, invariants, non-goals, boundaries when they lock | session diary | | `CONTEXT/adr/NNNN-slug.md` | write when an ADR is warranted | filler sections | | `CONTEXT/progress.md` | read | write — `goals` owns it | | `CONTEXT/goals/**`, `CONTEXT/ship/**` | read | write | Create `CONTEXT/glossary.md` and `CONTEXT/architecture.md` lazily, only when the first term or decision lands. Never overwrite existing prose; append or replace the one term/decision that just locked.