UX Jtbd

What it does

When your agent uses it

• The user needs to understand why customers hire
• Discover unmet needs
• Write job stories
• Reframe product strategy around customer outcomes — even if they say why do customers buy this

Example prompts

• “why do customers buy this”
• “what need does this serve”
• “customers aren”
• “/ux-jtbd”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

1. 1Identify the situation/trigger: What circumstance creates the need?
2. 2Uncover the job: What progress is the customer trying to make?
3. 3Map all three dimensions: Functional + emotional + social
4. 4Identify current "hires": What do they currently use to do this job?
5. 5Find forces of progress: Push (dissatisfaction with current) + Pull (attraction of new) vs Anxiety (fear of new) + Habit (comfort of…
6. 6Discover unmet needs: Where do current solutions fall short?

What it can do on your machine

Read from SKILL.md and the folder at commit 4e7f4f8. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

UX Jtbd loads about 1.3k tokens when it runs, and up to ~4.2k if it reads all its reference files. Until then it costs about 110 tokens; SKILL.md has 449 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~110

When it runs · the whole SKILL.md, loaded when a task matches

~1.3k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~4.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from asgard-ai-platform/skills at commit 4e7f4f8, republished under its MIT licence (© asgard-ai-platform). 449 words, ~1,259 tokens.

name

ux-jtbd

description

Apply Jobs to Be Done (JTBD) framework to understand customer motivation through functional, emotional, and social jobs. Use this skill when the user needs to understand why customers hire or fire a product, discover unmet needs, write job stories, or reframe product strategy around customer outcomes — even if they say 'why do customers buy this', 'what need does this serve', or 'customers aren't using our product as intended'.

metadata.category

WP-21 設計/資訊/傳播/公衛

metadata.tags

product, jtbd, jobs-to-be-done, customer-insight

IRON LAW: The Job Is About the Customer's Progress, Not Your Product

"Help me manage my tasks" is a job. "Use our task management app" is not.
The job exists independently of any solution. Your product is ONE way
to fulfill the job — customers can "hire" a spreadsheet, a notebook,
or a whiteboard for the same job.

Define jobs from the CUSTOMER's perspective, never from the product's.

When [situation/trigger],
I want to [motivation/job],
so I can [expected outcome].

PUSH (away from current) + PULL (toward new) > ANXIETY (about new) + HABIT (of current)
= Customer switches

# JTBD Analysis: {Product/Category}

## The Job
When [situation], I want to [job], so I can [outcome].

## Three Dimensions
- Functional: {practical need}
- Emotional: {desired feeling}
- Social: {desired perception}

## Current Hires (Competition)
| Solution | What Job It Does | Where It Falls Short |
|----------|-----------------|---------------------|
| {product/workaround} | {what need it serves} | {unmet need} |

## Forces of Progress
- Push: {what's driving them away from current solutions}
- Pull: {what attracts them to new solutions}
- Anxiety: {what holds them back from switching}
- Habit: {what keeps them using current solutions}

## Unmet Needs & Opportunities
1. {unmet need} → {opportunity}

© asgard-ai-platform, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in ux-jtbd of asgard-ai-platform/skills.

• SKILL.md
• examples/sample_scenario.md
• references/switch-interviews.md

Open the folder on GitHubat commit 4e7f4f8