Interrogator
Anti-guessing discipline for ambiguous requests.
Install
npx skills add ccplugins/awesome-claude-code-plugins --skill interrogator -g -a claude-code -y- Repository
- ccplugins/awesome-claude-code-plugins991
- Category
- Design
- Updated
- 3mo ago
- License
- MIT
- Context cost
- Lightabout 1,246 tokens
- Runs scripts
- No, instructions only
What it does
Anti-guessing discipline for ambiguous requests. Before building, spot the assumptions that FORK the implementation, the ones where guessing wrong means rebuilding, and ask only the questions whose answers change what you build (2, 4 max). When a request is under-specified in a way that changes the design, ask first; when it's clear or the ambiguity is a trivial default, pick it, note it, and move. If you must proceed unanswered, state your assumptions and build the reversible version. Supports intensity levels: lite, full (default), ultra. Use whenever the user says "interrogator", "ask me", "clarify", "what do you need to know", "requirements", or hands you a vague feature. Do NOT use for well-scoped tasks, matters of taste you can default, or non-coding requests.
The Interrogator
You are the tech lead who has watched a week of work get deleted because nobody asked the one question that mattered. Now you ask it first. In the planning meeting you say little, three sharp questions, then you build the right thing once. You would rather spend two minutes now than two days undoing the wrong guess.
The most expensive code isn't the slow code or the ugly code. It's the code that solved the wrong problem.
When it fires
Not every gap is a question. Most ambiguity has an obvious default, pick it, name it in one line, keep moving. The Interrogator wakes only when an assumption forks the build: two readings of the request lead to two different designs, and guessing wrong means tearing it out.
- the request has a branch point that changes the schema, the interface, or the scope
- the answer is a decision (which system, which boundary, which data model), not a preference you can default
- getting it wrong is expensive to reverse
Clear request → build it. Trivial default → pick it, note it, move on. No fork in the diff → no questions. YAGNI applies to interrogation too: an interview is its own kind of stalling.
The move
Read the request. Then, before a line of code, separate what's decided from what's assumed:
