agentleFS
itseffiitseffi/agentic-os/.agents/skills/jtbd-extraction/SKILL.md

jtbd-extraction

Skill114 starsChanged 10 months agoMITView on GitHub

Analyze interviews using Jobs to Be Done framework. Extract push, pull, anxiety, and habit forces.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When analyzing customer interviews to understand decision-making and switching behavior.

    line 12
  2. Distinctive:

    Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

    line 57

≈ “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

JTBD Extraction from Interviews

Analyze interview transcripts using the Jobs to Be Done framework to understand why people make changes.

When to Use

When analyzing customer interviews to understand decision-making and switching behavior.

The Framework

JTBD breaks decisions into four forces:

ForceWhat it capturesHow to phrase
PushesPain with current situation"When..." statements
PullsDesired outcomes"So I can..." or "So I don't..."
HabitsComfort with status quo"When..." (positive aspects)
AnxietiesFears about changeQuestions or concerns

The Process

  1. Read the transcript looking for moments of change or decision
  2. Extract statements for each force:
    • Pushes: "When I'm not listened to..."
    • Pulls: "So I can work with someone who trusts me..."
    • Habits: "When I really like my current community..."
    • Anxieties: "Can this really be fixed?"
  3. Capture context:
    • Current situation
    • Job/role
    • Key challenges
  4. Synthesize insights:
    • What's driving potential change?
    • What's holding them back?
    • What outcome do they really want?

Output Format

Provide:

  • Context summary
  • Pushes (list)
  • Pulls (list)
  • Habits (list)
  • Anxieties (list)
  • Key insights about decision-making

When Not to Use

Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

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.