User 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.
Deciding what to build or why adoption fails. An agent skill from tjboudreaux/cc-thinking-skills.
Install Thinking Jobs To Be Done
$ npx skills add tjboudreaux/cc-thinking-skills --skill thinking-jobs-to-be-done -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tjboudreaux/cc-thinking-skills thinking-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/tjboudreaux/cc-thinking-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/thinking-jobs-to-be-done .claude/skills/thinking-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 "thinking-jobs-to-be-done" agent skill from https://github.com/tjboudreaux/cc-thinking-skills/tree/main/skills/thinking-jobs-to-be-done into .claude/skills/thinking-jobs-to-be-done/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thinking-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/tjboudreaux/cc-thinking-skills/tree/main/skills/thinking-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 tjboudreaux/cc-thinking-skills --skill thinking-jobs-to-be-done -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tjboudreaux/cc-thinking-skills thinking-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/tjboudreaux/cc-thinking-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/thinking-jobs-to-be-done .agents/skills/thinking-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 "thinking-jobs-to-be-done" agent skill from https://github.com/tjboudreaux/cc-thinking-skills/tree/main/skills/thinking-jobs-to-be-done into .agents/skills/thinking-jobs-to-be-done/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thinking-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 tjboudreaux/cc-thinking-skills --skill thinking-jobs-to-be-done -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tjboudreaux/cc-thinking-skills thinking-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/tjboudreaux/cc-thinking-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/thinking-jobs-to-be-done .cursor/skills/thinking-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 "thinking-jobs-to-be-done" agent skill from https://github.com/tjboudreaux/cc-thinking-skills/tree/main/skills/thinking-jobs-to-be-done into .cursor/skills/thinking-jobs-to-be-done/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thinking-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/tjboudreaux/cc-thinking-skills.git --path skills/thinking-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 tjboudreaux/cc-thinking-skills --skill thinking-jobs-to-be-done -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tjboudreaux/cc-thinking-skills thinking-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/tjboudreaux/cc-thinking-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/thinking-jobs-to-be-done .gemini/skills/thinking-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 "thinking-jobs-to-be-done" agent skill from https://github.com/tjboudreaux/cc-thinking-skills/tree/main/skills/thinking-jobs-to-be-done into .gemini/skills/thinking-jobs-to-be-done/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thinking-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 tjboudreaux/cc-thinking-skills thinking-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 tjboudreaux/cc-thinking-skills --skill thinking-jobs-to-be-done -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tjboudreaux/cc-thinking-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/thinking-jobs-to-be-done .github/skills/thinking-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 "thinking-jobs-to-be-done" agent skill from https://github.com/tjboudreaux/cc-thinking-skills/tree/main/skills/thinking-jobs-to-be-done into .github/skills/thinking-jobs-to-be-done/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thinking-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 tjboudreaux/cc-thinking-skills --skill thinking-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 tjboudreaux/cc-thinking-skills thinking-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/tjboudreaux/cc-thinking-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/thinking-jobs-to-be-done .opencode/skills/thinking-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 "thinking-jobs-to-be-done" agent skill from https://github.com/tjboudreaux/cc-thinking-skills/tree/main/skills/thinking-jobs-to-be-done into .opencode/skills/thinking-jobs-to-be-done/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thinking-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
thinking-jobs-to-be-done- GitHub stars
- 1.6k
- Token cost
- ~940 tokens
- SKILL.md length
- 441 words
- Files
- 1
- Skills in repo
- 26
- Repo updated
- First seen
- Licence
- MIT
At a glance
Deciding what to build or why adoption fails. An agent skill from tjboudreaux/cc-thinking-skills.
- Works in 7 steps: Name performers and circumstance. Who… → State the job, not the solution. Frame:… → Map forces and switch. From artifacts:… → …
- Tasks that involve User stories
- SKILL.md covers When to Use, When NOT to Use, Procedure and Output, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Thinking Jobs To Be Done is an agent skill from tjboudreaux/cc-thinking-skills. 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.
Its SKILL.md is about 940 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering User stories. The repository describes itself as: 28 eval-informed mental models and critical-thinking skills for Claude Code, GitHub Copilot, Codex, Cursor, and other Agent Skills-compatible tools. The licence is MIT.
When your agent uses it
- Tasks that involve User stories
Example prompts
- “/thinking-jobs-to-be-done”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Name performers and circumstance. Who hires a solution, in what trigger situation, how often, and with what stakes. Prefer primary…
- State the job, not the solution. Frame: When [circumstance], I want to [progress], so I can [outcome]. Reject solution-shaped statements…
- Map forces and switch. From artifacts: what push made the old way fail, what pull the new progress offers, what anxiety blocks switching…
- Define done and outcome metrics. How the performer knows the job is finished. List outcomes to minimize and maximize (time-to-progress…
- Score candidates against the job. For each feature/priority: which job step it serves, performer share, frequency, quality of…
- Strongest countercase. State the best case that the stated job is wrong (wrong performer, vanity metric, process-is-the-job, competition…
- Stop. Stop when one primary job statement, competing set, and outcome metrics are evidence-backed enough to change a build/position…
What it can do on your machine
Read from SKILL.md and the folder at commit 7b8fece. 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.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Thinking Jobs To Be Done loads about 940 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 441 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
The full file from tjboudreaux/cc-thinking-skills at commit 7b8fece, republished under its MIT licence (© tjboudreaux). 441 words, ~940 tokens.
Download SKILL.mdSave it as
.claude/skills/thinking-jobs-to-be-done/SKILL.md (or your agent's skills folder).- name
- thinking-jobs-to-be-done
- description
- 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.
- disable-model-invocation
- true
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
Procedure
- Name performers and circumstance. Who hires a solution, in what trigger situation, how often, and with what stakes. Prefer primary performers with daily high-stakes jobs over rare secondary ones.
- State the job, not the solution. Frame:
When [circumstance], I want to [progress], so I can [outcome]. Reject solution-shaped statements ("use Slack", "add a dashboard"). Capture functional, emotional, and social dimensions only if evidence supports them. - Map forces and switch. From artifacts: what push made the old way fail, what pull the new progress offers, what anxiety blocks switching, what habit keeps the status quo. List what they hire today—including non-software and non-consumption.
- Define done and outcome metrics. How the performer knows the job is finished. List outcomes to minimize and maximize (time-to-progress, rework, confidence, surprises). Prefer frequent, poorly served jobs over rare, adequately worked-around ones.
- Score candidates against the job. For each feature/priority: which job step it serves, performer share, frequency, quality of alternatives. Promote high-frequency underserved dimensions; demote polished work for well-served or low-stakes jobs.
- Strongest countercase. State the best case that the stated job is wrong (wrong performer, vanity metric, process-is-the-job, competition is actually non-consumption). If the countercase fits evidence better, revise the job before recommending build.
- Stop. Stop when one primary job statement, competing set, and outcome metrics are evidence-backed enough to change a build/position decision—or when artifacts cannot answer and research is the only next step.
Show full SKILL.md (65 more words)Show less
Output
Produce a JTBD decision artifact:
Job statement: When …, I want to …, so I can …
Performers: primary / secondary (frequency, stakes)
Forces: push / pull / anxiety / habit
Competition: direct | indirect | non-consumption
Outcomes: minimize […] ; maximize […]
Priority implication: build / cut / reposition — because job gap is …
Countercase checked: …
Evidence used / gaps: …Verification
- Falsify: If replacing the job statement with a feature name does not change the recommendation, you never left solution-space—rewrite the job from circumstance and progress.
- Stop: Do not keep mapping job steps once the ranking decision is stable.
- Over-application guard: Skip on pure implementation tasks and known jobs. Never fabricate user quotes or personas to fill missing evidence.
© tjboudreaux, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/thinking-jobs-to-be-done of tjboudreaux/cc-thinking-skills.
Open the folder on GitHubat commit 7b8fece
Compare with similar skills
Thinking Jobs To Be Done 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 |
|---|---|---|---|---|---|---|
| Thinking Jobs To Be Done this skilltjboudreaux/cc-thinking-skills | 1.6k | — | ~940 | Automated safety check: Pass | MIT | |
| User Story Writerdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~2.9k | Automated safety check: Pass | Custom licence | |
| Ralph Tui Create Beadssubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Agile Product Owneralirezarezvani/claude-skills | 28k | 3 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beads Rustsubsy/ralph-tui | 2.5k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| To Specbestofjs/bestofjs | 3.1k | 21 repos | ~757 | Automated safety check: Pass | MIT |
Similar skills
Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Agile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
To Spec
bestofjs/bestofjs
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Ralph Tui Create JSON
subsy/ralph-tui
Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.
More from tjboudreaux/cc-thinking-skills
All 26 skills in this repoThinking Bounded Rationality
tjboudreaux/cc-thinking-skills
A skill your agent uses when search or investigation could run forever.
Thinking Circle Of Competence
tjboudreaux/cc-thinking-skills
A skill your agent uses when a specific claim may lack grounding.
Thinking Lindy Effect
tjboudreaux/cc-thinking-skills
A skill your agent uses when longevity of a non-perishable option matters.
Thinking Via Negativa
tjboudreaux/cc-thinking-skills
A skill your agent uses when the reflex is to add a feature, layer, or process.
Thinking Cynefin
tjboudreaux/cc-thinking-skills
When the right response mode is unclear, classify the cause-effect domain first; decompose disorder.
Thinking Five Whys Plus
tjboudreaux/cc-thinking-skills
When a fault is localized and the proximate cause is known but the systemic root is not, chain evidence-linked whys with a counterfactual stop and a countermeasure.
Related
Categories
Questions about Thinking Jobs To Be Done
What does Thinking Jobs To Be Done do?
Deciding what to build or why adoption fails. An agent skill from tjboudreaux/cc-thinking-skills. Thinking Jobs To Be Done is an agent skill from tjboudreaux/cc-thinking-skills. Deciding what to build or why adoption fails.
When should I use Thinking Jobs To Be Done?
Thinking Jobs To Be Done fits situations like: tasks that involve User stories.
How do I install Thinking Jobs To Be Done in Claude Code?
Run `npx skills add tjboudreaux/cc-thinking-skills --skill thinking-jobs-to-be-done -a claude-code`. Or copy the skill folder (skills/thinking-jobs-to-be-done in tjboudreaux/cc-thinking-skills) into .claude/skills/thinking-jobs-to-be-done in your project. Claude Code loads it when a task matches its description.
How do I install Thinking Jobs To Be Done in Codex?
Run `npx skills add tjboudreaux/cc-thinking-skills --skill thinking-jobs-to-be-done -a codex`. Or copy the skill folder (skills/thinking-jobs-to-be-done in tjboudreaux/cc-thinking-skills) into .agents/skills/thinking-jobs-to-be-done in your project. Codex loads it when a task matches its description.
Can I use Thinking Jobs To Be Done 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 tjboudreaux/cc-thinking-skills --skill thinking-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/thinking-jobs-to-be-done, .gemini/skills/thinking-jobs-to-be-done, .github/skills/thinking-jobs-to-be-done and .opencode/skills/thinking-jobs-to-be-done in your project.
What does Thinking Jobs To Be Done need to run?
SKILL.md names no scripts, command-line tools or credentials: Thinking Jobs To Be Done is instructions for the agent only.
Does Thinking Jobs To Be Done access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Thinking Jobs To Be Done 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 Thinking Jobs To Be Done use?
Thinking Jobs To Be Done is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Thinking Jobs To Be Done use?
About 940 tokens (SKILL.md is roughly 3.8k 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 Thinking Jobs To Be Done?
Skills that share tags, products or a category with Thinking Jobs To Be Done: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Agile Product Owner (alirezarezvani/claude-skills, 28k stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Thinking Jobs To Be Done?
tjboudreaux (a GitHub user) maintains it in tjboudreaux/cc-thinking-skills, which has 1,613 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on August 7, 2026.
Source: tjboudreaux/cc-thinking-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.