Structured framework for uncovering customer jobs, pains, and gains to validate product ideas and improve messaging.
Create detailed user stories, acceptance criteria, and feature specs
Example: Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example: Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example: Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example: Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Submit your Claude Code skill and start earning
epx add deanpeters/product-manager-skills --skill jobs-to-be-doneCompatible with
Supported agents
Breaks customer needs into three categories: functional jobs (tasks to complete), social jobs (how they want to be perceived), and emotional jobs (emotional states they seek or avoid)
Identifies four pain types: challenges blocking progress, costliness in time/money/effort, common mistakes, and unresolved problems current solutions don't address
Surfaces four gain type
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionjobs-to-be-doneExecute the skills CLI command in your project's root directory to begin installation:
epx add deanpeters/product-manager-skills --skill jobs-to-be-doneFetches jobs-to-be-done from deanpeters/product-manager-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/jobs-to-be-done
Restart Cursor to activate jobs-to-be-done. Access via /jobs-to-be-donein your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Time estimate: 30-60 minutes to see productivity improvements
Prerequisites
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
yt-dlp
lwmxiaobei/yt-dlp-skill · Productivity · same category
framer-motion
pproenca/dot-skills · Productivity · same category
find-skills
kimyx0207/findskill · Productivity · same category
xauusd-trading
huynguyen03dev/xauusd-trading · Productivity · same category
lua
mindrally/skills · Productivity · same category
skill-installer
openai/skills · Productivity · same category
jobs-to-be-done is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added jobs-to-be-done from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: jobs-to-be-done is focused, and the summary matches what you get after install.
Useful defaults in jobs-to-be-done — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in jobs-to-be-done — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: jobs-to-be-done is the kind of skill you can hand to a new teammate without a long onboarding doc.
jobs-to-be-done has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added jobs-to-be-done from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
jobs-to-be-done fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for jobs-to-be-done matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 47