owl-listener/jobs-to-be-done
design-research/skills/jobs-to-be-done/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add owl-listener/designer-skills jobs-to-be-doneInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 15, 2026, 5:23 AM257.2s1 file scanned
SKILL.md
- name:
- jobs-to-be-done
- description:
- 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.
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
- Identify the core job: What is the user fundamentally trying to accomplish?
- 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
- Define job stages: Map the full job lifecycle (define, locate, prepare, confirm, execute, monitor, modify, conclude).
- Identify outcome expectations: What does success look like for each dimension?
- Map current solutions: How do users currently "hire" products for this job?
- Find opportunities: Where are current solutions underserving the job?
- Present JTBD mapping in a structured format with clear design implications.
Related Skills
owl-listener/business-design
tools
VerifiedTrustedCommunity
A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.
1,535SKILL.mdUpdated Jun 12, 2026
owl-listener/interfaces-that-feel
testing
VerifiedTrustedCommunity
Apply an emotional resonance lens to any UI. Use when a design is technically correct but flat — to identify what's missing and prescribe specific changes at the copy, motion, and interaction layer.
1,535SKILL.mdUpdated Jun 12, 2026
owl-listener/test-scenario
testing
VerifiedTrustedCommunity
Generates structured usability test scenarios with realistic tasks, success criteria, and facilitation notes — ready to run with real participants or in a moderated session.
1,535SKILL.mdUpdated May 15, 2026
owl-listener/interview-script
research
VerifiedTrustedCommunity
Create a structured user interview script with warm-up, core exploration, and wrap-up sections. Use when preparing for user research interviews to ensure consistent, insightful conversations.
1,535SKILL.mdUpdated May 15, 2026