SkillAgentSearch skills...

nw-persona-jtbd-analysis

Structured persona creation and JTBD analysis methodology - persona templates, ODI job step tables, pain point mapping, success metric quantification, and multi-persona segmentation

Install / Use

npx skills add nWave-ai/nWave --skill nw-persona-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-persona-jtbd-analysis

nw-persona-jtbd-analysis scores 86/100 on our quality scale, 745th of 1,156 Content & Media skills we index.

Its SKILL.md is 4.9 KB long, well organised into 11 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-persona-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-persona-jtbd-analysis compared with similar skills

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

SkillScoreStarsUpdatedFormat
nw-persona-jtbd-analysis (this skill)by nWave-ai866172mo agoSKILL.md
siyuanby siyuan-note10047.3ktodayMCP Server
x402by browser-use100121.0k4d agoSKILL.md
algorithmic-artby anthropics100177.9k56d agoSKILL.md
pptxby anthropics100177.9k56d agoSKILL.md

Frequently asked questions

How do I install nw-persona-jtbd-analysis?
Run npx skills add nWave-ai/nWave --skill nw-persona-jtbd-analysis. The install tabs above show the steps for each supported agent.
Which AI agents does nw-persona-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-persona-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-persona-jtbd-analysis still maintained?
The repository was last updated about 2 months ago, so nw-persona-jtbd-analysis is actively maintained.

name: nw-persona-jtbd-analysis description: Structured persona creation and JTBD analysis methodology - persona templates, ODI job step tables, pain point mapping, success metric quantification, and multi-persona segmentation user-invocable: false disable-model-invocation: true

Persona and JTBD Analysis

Use during Phase 1 (GATHER) when the user lacks clear personas or the "Who" section needs rigorous definition. Provides structured alternative to ad-hoc persona descriptions.

Persona Template

For each user type, build a complete persona:

## Persona: {Name}

**Who**: {Role description -- one sentence capturing relationship to product}
**Demographics**:
- {Characteristic 1: e.g., technical proficiency level}
- {Characteristic 2: e.g., frequency of interaction}
- {Characteristic 3: e.g., environment/context of use}
- {Characteristic 4: e.g., primary motivation}

**Jobs-to-be-Done**: (see Job Step Table below)

**Pain Points**:
- {Pain 1} -- maps to Job Step: {step name}
- {Pain 2} -- maps to Job Step: {step name}

**Success Metrics**:
- {Quantified outcome 1: e.g., "Task completed in < 2 minutes"}
- {Quantified outcome 2: e.g., "Zero manual configuration steps"}

Job Step Table

Each persona has job steps describing what they accomplish. Steps follow ODI format.

| Job Step | Goal | Desired Outcome | |----------|------|-----------------| | {Verb} | {What the user wants to achieve} | Minimize {metric} of {undesirable state} |

Rules for Job Steps

  • Job Steps are always verbs: Discover, Validate, Install, Configure, Monitor, Recover
  • Goals describe what the user wants, not what the system does
  • Desired Outcomes use ODI format: "Minimize [time/effort/risk/likelihood] of [undesirable state]"
  • Each step maps to a workflow point where value is created or destroyed

Example Job Step Table

| Job Step | Goal | Desired Outcome | |----------|------|-----------------| | Discover | Find the right tool for the task | Minimize time to evaluate fit | | Install | Get the tool running locally | Minimize steps to working state | | Configure | Adapt to local environment | Minimize likelihood of misconfiguration | | Verify | Confirm correct installation | Minimize uncertainty about readiness | | Start | Begin productive work | Minimize time from install to first output |

Pain Point Mapping

Every pain point maps to a specific job step. Pain points without a corresponding step indicate either a missing step or irrelevant pain point.

Pain Point: "I don't know if the tool supports my OS"
  -> Job Step: Discover
  -> Desired Outcome: Minimize uncertainty about compatibility

Pain Point: "Installation fails silently with no error message"
  -> Job Step: Install
  -> Desired Outcome: Minimize time to diagnose installation failures

Prioritize: pain points on high-frequency job steps deserve attention first.

Success Metric Quantification

Every success metric needs a number or threshold. Qualitative metrics ("easy to use") are not actionable.

| Qualitative | Quantified | |-------------|-----------| | "Easy to install" | "Install completed in < 2 minutes with zero manual steps" | | "Fast startup" | "First productive output within 30 seconds of launch" | | "Reliable" | "Zero silent failures; all errors produce actionable messages" | | "Intuitive" | "New user completes core task without reading documentation" |

Multi-Persona Segmentation

Different users have fundamentally different jobs even when using the same product. Segment by relationship to the product.

Common axes: Frequency (first-time vs returning vs power user) | Role (end user vs admin vs developer) | Context (individual vs team vs CI/CD) | Motivation (exploration vs production vs evaluation)

Example: Same Product, Different Jobs

| Persona | Primary Job | Key Difference | |---------|-------------|----------------| | Explorer | Evaluate the tool quickly | Needs fast time-to-value, minimal commitment | | Returner | Resume work after absence | Needs state preservation, quick re-orientation | | Deployer | Install for a team | Needs configuration management, multi-user setup | | Automator | Integrate into CI/CD pipeline | Needs scriptability, headless operation, exit codes |

Each persona gets their own Job Step table because workflows differ. Do not merge personas -- JTBD analysis value comes from surfacing differences.

Integration with Story Crafting

After completing persona analysis, feed results into LeanUX user story template:

  1. Persona Who -> populated from persona template
  2. Persona Pain Points -> inform story Problem section
  3. Job Step Desired Outcomes -> inform AC (ODI outcomes translate to testable criteria)
  4. Success Metrics -> inform NFR requirements in handoff package

Cross-reference: use bdd-requirements skill for Example Mapping once personas established. Use jtbd-workflow-selection skill to determine workflow for resulting stories.

Related Skills

View on GitHub
GitHub Stars617
CategoryContent
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