agentleFS
anilkkanilkk/jobs-to-be-done-claude-skill/jobs-to-be-done/SKILL.md

jobs-to-be-done

Skill0 starsChanged 3 months agoLicence not identifiedView on GitHub

Apply Jobs-to-be-Done thinking (Tony Ulwick's "Jobs to be Done: Theory to Practice") to any product, feature, project, or task. Use whenever the user wants to identify the job a customer is trying to get done, break a job into steps and needs, prioritize unmet needs, or plan what to build and how to position it. Trigger on "JTBD", "job to be done", "what job is this solving", "jobs framework", "desired outcomes", "job map", "opportunity score", "underserved needs", "outcome-driven", or casual asks like "help me plan this feature around customer needs" or "JTBD this". Three modes - Discover (define the job), Break down (job map + desired outcomes), Plan (prioritize opportunities and pick a growth strategy).

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use proto-persona, usability-test-plan and 10 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.
  • nandanosqlSkill

    proto-persona

    Create hypothesis-driven user personas before doing full research. Uses behavioral attributes, goals, and frustrations to model target users quickly for early-stage alignment.

    Also in 4 projects that use this

  • launchapp-devSkill

    usability-test-plan

    Design a usability test plan with tasks, success metrics, participant criteria, and facilitation guide. Use when planning moderated or unmoderated usability testing sessions.

    Also in 3 projects that use this

  • nandanosqlSkill

    acquisition-channel-advisor

    Evaluate and recommend customer acquisition channels based on product type, target audience, budget, and stage — covering organic, paid, referral, partnerships, and product-led growth.

    Also in 3 projects that use this

  • brainbytes-devSkill

    balanced-scorecard

    Also in 3 projects that use this

  • +8 more from nandanosql

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

The licence could not be identified — 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 20 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.