agentleFS
elvladislavoelvladislavo/claude-skills/.claude/skills/interview-me/SKILL.md

interview-me

Skill0 starsChanged 20 days agoNo licenceView on GitHub

Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.

101 other projects use a version of this, 39 of them edited; most edited versions we compared are an older text (27 of 36); 2 new projects in the last 4 weeks, against 0 the 4 before.

How people change it

Most projects run an older version: 27 of 36 add nothing and lack rules this one has, most likely added since.

Of the 36 edited versions we compared: 4 keep every rule, 27 are an older text, 5 made changes of their own.

Not in older versions

  1. STOP YOUR TURN IMMEDIATELY. Do NOT invoke tools or start downstream work in this turn. Hand control back to the user to choose the next step.missing from 27 of 27
  2. When the user confirms the statement of intent with an explicit "yes":missing from 26 of 27
  3. If the user wants the intent to persist (a multi-session project, a handoff to another collaborator), offer to save it to docs/intent/[topic].md. Only save if they confirm.missing from 1 of 27

Rules people drop

  1. When the user confirms the statement of intent with an explicit "yes":dropped by 4 of 5
  2. STOP YOUR TURN IMMEDIATELY. Do NOT invoke tools or start downstream work in this turn. Hand control back to the user to choose the next step.dropped by 4 of 5
  3. When you hear these, the question to ask is:dropped by 2 of 5
  4. When confidence is below ~70%, append a brief reason on the same line — what's still unresolved or missing. This tells the user exactly what the interview needs to surface, and prevents the number from being a vague signal.dropped by 2 of 5
  5. Wait for the user to react before asking the next question.dropped by 2 of 5
  6. If yes, you have shared understanding. Stop interviewing and produce the restate. If no, you're not done; ask the next question.dropped by 2 of 5
  7. Before asking anything, write down your current best read of what the user wants in one sentence, plus an honest confidence number (0–100%):dropped by 1 of 5
  8. When your confidence is high, write back what you now think the user wants. Keep it tight (5–8 lines), use their language where possible, and structure it so the user can confirm or correct line by line:dropped by 1 of 5

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Surging: 2 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 1 new projectWeek of Nov 1: 1 new projectWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 2 in all, so this is a hint, not a trend.

Most recently taken up by

Used with

Projects with it also use implementation-notes.

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.
  • orenluxySkill

    implementation-notes

    Maintain an IMPLEMENTATION_NOTES.md decision log during any multi-step implementation session. Use this in EVERY session that involves writing or modifying code across more than one file, or any session expected to run longer than a few tool calls. Records decisions, deviations from plan, and open questions so nothing is silently guessed.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 76 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 76 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.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.