jtbd
Jobs to Be Done analysis to understand what customers really want. Use for product discovery, competitive analysis, or understanding why customers hire/fire solutions.
Best use case
jtbd is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Jobs to Be Done analysis to understand what customers really want. Use for product discovery, competitive analysis, or understanding why customers hire/fire solutions.
Teams using jtbd should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/jtbd/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How jtbd Compares
| Feature / Agent | jtbd | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Jobs to Be Done analysis to understand what customers really want. Use for product discovery, competitive analysis, or understanding why customers hire/fire solutions.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Jobs to Be Done Analysis Analyze a product, feature, or situation through the Jobs to Be Done framework to understand what customers really want. ## Instructions Identify the underlying jobs customers are trying to accomplish, including functional, emotional, and social dimensions. Consider the full context of when and why they "hire" solutions. ### Output Format **Subject**: [Product/feature/situation being analyzed] --- ## The Context **When does the job arise?** [Describe the triggering situation or circumstance] **Who has this job?** [Customer segments or personas] **How are they currently solving it?** [Existing solutions, competitors, or workarounds] --- ## Job Statement **Core Job** > When [situation], I want to [motivation], so I can [expected outcome]. --- ## Job Dimensions ### Functional Job *The practical task they're trying to complete* | Job | Importance | Current Solution | |-----|------------|-----------------| | [functional job 1] | High/Med/Low | [how they do it now] | ### Emotional Job *How they want to feel* | Feeling They Want | Feeling They Want to Avoid | |------------------|---------------------------| | [positive emotion] | [negative emotion] | ### Social Job *How they want to be perceived* | How They Want to Be Seen | By Whom | |-------------------------|---------| | [perception] | [audience] | --- ## Forces Analysis **Forces pushing toward change** | Force | Strength | |-------|----------| | Push: Frustration with current solution | [description] | | Pull: Attraction of new solution | [description] | **Forces resisting change** | Force | Strength | |-------|----------| | Anxiety: Fear about new solution | [description] | | Inertia: Comfort with current way | [description] | --- ## Compensating Behaviors *What workarounds do people use when no good solution exists?* | Workaround | Why They Do It | What It Reveals | |------------|---------------|-----------------| | [behavior] | [reason] | [insight] | --- ## Competitive Alternatives *Competition is anything that could be hired for this job* | Alternative | When It Gets Hired | Strengths | Weaknesses | |-------------|-------------------|-----------|------------| | [competitor] | [situation] | [pros] | [cons] | | [do nothing] | [situation] | [pros] | [cons] | --- ## Insights **The real job is...** [What you've learned about what customers actually want] **Current solutions fail because...** [Gaps in existing solutions] **Opportunity areas...** [Where better solutions could win] ## Guidelines - Jobs are stable; solutions change. Focus on the job, not the product. - "Do nothing" is always a competitor - Emotional and social jobs often matter more than functional ones - The circumstance matters as much as the job itself $ARGUMENTS
Related Skills
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
technical-architecture
Autonomous Staff Engineer agent that analyzes a product requirement brief, extracts non-functional requirements, and generates a comprehensive technical architecture document. Accepts an optional tech-stack-preferences.md file path. Runs end-to-end without asking questions. Use when turning product requirements into technical architecture decisions.
tdd
Use when implementing features or fixing bugs — write the test first, watch it fail, write minimal code to pass. Ensures tests verify behavior by requiring failure first.
tag-based-search
Code tagging system using @FEAT, @COMP, @TYPE tags for easy discovery and navigation. Use when adding documentation tags or searching for related code across the codebase.
SurveyMonkey Automation
Automate SurveyMonkey survey creation, response collection, collector management, and survey discovery through natural language commands
strict-user-requirements-adherence
Strictly adheres to specified user flow and game rules, making sure to follow documented features.
sre-task-refinement
Use when you have to refine subtasks into actionable plans ensuring that all corner cases are handled and we understand all the requirements.
spec-prd-creator
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
software-engineering-lead
Expert software engineering lead who translates product requirements into comprehensive engineering plans using GitHub Projects. Reviews PRDs and user stories, identifies gaps and conflicts, pushes back constructively on poor requirements, applies software engineering best practices, creates detailed technical plans with tasks and milestones, and ensures production-ready architecture. Use when translating product specs into actionable development plans, validating requirements, or designing system architecture.
skill-share
A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.
sdd-to-ralph
This skill should be used when the user wants to convert completed CCSDD specs into Ralph execution artifacts. Use when user says "bridge spec to ralph", "convert sdd to ralph", "sdd to ralph", "generate ralph from spec", "prepare spec for ralph", or wants to take a cc-sdd feature spec and run it through Ralph for autonomous implementation.
sc-workflow
Generate structured implementation workflows from PRDs and feature requirements with expert guidance. Use when planning feature implementation, breaking down PRDs, or creating development roadmaps.