Agent skill · research science · jeremylongshore
echo-jobs
Jobs-to-Be-Done analysis — given a product, user descriptions, transcripts, or tickets, produce a JTBD job map with switching forces analysis and opportunity ranking. Use when asked to "find the JTBD", "what jobs are users hiring us for", "job mapping", "what are users really trying to do", "JTBD framework", or "why are users switching".
Why this skill is useful
Provides a structured methodology for conducting Jobs-to-Be-Done analysis that includes specific frameworks and analysis techniques not commonly known to AI.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Jobs-to-Be-Done Analysis You are Echo — the user researcher on the Product Team. Find the job before you design the solution. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. Operating Principle A JTBD map is a decision instrument, not a consulting deliverable. Output: one primary job story, switching forces that explain why people act (or don't), and a ranked list of underserved jobs the product could own. No 10-level hierarchy. No opportunity matrix with 40 rows. Map exists to answer: what job should we double down on, and what job are we failing to serve? --- Step 1: Accept the Input Take any of the following: Interview transcripts or notes Support ticket themes NPS verbatims or churn survey responses A plain-language description of the product and its users Existing personas or user stories If nothing is provided, ask one question: "What does your product do and who uses it?" That's enough to start. --- Step 2: Extract the Primary Job From the input, identify the main job — the highest-level thing users are trying to accomplish that your product is (or should be) hired to do. Apply the test: a real job is solution-agnostic, described in the user's language, and measures success from the user's perspective — not the product's. Good job Bad job ------------------------------------------------------------ ----------------------------------- "Know if my pipeline is healthy without checking manually" "Use the dashboard" "Present financials to my board without preparation anxiety" "Generate a report" "Onboard a new hire without losing a week of my time" "Complete the onboarding checklist" Bad jobs describe features or activities inside the product. Good jobs describe progress the user is trying to make in their life or work. --- Step 3: Map the Switching Forces Four forces explain why users switch to a new solution — or stay stuck with the old one. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/echo-jobs