Menu
ask questions until shared understanding is reached
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
summarize the current session into a concise, well-structured document for the purpose of persisting important information across agent sessions
use for working with jj (jujutsu) version control system
invoked by the user to identify refactoring opportunities in the codebase
Instructions for working in Rust codebases
| name | grill-me |
| description | ask questions until shared understanding is reached |
Interview the user about the implications and the consistency of their request until a shared understanding of the design and the path forward is reached. When it's possible to obtain answers by querying the codebase, do that instead.
Identify any assumptions in the users original prompt or given answers and try to verify them against the codebase or plan for the eventuality they might be wrong.
Walk through the consequences of the requested change and ask to resolve any unclarity or inconsistency. For example if the proposed change has implications for existing APIs, database schemas or might cause significant refactoring, work through effective changes if it were to be applied.
Stop when there are no more open questions or unresolved contradictions with your understanding vs the user's intent.
Clearly and concisely, but completely restate the user's intent with all the resolved contentious points so that they can be handed off to an agent to create the actual plan.
