infrasity-labs/dev-gtm-claude-skills

jobs-to-be-done

Map user Jobs-to-Be-Done with functional, emotional, and social dimensions plus outcome expectations. Use when reframing product decisions around user motivations rather than features.

First seen Jun 30, 2026

Installation

$ npx skills add infrasity-labs/dev-gtm-claude-skills --skill jobs-to-be-done

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from infrasity-labs/dev-gtm-claude-skills · top by installs.

npx skills add infrasity-labs/dev-gtm-claude-skills

Browse all from infrasity-labs/dev-gtm-claude-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 123
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,610 B
  • docs SUMMARY.md 207 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 54 installs

SKILL.md

Jobs-to-Be-Done

Map user Jobs-to-Be-Done to understand the deeper motivations behind user behavior.

Context

You are a UX researcher applying the JTBD framework for $ARGUMENTS. If the user provides files (interview data, product context), read them first.

Domain Context

  • JTBD (Clayton Christensen, Tony Ulwick): People hire products to get a job done — focus on the job, not the product.
  • Three dimensions: Functional (practical task), Emotional (how they want to feel), Social (how they want to be perceived).
  • Job statements follow the format: When [situation], I want to [motivation], so I can [expected outcome].

Instructions

  1. Identify the core job: What is the user fundamentally trying to accomplish?
  2. Map the job dimensions:

- Functional: The practical task or outcome - Emotional: The feeling they seek or want to avoid - Social: How they want to be perceived by others

  1. Define job stages: Map the full job lifecycle (define, locate, prepare, confirm, execute, monitor, modify, conclude).
  2. Identify outcome expectations: What does success look like for each dimension?
  3. Map current solutions: How do users currently "hire" products for this job?
  4. Find opportunities: Where are current solutions underserving the job?
  5. Present JTBD mapping in a structured format with clear design implications.