Agent Skills
› Owl-Listener/designer-skills
› jobs-to-be-done
jobs-to-be-done
GitHub基于JTBD框架分析用户行为背后的深层动机，涵盖功能、情感和社会维度。通过识别核心任务、映射需求阶段及当前解决方案，发现产品机会并输出结构化设计建议，辅助以用户为中心的产品决策。
Trigger Scenarios
分析用户行为动机
重构以用户目标为核心的产品策略
挖掘产品改进机会
Install
npx skills add Owl-Listener/designer-skills --skill jobs-to-be-done -g -y
SKILL.md
Frontmatter
{
"name": "jobs-to-be-done",
"description": "Map functional, emotional, and social jobs with outcome expectations. Use when reframing decisions around motivation rather than features. For who the user is, use `user-persona`."
}
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.
Version History
-
20e34c4
Current 2026-08-19 23:19
优化技能描述结构，增加使用场景和边界说明，解决技能冲突并规范引用格式。
- acc3e57 2026-07-25 05:14
