interview-me
Skill339 starsChanged 2 months agoMITView on GitHub
Interview the user one question at a time to resolve remaining ambiguity before implementation. Use when planning or brainstorming is done but unknowns remain, or when the user asks to be interviewed about a task or spec.
98 other projects use a version of this.
Adopted by
Most recently taken up by
- thistleknot/skillstheir own version, first seen Nov 8, 2026
- ishandutta2007/Awesome-Agent-Skillstheir own version, first seen Nov 8, 2026
- pedrohcgs/claude-code-my-workflowtheir own version, first seen Nov 8, 2026
- resonatingloop/hmmariumtheir own version, first seen Nov 8, 2026
- ggoosen/Digital-Workforcetheir own version, first seen Nov 8, 2026
- MMACABRE/SKILLStheir own version, first seen Nov 8, 2026
Used with
Projects with it also use constraint-driven-development, idea-refine and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MrCipherSmithSkillconstraint-driven-development
Use when a project needs a persistent, measurable quality bar — starting a project without documented standards, 'set up constraints', or when coverage/perf/a11y thresholds get re-debated per-PR. Produces CONSTRAINTS.md with enforceable numbers, ratchets, and a guard against silent weakening. NOT for throwaway prototypes or a one-off CI setup.
Also in 16 projects that use this
LLl0k0laDSkillidea-refine
Refine ideas through structured divergent and convergent thinking. Use "idea-refine" or "ideate" to trigger.
Also in 42 projects that use this
- LLl0k0laDSkill
using-agent-skills
Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.
Also in 32 projects that use this
HK-hubSkillobservability-and-instrumentation
Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.
Also in 32 projects that use this
- HK-hubSkill
deprecation-and-migration
Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.
Also in 29 projects that use this
- +6 more from LLl0k0laD
Other versions98 projects use a version of this.
Word for word · 1
- edenbuilds/agentloop★ 0100% same
Edited · 0
None found.
Wrote their own version · 97
- addyosmani/agent-skills★ 114ksame name
- pedrohcgs/claude-code-my-workflow★ 1.7ksame name
- kdlbs/kandev★ 1.1ksame name
- flonat/flonat-research★ 150same name
- maxwell2732/paper-replicate-agent-demo★ 134same name
- maxwell2732/my-submission-formatting-agent★ 106same name
- PaulRBerg/agent-skills★ 104same name
- c-kick/hnl-agent-skills★ 56same name
- Sorbh/interview-me★ 52same name
- mycelium-hq/ai-brain-starter★ 50same name
87 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-interface-designSkill
- assumption-testSkill
- blindspot-passSkill
- brainstorm-prototypesSkill
- change-quizSkill
- context-auditSkill
- implementation-notesSkill
- implementation-planSkill
- pitch-packagerSkill
- progressive-disclosureSkill
- reference-huntSkill
- regression-proofSkill
- test-blindspotsSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 83 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Read everything already established: the request, any spec, any prototypes, relevant code.
- Distinctive: line 17
Ask exactly one question per turn.
- Distinctive: line 18
Every few questions, checkpoint: restate what has been decided so far in one tight list, so drift dies early.
- Distinctive: line 19
Stop when the remaining unknowns are cheaper to discover during implementation than to ask about now, and say that out loud.
- Distinctive: line 24
Never ask a question whose answer is discoverable from the codebase.
- Distinctive: line 25
If an answer contradicts an earlier decision, flag the conflict immediately rather than silently taking the newest answer.
“Common” is measured: kept by at least 6 in 10 of the 83 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Interview me
Brainstorming is over and there are still gaps between the user's map and the territory. Close them by asking, one question at a time, starting with the questions whose answers would change the most.
Steps
- Read everything already established: the request, any spec, any prototypes, relevant code. Do not ask about things that are already answered.
- Build a private list of open ambiguities and sort by blast radius:
- First: architecture-changers — answers that would alter the data model, the interfaces, or the overall approach.
- Then: behavior definers — edge cases, failure modes, defaults, permissions.
- Last: polish — naming, copy, cosmetics. Often not worth asking; propose and move on.
- Ask exactly one question per turn. For each: give the context that makes it matter, offer 2-3 concrete options with your recommendation, and accept "you decide" as an answer you then own.
- Every few questions, checkpoint: restate what has been decided so far in one tight list, so drift dies early.
- Stop when the remaining unknowns are cheaper to discover during implementation than to ask about now, and say that out loud. End with the final decision list, ready to paste into a plan.
Guardrails
- One question at a time means one. No question bundles.
- Never ask a question whose answer is discoverable from the codebase; go look instead.
- If an answer contradicts an earlier decision, flag the conflict immediately rather than silently taking the newest answer.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.