Jtbd job mapper

Skill lishix520/jtbd-skills/skills/jtbd-job-mapper

Modular agent skills for Jobs-to-be-Done and Outcome-Driven Innovation research.

Install

npx -y skills add lishix520/jtbd-skills --skill jtbd-job-mapper

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

14 days oldThe repository was created 14 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Deconstruct a defined Core Functional Job into a chronological Universal Job Map across standard stages (define, locate, prepare, confirm, execute, monitor, modify, conclude). Use when asked to map the steps of a customer job, identify functional dependencies between steps, or uncover missing execution steps in a workflow. Do not use to write desired outcome statements, calculate opportunity scores, or recommend product strategy.

SKILL.md

3.8 KB, 770 tokens by cl100k_base, as published. Nobody here has run it

JTBD Job Mapper

Deconstruct a customer job from start to finish to find where the journey gets stuck.

Use this when

You have a defined Core Functional Job and want to break it down into an 8-stage universal execution map.
You want to identify functional step dependencies, conditional loops, or missing preparation/monitoring steps.
You want to pinpoint which specific execution stage has the highest uncertainty or friction for research.

Don't use this when

You need to extract qualitative switching forces or non-consumption barriers (use jtbd-context-explorer or jtbd-forces-analyzer).
You need to write formulaic outcome metrics for a specific step (use jtbd-outcome-engineer).
You have survey ratings and need Opportunity Scores (use jtbd-opportunity-calculator).

Minimum input

Minimum Input: A Core Functional Job statement and Job Executor. Supports two starting points:
1. Validated Job: Maps an accepted Core Functional Job.
2. Candidate Job: Maps a candidate job hypothesis, explicitly marking unverified steps as hypothesis or domain_rationale.

What you get

Human Summary: Journey summary in one sentence, likely pain points to test, and unknown steps to validate.
Universal Job Map: Step statements organized across up to 8 universal stages (define, locate, prepare, confirm, execute, monitor, modify, conclude).
Flow Dependency Graph: Functional dependencies (flow.edges) between stages.

Quick prompt

"Break down the execution steps for this job statement: '[Paste job statement]'."

What to do next

Select a specific job map step with high friction or uncertainty -> Pass to jtbd-outcome-engineer to formulate Desired Outcome Statements.

Universal Job Map Stages

Define: Determine objectives and plan execution.
Locate: Gather necessary information, inputs, or materials.
Prepare: Set up the environment, format inputs, or configure tools.
Confirm: Verify readiness, completeness, or safety before execution.
Execute: Perform the core functional action of the job.
Monitor: Track execution progress, status, or environmental changes.
Modify: Adjust or revise execution when monitoring reveals variance.
Conclude: Finish, store, hand off, or clean up after execution.

Output Format

human_summary:
  job: ""
  journey_in_one_sentence: ""
  likely_pain_points_to_test: []
  unknown_steps_to_validate: []

job:
  core_functional_job: ""
  status: candidate | accepted
  job_executor:
    value: ""
    status: direct_evidence | inferred | unknown

map_status: provisional | validated

stages:
  - category: define | locate | prepare | confirm | execute | monitor | modify | conclude
    applicability: present | conditional | unknown
    steps:
      - statement: ""
        status: evidence_supported | hypothesis
        basis: direct_evidence | domain_rationale
        evidence: []
        assumptions: []

flow:
  edges:
    - from: ""
      to: ""
      when: ""
  branches: []

excluded_items: []
evidence_gaps: []
next_research_question: ""

Reference

Read references/universal-job-map-rules.md before:

Distinguishing job steps from solution features
Mapping conditional loops (monitor -> modify -> execute)
Assigning step basis (direct_evidence vs domain_rationale)