This prompts Claude to map user motivations using the Jobs-to-Be-Done framework instead of jumping straight to features. It breaks down why people "hire" your product across functional, emotional, and social dimensions, then structures it into job statements like "When [situation], I want to [motivation], so I can [outcome]." The real value is in the full job lifecycle mapping, from define through conclude, which helps you spot where current solutions fall short. Use this when you're deciding what to build next or trying to understand why users behave a certain way. It's particularly good at reframing product decisions away from competitor feature checklists and toward actual user problems worth solving.
npx skills add https://github.com/owl-listener/designer-skills --skill jobs-to-be-done