SkillAgentSearch skills...

nw-jtbd-analysis

JTBD methodology for extracting real jobs behind feature requests — job statements, abstraction layers, first-principles extraction, ODI outcome statements, and opportunity scoring

Install / Use

npx skills add nWave-ai/nWave --skill nw-jtbd-analysis

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Supported Platforms

Universal

Tags

Our assessment of nw-jtbd-analysis

nw-jtbd-analysis scores 86/100 on our quality scale, 2480th of 4,702 Development & Engineering skills we index.

Its SKILL.md is 5.2 KB long, well organised into 9 sections with 2 code examples: a solid amount of guidance for an agent.

It has 617 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so nw-jtbd-analysis is actively maintained.
  • Our last check on 2026-11-03 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

nw-jtbd-analysis compared with similar skills

All 4 of these similar skills score higher than nw-jtbd-analysis; compare them before choosing.

SkillScoreStarsUpdatedFormat
nw-jtbd-analysis (this skill)by nWave-ai866172mo agoSKILL.md
taste-skillby Leonxlnx100117.6k9d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.3ktodayCLAUDE.md
claude-howtoby luongnv8910047.4k3d agoCLAUDE.md
lobehubby lobehub10085.7ktodayMCP Server

Frequently asked questions

How do I install nw-jtbd-analysis?
Run npx skills add nWave-ai/nWave --skill nw-jtbd-analysis. The install tabs above show the steps for each supported agent.
Which AI agents does nw-jtbd-analysis work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is nw-jtbd-analysis safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is nw-jtbd-analysis still maintained?
The repository was last updated about 2 months ago, so nw-jtbd-analysis is actively maintained.

name: nw-jtbd-analysis description: JTBD methodology for extracting real jobs behind feature requests — job statements, abstraction layers, first-principles extraction, ODI outcome statements, and opportunity scoring user-invocable: false disable-model-invocation: true

JTBD Analysis

Core Principle

A job is the progress a person is trying to make in a particular circumstance. Jobs are stable over time — technology changes, jobs don't. People hire products to make progress; they fire them when they fail.

The trap: Feature requests describe a proposed solution, not the underlying job. Always extract the job first.


Job Statement Format

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

Examples (good):

  • "When I'm hosting a virtual networking event, I want to facilitate natural conversations between strangers, so I can create valuable connections that wouldn't happen otherwise."
  • "When I join an event as a participant, I want to quickly find relevant people to talk to, so I can maximize the value of my limited time."

Job Types — Extract All Three

| Type | Question | Example | |------|----------|---------| | Functional | What task is the user trying to accomplish? | Find someone with complementary expertise | | Emotional | How does the user want to feel? | Feel confident approaching strangers | | Social | How does the user want to be perceived? | Appear professional and well-connected |


Abstraction Layers — Navigate to the Real Job

Jobs usually live at strategic or physical level, not tactical.

| Layer | Question | Example | |-------|----------|---------| | Tactical | How do we improve this interaction? | Better drag-and-drop for notes | | Operational | Why does this workflow exist? | Why do we need a facilitator? | | Strategic | What decision is being pursued? | How do we reduce direction uncertainty? | | Physical | What's the irreducible function? | Input → Synthesis → Convergence |

Navigation rules:

  • Use "why?" to move up layers
  • Use "how?" to move down layers
  • Stop when further "why?" produces a life-goal answer

First-Principles Extraction — 3-Step Inversion

When a feature request is presented as a job, apply this:

  1. Identify the Activity — What visible action is the user performing?

    • e.g., "User brainstorms on a whiteboard"
  2. Reject the Activity as the Job — Does anyone wake up wanting to do this activity?

    • "Nobody wakes up wanting to brainstorm" → the job is deeper
  3. Strip to Irreducible Function — What remains if all tools and methods are removed?

    • e.g., "Reduce uncertainty via input-synthesis-convergence"

Disruption check: Is there a higher-level job that would make this entire job unnecessary?


ODI Outcome Statements — Measurable Success Criteria

Format: [Direction] + [Metric] + [Object] + [Context]

Direction: Always "Minimize" (95% of time). "Maximize" only when more is genuinely better.

Metrics priority:

  1. the time it takes to — speed/efficiency (preferred)
  2. the likelihood of — avoiding occurrences
  3. the likelihood that — avoiding results
  4. the number of — quantity reduction
  5. the effort required to — ease

Good vs bad examples:

| Bad | Problem | Good | |-----|---------|------| | "I want easy video calls" | Ambiguous + solution | "Minimize the time it takes to start a conversation with a specific person" | | "Manage my network effectively" | Vague verb + ambiguous | "Minimize the time it takes to identify who can help with a specific need" | | "Use breakout rooms to talk privately" | Solution embedded | "Minimize the likelihood of conversations being overheard by unintended parties" | | "Don't miss important people" | Negative framing | "Minimize the likelihood of failing to connect with relevant attendees" |

Forbidden words: easy, reliable, good, better, effective, efficient, manage, handle, deal with. Forbidden patterns: solution references ("using AI", "via the app"), compound statements with "and"/"or", demographics.


Opportunity Scoring

Formula: Score = Importance + Max(0, Importance - Satisfaction)

Where Importance and Satisfaction are surveyed 1-10.

| Score | Interpretation | |-------|---------------| | > 12 | Under-served — high opportunity | | 10-12 | Appropriately served — maintain | | < 10 | Over-served — do not invest |

Output format per opportunity:

| Outcome | Importance | Satisfaction | Score | Status |
|---------|------------|--------------|-------|--------|
| Minimize time to find relevant attendees | 9.2 | 4.1 | 14.3 | Under-served |

DIVERGE Output for JTBD Phase

Produce docs/feature/{feature-id}/diverge/job-analysis.md with:

  1. Raw request — verbatim feature/problem statement received
  2. Job extraction — 5 Why chain from tactical to physical/strategic level
  3. Job statements — functional (required) + emotional + social (if identifiable)
  4. Disruption check — Is there a higher-level job this entire job is serving?
  5. Outcome statements — 3-6 measurable ODI-format statements
  6. Opportunity candidates — Which outcomes appear most under-served?

Gate: Job must be at strategic or physical abstraction level. Tactical-level jobs are not acceptable input for brainstorming — elevate first.

Related Skills

View on GitHub
GitHub Stars617
CategoryDevelopment
Updated2mo ago
Forks63

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions