Product Manager Toolkit
borghei/Claude-Skills
Product manager toolkit covering RICE prioritization, customer interview analysis, PRDs, and discovery frameworks.
Structures customer jobs, pains and gains in a Jobs-to-be-Done format, to clarify unmet needs, reposition a product or sharpen discovery.
Install Jobs To Be Done Analysis
$ npx skills add deanpeters/Product-Manager-Skills --skill jobs-to-be-done -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install deanpeters/Product-Manager-Skills jobs-to-be-done --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/jobs-to-be-done .claude/skills/jobs-to-be-done && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "jobs-to-be-done" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/jobs-to-be-done into .claude/skills/jobs-to-be-done/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jobs-to-be-done", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/jobs-to-be-doneType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add deanpeters/Product-Manager-Skills --skill jobs-to-be-done -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install deanpeters/Product-Manager-Skills jobs-to-be-done --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/jobs-to-be-done .agents/skills/jobs-to-be-done && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "jobs-to-be-done" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/jobs-to-be-done into .agents/skills/jobs-to-be-done/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jobs-to-be-done", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add deanpeters/Product-Manager-Skills --skill jobs-to-be-done -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install deanpeters/Product-Manager-Skills jobs-to-be-done --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/jobs-to-be-done .cursor/skills/jobs-to-be-done && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "jobs-to-be-done" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/jobs-to-be-done into .cursor/skills/jobs-to-be-done/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jobs-to-be-done", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/deanpeters/Product-Manager-Skills.git --path skills/jobs-to-be-done--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add deanpeters/Product-Manager-Skills --skill jobs-to-be-done -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install deanpeters/Product-Manager-Skills jobs-to-be-done --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/jobs-to-be-done .gemini/skills/jobs-to-be-done && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "jobs-to-be-done" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/jobs-to-be-done into .gemini/skills/jobs-to-be-done/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jobs-to-be-done", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install deanpeters/Product-Manager-Skills jobs-to-be-doneInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add deanpeters/Product-Manager-Skills --skill jobs-to-be-done -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/jobs-to-be-done .github/skills/jobs-to-be-done && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "jobs-to-be-done" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/jobs-to-be-done into .github/skills/jobs-to-be-done/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jobs-to-be-done", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add deanpeters/Product-Manager-Skills --skill jobs-to-be-done -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install deanpeters/Product-Manager-Skills jobs-to-be-done --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/jobs-to-be-done .opencode/skills/jobs-to-be-done && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "jobs-to-be-done" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/jobs-to-be-done into .opencode/skills/jobs-to-be-done/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jobs-to-be-done", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
jobs-to-be-done- GitHub stars
- 7.2k
- Used in
- 1 other repo
- Token cost
- ~3.5k tokens
- SKILL.md length
- 1,434 words
- Files
- 4
- Skills in repo
- 75
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Structures customer jobs, pains and gains in a Jobs-to-be-Done format, to clarify unmet needs, reposition a product or sharpen discovery.
- Works in 5 steps: Define the Context → Explore Customer Jobs → Identify Pains → …
- Clarifying unmet needs before building a feature
- SKILL.md covers Purpose, Input, Key Concepts and Application, plus 3 more sections
- Reaches github.com
What it does
A Jobs-to-be-Done breakdown, influenced by Clayton Christensen and the Value Proposition Canvas, sorts customer findings into three groups. Customer jobs are functional, social or emotional; pains include challenges, costliness, common mistakes and unresolved problems; gains include expectations, savings, adoption factors and life improvement. The skill treats this as a lens rather than a survey and keeps the job separate from the solution.
You can pass a customer segment, interview notes, support tickets or research to mine, along with the situation or trigger you care about, and anything included with the request counts as answers already given. If you arrive with nothing, the agent asks who the customer is and what progress they are trying to make. A template and two worked examples, one of them industrial, ship with the skill.
When your agent uses it
- Clarifying unmet needs before building a feature
- Repositioning a product around customer motivations
- Mining interview notes for jobs, pains and gains
- Improving discovery questions and product messaging
Example prompts
- “Do a jobs-to-be-done analysis for freelance designers who use our invoicing app, based on these interview notes.”
- “What functional, social and emotional jobs do warehouse managers hire our scanning software for?”
- “Use the support tickets in ./tickets.csv to list the pains and gains of our trial users.”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Define the Context
- Explore Customer Jobs
- Identify Pains
- Uncover Gains
- Prioritize and Validate
What it can do on your machine
Read from SKILL.md and the folder at commit 1b5a524. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Jobs To Be Done Analysis loads about 3.5k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 1,434 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,434 words (~3,477 tokens).
“Systematically explore what customers are trying to accomplish (functional, social, emotional jobs), the pains they experience, and the gains they seek. Use this framework to uncover unmet needs, validate product ideas, and ensure your solution addresses real motivations—not just surface-level…”
- name
- jobs-to-be-done
- argument-hint
- [customer segment or product]
- intent
- Systematically explore what customers are trying to accomplish (functional, social, emotional jobs), the pains they experience, and the gains they seek. Use…
- type
- component
- theme
- discovery-research
- best_for
- Clarifying what customers actually hire your product to do, Repositioning a product around unmet needs rather than features, Turning fuzzy user feedback into…
- scenarios
- Customers keep asking for features that don't fit our roadmap — what job are they hiring us for?, We're repositioning and need to understand the unmet needs…
- estimated_time
- 20-30 min
Files
SKILL.md and 3 other files in skills/jobs-to-be-done of deanpeters/Product-Manager-Skills.
- SKILL.md
- examples/sample-industrial.md
- examples/sample.md
- template.md
Open the folder on GitHubat commit 1b5a524
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in deanpeters/Product-Manager-Skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Jobs To Be Done Analysis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Jobs To Be Done Analysis this skilldeanpeters/Product-Manager-Skills | 7.2k | 1 repos | ~3.5k | Automated safety check: Pass | Custom licence | |
| Product Manager Toolkitborghei/Claude-Skills | 891 | — | ~5.8k | Automated safety check: Pass | MIT | |
| Opportunity Solution Treeavelikiy/great_cto | 103 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Gingiris User InterviewGingiris-1031/Competitor-analysis-tool | 110 | — | ~1.2k | Automated safety check: Pass | None | |
| Building ProductGTM-Strategist/gtm-strategist-skills | 264 | — | ~5.8k | Automated safety check: Pass | MIT | |
| Osterwalder Canvas Architectsickn33/agentic-awesome-skills | 47k | 1 repos | ~647 | Automated safety check: Pass | MIT |
Similar skills
Opportunity Solution Tree
avelikiy/great_cto
Builds an Opportunity Solution Tree that links one measurable outcome to customer opportunities, candidate solutions and experiments.
Gingiris User Interview
Gingiris-1031/Competitor-analysis-tool
🇺🇸 User Interview & Cold-Start Operations Playbook — Battle-tested framework from HeyGen's 937 interviews to PMF.
Building Product
GTM-Strategist/gtm-strategist-skills
A skill your agent uses when the user needs to define their MVP, create a product roadmap, plan metrics and tracking, refine their value proposition with JTBD, or run usability tests.
Osterwalder Canvas Architect
sickn33/agentic-awesome-skills
Iterative consultant agent for building and validating logically consistent 9-block Business Model Canvases.
Icp Builder
OpenClaudia/openclaudia-skills
Define ideal customer profiles and buyer personas with structured frameworks.
More from deanpeters/Product-Manager-Skills
All 75 skills in this repoUser Story Writer
deanpeters/Product-Manager-Skills
Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.
TAM SAM SOM Calculator
deanpeters/Product-Manager-Skills
Calculates total, serviceable available and serviceable obtainable market size for a product idea with explicit assumptions, methods and caveats.
Organic Growth Path Advisor
deanpeters/Product-Manager-Skills
Diagnoses where a growth constraint lives and recommends one organic growth path from the McKinsey Growth Pyramid to test first.
Prioritization Framework Advisor
deanpeters/Product-Manager-Skills
Picks the right prioritization framework for your stage and context instead of defaulting to RICE or ICE out of habit.
Strategic Roadmap Planning
deanpeters/Product-Manager-Skills
Sequences prioritization, epic definition, and stakeholder alignment into a release plan that ladders up to business outcomes.
User Story Mapping
deanpeters/Product-Manager-Skills
Lays out a user journey as activities, steps, and tasks on a two-dimensional map that then informs backlog slicing.
Related
Categories
Questions about Jobs To Be Done Analysis
What does Jobs To Be Done Analysis do?
Structures customer jobs, pains and gains in a Jobs-to-be-Done format, to clarify unmet needs, reposition a product or sharpen discovery. A Jobs-to-be-Done breakdown, influenced by Clayton Christensen and the Value Proposition Canvas, sorts customer findings into three groups. Customer jobs are functional, social or emotional; pains include challenges, costliness, common mistakes and unresolved problems; gains include expectations, savings, adoption factors and life improvement.
When should I use Jobs To Be Done Analysis?
Jobs To Be Done Analysis fits situations like: clarifying unmet needs before building a feature; repositioning a product around customer motivations; mining interview notes for jobs, pains and gains; improving discovery questions and product messaging.
How do I install Jobs To Be Done Analysis in Claude Code?
Run `npx skills add deanpeters/Product-Manager-Skills --skill jobs-to-be-done -a claude-code`. Or copy the skill folder (skills/jobs-to-be-done in deanpeters/Product-Manager-Skills) into .claude/skills/jobs-to-be-done in your project. Claude Code loads it when a task matches its description.
How do I install Jobs To Be Done Analysis in Codex?
Run `npx skills add deanpeters/Product-Manager-Skills --skill jobs-to-be-done -a codex`. Or copy the skill folder (skills/jobs-to-be-done in deanpeters/Product-Manager-Skills) into .agents/skills/jobs-to-be-done in your project. Codex loads it when a task matches its description.
Can I use Jobs To Be Done Analysis in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add deanpeters/Product-Manager-Skills --skill jobs-to-be-done -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jobs-to-be-done, .gemini/skills/jobs-to-be-done, .github/skills/jobs-to-be-done and .opencode/skills/jobs-to-be-done in your project.
What does Jobs To Be Done Analysis need to run?
SKILL.md names no scripts, command-line tools or credentials: Jobs To Be Done Analysis is instructions for the agent only.
Does Jobs To Be Done Analysis access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Jobs To Be Done Analysis safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Jobs To Be Done Analysis use?
Jobs To Be Done Analysis has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Jobs To Be Done Analysis use?
About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Jobs To Be Done Analysis?
Skills that share tags, products or a category with Jobs To Be Done Analysis: Product Manager Toolkit (borghei/Claude-Skills, 891 stars), Opportunity Solution Tree (avelikiy/great_cto, 103 stars), Gingiris User Interview (Gingiris-1031/Competitor-analysis-tool, 110 stars) and Building Product (GTM-Strategist/gtm-strategist-skills, 264 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Jobs To Be Done Analysis?
deanpeters (a GitHub user) maintains it in deanpeters/Product-Manager-Skills, which has 7,224 GitHub stars. The repository holds 75 skills in this directory. The repository was last updated on September 1, 2026.
Source: deanpeters/Product-Manager-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.