From tbd-skill
This skill should be used when the user invokes /tbd or asks about JTBD analysis, jobs to be done, mini-jobs, job mapping, emotional UX forces, solution epics/stories from jobs, or traceability analysis. Trigger phrases: "JTBD", "jobs to be done", "mini-jobs", "job map", "emotional forces", "push pull anxiety habit", "user stories from jobs", "traceability", "gap analysis", "coverage matrix", "Ulwick", "analyze user needs for", "TBD analysis", "decompose jobs". Handles operations: discover, decompose, map, solve, trace, resume.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tbd-skill:tbdThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A progressive methodology that moves from "why do users need this" to "what should we build" to "did we cover everything." Each tier's output feeds the next.
examples/golden-example/01-jtbd.mdexamples/golden-example/02-mini-jobs.mdexamples/golden-example/03-jobmap-observations.mdexamples/golden-example/04-solution.mdexamples/golden-example/05-traceability.mdreferences/tier1-jtbd.mdreferences/tier2-mini-jobs.mdreferences/tier3-jobmap.mdreferences/tier4-solution.mdreferences/tier5-traceability.mdA progressive methodology that moves from "why do users need this" to "what should we build" to "did we cover everything." Each tier's output feeds the next.
| Tier | Name | Input → Output | What's Unique Here |
|---|---|---|---|
| 1 | JTBD | Product description → Job statements | Solution-agnostic; bold the motivation |
| 2 | Mini-Jobs | JTBDs → Sub-jobs with alternatives (DAG) | 25% must have alt paths; a-suffix convention |
| 3 | Job Map | Mini-jobs → Cross-cutting patterns + emotional landscape | Ulwick 8 steps × 4 emotional forces (Push/Pull/Anxiety/Habit); output is synthesized observations, not raw matrix |
| 4 | Solution | Patterns + mini-jobs → Epics + Stories | Regroup by solution concern, NOT by JTBD; every story carries emotional force tag + trace |
| 5 | Traceability | All tiers → Coverage matrices + gap analysis | 5 automated checks (5A-5E); gaps framed as opportunities |
Announce on activation: "Running TBD analysis — 5-tier JTBD methodology."
| Keywords | Op | Reference | Prereqs |
|---|---|---|---|
| "JTBD", "jobs to be done", "analyze [product]", "start TBD" | discover | references/tier1-jtbd.md | None |
| "mini-jobs", "decompose", "break down", "alternatives" | decompose | references/tier2-mini-jobs.md | 01-jtbd.md |
| "job map", "Ulwick", "emotional forces", "map the jobs" | map | references/tier3-jobmap.md | 02-mini-jobs.md |
| "solution", "epics", "user stories", "regroup" | solve | references/tier4-solution.md | 03-jobmap-observations.md |
| "traceability", "coverage", "gap analysis", "close the loop" | trace | references/tier5-traceability.md | 04-solution.md |
| "continue", "resume", "next tier" | resume | Auto-detect highest NN-*.md file, load next tier | |
| "full TBD", "run all tiers" | full | All refs sequentially; still pause at checkpoints | |
| "show example", "golden example" | example | Load specific tier from examples/golden-example/ |
ls *-*.md or equivalent).NN-name.md.01-jtbd.md, 02-mini-jobs.md, 03-jobmap-observations.md, 04-solution.md, 05-traceability.mdJ1, J2; Mini-jobs = J1.1, J1.2, J1.3a (a = alternative); Epics = E1; Stories = S1.1, S1.2Tiers are sequential — each tier's input is the previous tier's output. Cannot skip tiers.
2 hard checkpoints (must pause and get user confirmation before proceeding):
Tiers 1, 4, 5 have soft checkpoints (present results, offer adjustments, but don't block).
Resume: Scan workspace for highest-numbered NN-*.md file. Read it to restore context. Load next tier's reference.
| Tier | Pass Criteria |
|---|---|
| 1 | Min 5 JTBDs, each has situation + motivation + outcome |
| 2 | Every JTBD has 2+ mini-jobs. At least 25% of JTBDs have an alternative |
| 3 | Every mini-job mapped to 4+ steps. Every mini-job has 1+ emotional force |
| 4 | Zero orphan mini-jobs (every mini-job → 1+ story). Zero orphan stories |
| 5 | This IS the quality gate — present coverage % and gap analysis |
When calibrating quality for any tier, read the corresponding file from examples/golden-example/. The example is "Team Kanban Board": 8 JTBDs, 29 mini-jobs (8 alternatives), 6 cross-cutting patterns, 11 epics, 48 stories, 61% job map step coverage. Load specific tier examples on demand — not all at once.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub lagz0ne/tbd --plugin tbd-skill