Thinking Jobs To Be Done
Deciding what to build or why adoption fails.
Install
npx skills add tjboudreaux/cc-thinking-skills --skill thinking-jobs-to-be-done -g -a claude-code -y- Repository
- tjboudreaux/cc-thinking-skills1.7k
- Category
- Engineering
- Updated
- 3mo ago
- License
- MIT
- Context cost
- Lightabout 878 tokens
- Runs scripts
- No, instructions only
What it does
Deciding what to build or why adoption fails. Recover the progress users hire a solution for under a circumstance, then rank by outcome and competing workarounds.
Jobs to Be Done
Core rule: users hire solutions for progress in a situation. Prioritize the job, forces, outcome, and competing workaround, not the feature list.
When to Use
- Choosing what to build, cut, or prioritize when user need is unclear
- Explaining low adoption of a shipped feature
- Mapping competition beyond same-category products (email, spreadsheets, manual work, non-consumption)
- Positioning or research when the progress sought is contested
Requires at least one evidence source: PRD/spec, tickets, support/sales notes, analytics/logs, or current product behavior. If none exist, name the research gap; do not invent quotes.
When NOT to Use
- Pure execution once the job is known (bug fix, schema, CI, performance), implement, do not rediscover the job
- Retro-justifying a decision already locked, framework theater
- Infrastructure/internal work with no end-user progress decision
- When the open question is only how to implement a settled job
