afk-grilllisted

# Skill: afk-grill Interview the user relentlessly about every branch of their plan until you share a model of the design. As decisions crystallise, write them into `CONTEXT.md` (vocabulary) and `docs/adr/` (decisions worth a paper-trail). The transcript of this session becomes the input for `afk-prd`. This is the lightly-revised universal version of [`mattpocock/grill-with-docs`](https://www.skills.sh/mattpocock/skills/grill-with-docs) — same philosophy, fewer assumptions about your repo layout, and tuned to dovetail with the rest of the AFK pipeline. ## What to do Interview the user **one question at a time**. Walk down each branch of the design tree. For each question: 1. Propose your recommended answer (with a one-line reason). 2. Wait for feedback. 3. Either accept their answer or push back once with a concrete alternative — then accept. If a question can be answered by reading the codebase, **read the codebase instead** and report what you found. ## Domain awareness During exploration, also look for existing documentation. Most repos have a single context: ``` / ├── CONTEXT.md ├── docs/ │ └── adr/ │ ├── 0001-event-sourced-orders.md │ └── 0002-postgres-for-write-model.md └── src/ ``` If a `CONTEXT-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives: ``` / ├── CONTEXT-MAP.md ├── docs/adr/ ← system-wide decisions └── src/ ├── ordering/ │ ├── CONTEXT.md │ └──