Jtbd job definer

Skill lishix520/jtbd-skills/skills/jtbd-job-definer

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

Install

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

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

Extract, audit, or rewrite a solution-free and outcome-free Core Functional Job statement from customer quotes or candidate sentences. Use when given a proposed product feature or customer statement and asked to express the underlying functional job, audit a job statement for solution contamination, or determine if enough evidence exists to validate a job statement. Do not use to map job steps, write desired outcomes, calculate opportunity scores, or recommend product strategy.

SKILL.md

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

JTBD Job Definer

Rewrite "I want this feature" into a solution-free customer job statement.

Use this when

A user asks for a specific product feature or button, and you need to uncover the underlying solution-free goal.
You have a proposed Core Job statement and need to audit it for embedded technologies, products, quality adjectives, or outcome metrics.
You want to establish a clean Core Functional Job statement before mapping workflow steps.

Don't use this when

You want to extract raw circumstances, non-consumption barriers, or feature requests without defining a job (use jtbd-context-explorer).
You need to map the step-by-step execution journey (use jtbd-job-mapper).
You need to engineer quantitative metric statements (use jtbd-outcome-engineer).

Minimum input

Minimum Input: A customer statement, feedback quote, feature request, or candidate job statement. Includes two operating modes:
1. Audit Mode: Provide a job statement -> audits for embedded solutions, features, or outcomes.
2. Rewrite Mode: Provide a feature request or quote -> formulates a candidate solution-free job statement.

What you get

Plain Language Explanation: A 3-part summary explaining what the customer is trying to do, what was removed (and why), and what evidence is still missing.
Core Functional Job Statement: A single solution-free, outcome-free functional statement ([Verb] + [Object of Control] + [Contextual Clarifier]).
Quality Check Audit: Boolean checks verifying customer perspective, solution-free, outcome-free, and appropriate scope.

Quick prompt

"Rewrite this feature request into a solution-free Core Functional Job: '[Paste feature request or quote]'."

What to do next

Core job accepted or candidate defined? Pass to jtbd-job-mapper to break it down into an 8-stage functional workflow map.

Operating Rules

Solution-Free Rule: A Core Functional Job MUST NOT mention any technology, product, feature, tool, or vendor name.
Outcome-Free Rule: A Core Functional Job MUST NOT contain quality adjectives or performance metrics (e.g., "fast", "reliable", "cheap", "easily"). Performance criteria belong in Desired Outcome Statements (jtbd-outcome-engineer).
Single Job Focus: Output exactly ONE Core Functional Job statement per request.
Status Discipline: Mark unverified inferences as status: candidate. Only mark status: accepted when direct source evidence proves the job executor's primary functional goal.

Output Format

plain_language:
  customer_is_trying_to: ""
  this_is_not_the_job_because: []
  what_we_still_need_to_know: ""

job:
  statement: ""
  status: candidate | accepted | insufficient_evidence
  executor: ""

evidence:
  direct: []
  inferred: []
  contradictions: []

quality_check:
  customer_perspective: pass | fail
  functional_only: pass | fail
  solution_free: pass | fail
  outcome_free: pass | fail
  appropriately_scoped: pass | fail

missing_evidence: []
next_research_question: ""

Reference

Read references/job-statement-rules.md before:

Stripping embedded technologies or features from candidate statements
Resolving whether a job is micro-scoped (step) or macro-scoped (life goal)
Auditing quality buzzwords and performance criteria