Jobs To Be Done Thinking

Jobs To Be Done Thinking is an AI Engineering skill for Claude Code, published by tjboudreaux in cc-thinking-skills.

969 stars133 forkson tjboudreaux/cc-thinking-skillsAdded 2026/08/21+1% in starsRepository updated 2026/08/07

agent-skillsai-toolsanthropicclaudeclaude-codecritical-thinkingdecision-makingfirst-principlesmental-modelsproblem-solvingsystems-thinking

Install in seconds

Install Jobs To Be Done Thinking

Copy Jobs To Be Done Thinking into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/tjboudreaux/cc-thinking-skills/tree/main/skills/thinking-jobs-to-be-done ~/.claude/skills/thinking-jobs-to-be-done

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/tjboudreaux/cc-thinking-skills.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/thinking-jobs-to-be-done/SKILL.md in tjboudreaux/cc-thinking-skills
Installs to: ~/.claude/skills/thinking-jobs-to-be-done
Collection: One of 25 skills cataloged from this repository
Category: AI Engineering — 2451 skills

What Jobs To Be Done Thinking does

Jobs To Be Done Thinking helps decide what to build, cut, or reposition by framing the user's circumstance, desired progress, and competing workarounds. It is used when adoption is unclear or a shipped feature is underperforming.

Jobs To Be Done Thinking is cataloged under AI Engineering on DirSkills. Jobs To Be Done Thinking comes from a repository tagged agent-skills, ai-tools, anthropic, claude and claude-code.

Documentation

README

Excerpt

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

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Jobs To Be Done Thinking

What else does tjboudreaux publish alongside Jobs To Be Done Thinking?
Jobs To Be Done Thinking is one of 25 skills that DirSkills catalogs from tjboudreaux/cc-thinking-skills, the repository it ships in. Its siblings there include Bounded Rationality, Circle Of Competence and Effectuation. Each one is a separate skill with its own page in this directory, installs the same way Jobs To Be Done Thinking does, and is maintained by tjboudreaux in that same repository. The rest of the collection is listed on the tjboudreaux/cc-thinking-skills page.
How does Jobs To Be Done Thinking compare to other AI Engineering skills?
Jobs To Be Done Thinking ranks #1394 by stars among the 2451 AI Engineering skills in this catalog. The most-starred ones next to it are Architecture Decision Records, AI-First Engineering and Agentic OS. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Jobs To Be Done Thinking against them. Open each page to compare what they document and how they install.