job-story-mapper
Write Jobs-to-be-Done (JTBD) job stories and map customer jobs across functional, social, and emotional dimensions. Use when defining user needs, writing job stories, conducting JTBD research, or reframing features around customer outcomes. Produces a job story map with opportunity scoring, pain intensity ratings, and product opportunity analysis.
npx skills add mohitagw15856/pm-claude-skills --skill job-story-mapper --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Job Story Mapper Skill Stop writing features. Start understanding jobs. This skill translates product requirements and user interviews into precise job stories that keep the team focused on outcomes — not outputs. ## Jobs-to-be-Done Fundamentals A "job" is the progress a customer is trying to make in a given situation. People don't buy products — they hire them to get a job done. Three dimensions of every job: - **Functional job:** The practical task ("get from A to B") - **Emotional job:** How they want to feel ("feel confident I made the right choice") - **Social job:** How they want to be perceived ("look like a competent professional to my team") Great products address all three. Most roadmaps only address the functional one. --- ## Job Story Format **Template:** > When [situation/trigger], I want to [motivation/goal], so I can [expected outcome]. **Not a user story:** User stories focus on roles and features: "As a [role] I want [feature] so that [benefit]." Job stories focus on situations and motivations: "When [I'm in this specific situation] I want [this capability] so I can [achieve this outcome]." **The situation is the most important part.** "When I'm in the middle of
- Jobs-to-be-Done Fundamentals
- Job Story Format
- Mapping Process
- Step 1: Identify the main job
- Step 2: Break into job steps
- Step 3: Identify pain points per step
- Step 4: Write job stories for each pain point
- Step 5: Map to product opportunities
- Output Format
- Job Story Map — [Product/Feature Area] — [Date]
- Deeper Materials
- Scoring Rubric (0–40)
- Quality Checks
- Required Inputs
What does the job-story-mapper skill do?
Write Jobs-to-be-Done (JTBD) job stories and map customer jobs across functional, social, and emotional dimensions. Use when defining user needs, writing job stories, conducting JTBD research, or reframing features around customer outcomes. Produces a job story map with opportunity scoring, pain intensity ratings, and product opportunity analysis.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill job-story-mapper --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.