grilling: questions rely on names made up earlier in the session

### Skill grilling ### What went wrong Over about seven weeks of daily grilling in Claude Code (mostly Fable 5.1, some Opus 5.5), around 40 of my replies to a round were some form of "huh?" or "simplify the question". That's despite most of my grill prompts asking for self-contained questions. Nearly every time, the question relied on something only defined earlier in the session: a label the agent made up ("the fund accumulator", "slice 2 design"), a finding from an earlier message, or a doc I couldn't see. e.g. this question from 22 Sep (Fable 5.1), in a session about organising my Claude Code sessions: ``` ❓ **Q8** - **Sidebar groups**: Today groups are per RFC and half your sessions are ungrouped. Options: (a) keep RFC groups, bearings files sessions into them from the ticket; (b) state groups managed by bearings: Needs me, Running, Docked; (c) both, which the sidebar cannot do, so pick one. ➡️ (b). The RFC is in the title once titles carry the key, so the group can carry the thing the title cannot: whether the session needs you. Bearings moves sessions between groups on every run. ``` "bearings" is a tool from another project that the agent had mentioned once, half an hour earlier. "Docked" was its own word for a finished session, and "the key" was never defined. My reply was "Q8. i don't understand the question, explain in more detail, clear and simple". #1115 covers one case of this (bare `Q3` back-references), but restating the title next to the number doesn't help when the question body relies on earlier context. `wait-what` fixes it after the fact, though in a round it's often every question, so I think it's better to avoid the problem up front. ### Proposed change One rule under the round format in `skills/productivity/grilling/SKILL.md`: ``` Make each question answerable on its own: briefly restate whatever it relies on from earlier in the session, and use only the user's words or the project's own names, defining any other term in the question. ``` The project's own names (code identifiers, `GLOSSARY.md`) are still fine, so this fits the shared-language idea. It only rules out names that exist nowhere except earlier in the chat.