jobs-to-be-done
Skill6 starsChanged 4 months agoApache-2.0View on GitHub
Use when product, service, sales, or messaging work needs to understand why someone would switch, buy, adopt, or reject. Use when applying the Jobs To Be Done consulting method and when a user asks for Jobs To Be Done, method execution, structured diagnosis, or action planning.
23 other projects use a version of this.
Adopted by
Most recently taken up by
- miguelclavel/ux-research-skillstheir own version, first seen Nov 8, 2026
- vijaysuperpositionist/skillstheir own version, first seen Nov 1, 2026
- deanpeters/Product-Manager-Skillstheir own version, first seen Oct 25, 2026
- OptionalGanesh/claude-skillstheir own version, first seen Oct 20, 2026
- anilkk/jobs-to-be-done-claude-skilltheir own version, first seen Oct 15, 2026
- The-Utopia-Studio/skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use proto-persona, usability-test-plan 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.
nandanosqlSkillproto-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-devSkillusability-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
nandanosqlSkillacquisition-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
- +8 more from nandanosql
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 23
- deanpeters/Product-Manager-Skills★ 8ksame name
- wondelai/skills★ 2.7ksame name
- launchapp-dev/animus-cli★ 39same name
- deciqAI/knowledge-skills★ 13same name
- DIAL-Studio/pm-agent-harness-kit★ 12same name
- flpbalada/fb-skills★ 8same name
- huntsyea/product-skills★ 8same name
- The-Utopia-Studio/skills★ 6same name
- Dragoon0x/product-skills★ 4same name
- Adhamxon/claude-code-skills★ 2same name
13 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 repository57 other files it gives its agents.
- 5w1h-analysisSkill
- abductive-reasoningSkill
- account-planSkill
- affinity-diagramSkill
- assumption-inventorySkill
- balanced-scorecardSkill
- break-even-analysisSkill
- business-model-canvasSkill
- change-event-timelineSkill
- change-impact-analysisSkill
- communications-planSkill
- competitive-positioningSkill
- constraint-analysisSkill
- cost-benefit-analysisSkill
- critical-uncertaintiesSkill
- customer-segmentationSkill
- customer-success-health-scoreSkill
- deal-strategy-mapSkill
- decision-matrixSkill
- deductive-reasoningSkill
- effort-impact-matrixSkill
- empathy-mapSkill
- evidence-mapSkill
- fifteen-percent-solutionsSkill
- first-principles-thinkingSkill
- fishbone-diagramSkill
- five-whys-root-causeSkill
- force-field-analysisSkill
- go-to-market-diagnosisSkill
- hypothesis-treeSkill
- inductive-reasoningSkill
- issue-treeSkill
- kano-modelSkill
- mece-frameworkSkill
- metrics-treeSkill
- mind-map-analysisSkill
- min-specsSkill
- north-star-metricSkill
- pestel-analysisSkill
- porter-five-forcesSkill
- power-interest-gridSkill
- pre-mortemSkill
- pricing-strategy-checkSkill
- raci-matrixSkill
- rice-scoringSkill
- risk-matrixSkill
- scenario-planningSkill
- service-blueprintSkill
- signal-vs-noise-filterSkill
- stakeholder-power-mapSkill
- swot-analysisSkill
- systems-thinkingSkill
- user-journey-mappingSkill
- validation-planSkill
- weighted-scorecardSkill
- win-loss-reviewSkill
- wsjf-prioritizationSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Use this skill to run Jobs To Be Done as a practical consulting method, not as a generic framework explanation.
- Very specific: line 26
If an input is missing, do not block automatically.
- Distinctive: line 30
Do not use to translate feature requests directly into a backlog or to infer a job from demographics.
- Distinctive: line 88
Keep wording professional and plain enough that a smart non-specialist can use the output directly.
“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.
Files
Jobs To Be Done
Use this skill to run Jobs To Be Done as a practical consulting method, not as a generic framework explanation.
Method Notes
- Describe progress in a circumstance, not a product category.
- Capture functional, social, and emotional forces plus push, pull, anxiety, and habit.
Required Inputs
Collect or infer these inputs before execution:
- target customer
- situation
- current workaround
- desired progress
- switching evidence
If an input is missing, do not block automatically. Mark it as missing, state the assumption used, and add a validation action.
When Not To Use
Do not use to translate feature requests directly into a backlog or to infer a job from demographics. Anchor the analysis in a specific struggling moment, desired progress, context, and current alternatives.
Adjacent Methods
empathy-map: one actor's perceptions and behavior.user-journey-mapping: chronological user experience.service-blueprint: frontstage/backstage operating process.
Step-by-Step Execution
| Step | Required input | How to execute | Output |
| Define circumstance | Customer situation, trigger, current workaround. | Describe when the customer starts looking for progress. | Job circumstance. |
| Write job statement | Customer goal, struggle, desired progress. | Express the job as progress, not product usage. | Job statement. |
| Map forces | Pushes, pulls, anxieties, habits, alternatives. | Identify forces moving the customer toward or away from change. | Forces-of-progress map. |
| Define success criteria | Functional, social, emotional outcomes. | State what good enough looks like in customer language. | Outcome criteria. |
| Translate to offer | Job, forces, outcomes. | Recommend product, service, message, sales, or validation implications. | JTBD action implications. |
Output Template
### 1. Circumstance And Progress
Target customer:
Triggering situation:
Current workaround:
Progress sought:
### 2. Job Statement
When:
I want to:
So I can:
Evidence:
### 3. Forces And Outcomes
| Push / pull / anxiety / habit | Evidence | Strength | Implication |
|---|---|---|---|
| | | | |
### 4. Offer And Adoption Tests
| Outcome / barrier | Offer response | Test | Signal |
|---|---|---|---|
| | | | |
### Evidence And Next Decision
- Confirmed facts:
- Assumptions:
- Missing evidence:
- Next action, owner, and timing:
- Expected signal and decision threshold:Quality Gate
- Produce the method-specific outputs for Circumstance And Progress, Job Statement, Forces And Outcomes; do not substitute a generic framework summary.
- Tie every material score, causal claim, or stakeholder judgment to evidence or label it as an assumption.
- Include at least one disconfirming check, sensitivity, alternative explanation, or failure condition appropriate to the method.
- Convert the result into a named action or decision with an owner or stakeholder, timing, and observable signal.
- State missing inputs and the smallest validation action instead of inventing precision.
- Keep wording professional and plain enough that a smart non-specialist can use the output directly.
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.

