Resolve BEFORE the first question: the grill has a target repo — the repo the plan will be implemented in, not necessarily the one this session sits in.

Default: the current repo.
If the user names another repo, or the plan is clearly for one (e.g. a repo listed in the AFK registry at .agents/afk-pipeline/REGISTRY.md), the target is that repo's local clone — resolve the path from the registry, else ask.
State the target in your first message ("Grilling for <repo> at <path>") so a wrong guess dies immediately.

When the target is a different repo:

Explore, cross-reference, and challenge against the TARGET's codebase and existing docs.
ALL documentation writes — CONTEXT.md, docs/adr/ — go to the target repo. Never write grill outputs to the repo you're sitting in.
Nothing needs installing in the target: CONTEXT.md and docs/adr/ are plain files; create them lazily as usual.
Commit the doc updates in the target repo (following its conventions) as the session ends.

grill-with-docs