jobs-to-be-done

Create and review Jobs to be Done statements using Klement's progress-based interview method.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/subvisual/the-a-team --skill jobs-to-be-done-subvisual
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jobs-to-be-done
Source: https://github.com/subvisual/the-a-team/tree/main/.claude/skills/jobs-to-be-done
Command: npx skills add https://github.com/subvisual/the-a-team --skill jobs-to-be-done-subvisual

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product teams routinely confuse tasks, features, and personas with real customer jobs, producing JTBD statements that cannot guide prioritization. This Skill runs a structured interview that separates genuine customer progress from solution-speak and stamps each job with an honest confidence level. ## Core Features & Use Cases - CREATE (grill mode): Runs Klement's one-question-at-a-time interview covering push, pull, anxiety, inertia, and an altitude ladder to draft a gate-checked job statement. - REVIEW (diagnose then uplift): Scores existing JTBDs on form and grounding axes, then grills weak statements into shape. - Durable artifacts: In an A-Team target repo, writes one file per job at docs/product/jtbd/NN-<slug>.md with stable ids, source citations, and supersede pointers. - Use Case: A founder says users want a faster report export; the Skill grills the underlying struggle and produces a validated job statement naming what it replaces, stamped with a confidence level. ## Quick Start Ask the assistant to grill your idea into a real Job to be Done using the jobs-to-be-done skill.

Frequently Asked Questions about jobs-to-be-done

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a Job to be Done statement?▼

Run the grill interview: identify the push (struggling moment), pull (better life), anxiety, and inertia, then draft in the form 'Free me from [struggle], so I can [better me]' and render it as 'When [situation], I want to [progress], so I can [outcome]'. The statement must name what it replaces.

What is the difference between a job and a task in JTBD?▼

A job is the progress a customer wants in their life; a task is a visualizable action like filtering or exporting. The disqualifier test asks whether you can picture someone performing it — if yes, it is a task or solution, not a job.

How do I review existing JTBD statements for quality?▼

Score each statement on two separate axes: form (progress wording, no features, personas, or job types) and grounding (evidence basis and confidence stamp). Failed statements are then grilled into shape rather than just rejected.

Can this skill run without a human to answer questions?▼

No. The skill is an interview and escalates instead of guessing when no human is present, serializing blocking questions into docs/product/context.md under 'Awaiting answers'. Autonomous job invention is explicitly forbidden.

When should I not use the jobs-to-be-done skill?▼

Do not use it for writing PRDs, roadmaps, tickets, acceptance criteria, or implementation user stories — those consume a finished JTBD. Also skip it when the user only wants JTBD theory explained.

Where are JTBD files stored in a target repository?▼

Jobs are durable markdown files at docs/product/jtbd/NN-<slug>.md with frontmatter for id, slug, status, confidence, and sources. Ids are never reused or renumbered, and reshaped jobs become new files that supersede the old ones.