agentleFS
Sign inStart free
The-AI-ThinkerThe-AI-Thinker/claude-code-pm-starter/.claude/skills/interview-synthesis/SKILL.md

interview-synthesis

Skill13 starsChanged 3 months agoMITView on GitHub

Turn raw user-interview notes or a transcript into a filed synthesis, kept separate from interpretation, and route durable findings to the context files. Use after the user runs one or several user interviews.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. imohammadfaraz/claude-skills-for-product-manager★ 19same name

    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 repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow-ups: what to probe in the next session.

    line 20
  2. Very specific:

    Promote what's durable: If a finding holds across several interviews, offer to update context/users.md (What we know) with a one-line …

    line 22
  3. Distinctive:

    Never present one participant's view as "users want".

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Interview synthesis

Turn what a user said into something the team can act on, and file it where future sessions will find it.

Steps

  1. Take the raw material. A transcript, rough notes, or a voice-note dump. Ask for the interview goal and who the participant was (role, segment) if not stated.
  2. Separate observation from interpretation. First pass: what the participant actually said and did, with short verbatim quotes. Second pass: what you and the user think it means. Never blend the two; a quote is evidence, a reading is a hypothesis.
  3. Structure the synthesis:
    • Participant: role, segment, context, date.
    • Goal of the session.
    • What they said and did: the strongest verbatim moments, each with a one-line setup.
    • Readings: the hypotheses these moments support or weaken, stated as hypotheses.
    • Contradictions: where what they said conflicts with what they do, or with previous interviews.
    • Follow-ups: what to probe in the next session.
  4. File it. Save to operations/ with the date and participant slug in the filename, for example 2026-08-14-interview-nadia-churn.md.
  5. Promote what's durable. If a finding holds across several interviews, offer to update context/users.md (What we know) with a one-line digest pointing at the filed syntheses. Single-interview findings stay in operations/; patterns get promoted.

Rules

  • Quotes stay verbatim, including hesitations that carry meaning. Cleaning up a quote destroys the evidence.
  • Flag leading questions you notice in the transcript; the next interview gets better.
  • Never present one participant's view as "users want". One voice is a data point.

Download now (ZIP)

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.

Check your setup, free