grill-docslisted

Run the `grilling` interview and write it down as you go. Nothing about the interview changes: rounds, one recommendation per question, wait for answers. The difference is that the session leaves files in the repo. ## 1. Where things land All output goes under `skilleddocs/` at the repo root (see the skills repo README, "Where skills write"). Create the directory and files lazily. | What | Path | |---|---| | The session transcript | `skilleddocs/grills/<YYYY-MM-DD>-<slug>.md` | | The decision register | `skilleddocs/decisions.md` (append; create with a header if missing) | A repo's `AGENTS.md` / `CLAUDE.md` may name a different decisions doc (`docs/decisions.md`, an ADR folder). If it does, append there instead and say so in the transcript header. Slug: the user's argument if they gave one, else 2–4 kebab-case words from the topic. Date: the user's local date (`date +%F`, or `python -c "import datetime as d;print(d.date.today())"`), never UTC. ## 2. Start the transcript before the first round Write the file header immediately so a crashed or abandoned session still leaves something: ```markdown # Grill: <topic> Date: <local date> · Subject: <doc path or one-line description> · Status: in progress ## Rounds ``` ## 3. Record each round as it settles After the user answers a round, append to the transcript, one block per question: ```markdown ### Q<n> — <question title> - Asked: <one-line restatement of the question and the options> - Recommended: <your recommendati