Skip to content

feat(skills): grill-me checks the code before asking each question #114

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bhagyamudgal merged 2 commits into from
Nov 12, 2026
Merged

feat(skills): grill-me checks the code before asking each question #114

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a957cbf
feat(skills): ground every grill-me question in the code before asking
bhagyamudgal Nov 12, 2026
2b74bc3
fix(skills): keep grill-me asking about decisions the plan changes
bhagyamudgal Nov 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions skills/grill-me/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ If I invoke you with a file path argument, read that file first and grill its co

Ask every question through the AskUserQuestion tool, so each decision reaches me as a selectable option.

- Before the first question, enumerate the open decisions in the plan as a numbered list and print it.
- Before the first question, read the code the plan touches and check the files, symbols, and behavior its decisions rest on. Then enumerate the open decisions as a numbered list and print it. Leave out any decision the code already settles and the plan does not change, and name the `file:line` that settled it.
- When the open list holds more than 10 decisions, group them by area and offer to settle a whole group in one answer.
- Ask decision zero first: is this approach even right. Offer one credible alternative drawn from the codebase or the issue, and grill it before the rest.
- Ask one question at a time. Make one AskUserQuestion call per turn, then wait for my answer.
Expand All @@ -22,7 +22,7 @@ Ask every question through the AskUserQuestion tool, so each decision reaches me
- After each answer, acknowledge the choice in 1 sentence max, ending with `<n> of <total> resolved`, then ask the next question.
- If my answer is non-committal, something like "not sure" or "whatever you think" or "both", do not record it. Restate the trade-off in one sentence and re-ask the same decision once. Record the second answer either way.
- When an answer contradicts an earlier one or leaves a dependency unresolved, say which one and re-ask before moving on.
- If you can answer a question by exploring the codebase, explore it instead of asking me. Use Grep, Glob, Read, or Agent to verify assumptions before grilling me on them.
- Ground every question in the code before asking it: read the files and symbols it rests on. When the code answers it and the plan does not propose changing that behavior, record that answer with its `file:line` and move on without asking. Otherwise build the options and the recommendation from what you found, and cite the `file:line` in the context line. When no code bears on the decision, say so in the context line.
- If I say "enough" or "done" or "stop" or "skip the rest", append per the file rule and post per the issue rule below with the decisions captured so far, then announce "Grill complete." and exit.
- Every "Grill complete." announcement ends with a `Pending on you:` line that names each decision or action still waiting on me, or reads `Pending on you: nothing`.
- When every numbered decision has a recorded answer and no answer has opened a new one, move to the verification pass below instead of closing out. If an answer opens a new decision, append it to the list and say so.
Expand Down
Loading