dbs-jtbd

Clarifies user jobs-to-be-done to align products, content, and AI prompts with real progress.

9.8k|1.1k|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/dontbesilent2025/dbskill --skill dbs-jtbd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dbs-jtbd
Source: https://github.com/dontbesilent2025/dbskill/tree/main/skills/dbs-jtbd
Command: npx skills add https://github.com/dontbesilent2025/dbskill --skill dbs-jtbd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Users often describe solutions ("write me an article", "build me a course") instead of the underlying progress they want, leading to misaligned products, content, and AI outputs. This Skill applies the Jobs to Be Done framework to uncover the real task behind a request, the forces driving switching decisions, and the observable criteria users use to judge solutions.

Core Features & Use Cases

  • Task Statement Extraction: Converts surface requests into structured JTBD statements (situation → progress → outcome) across functional, emotional, and social layers.
  • Switching Force Analysis: Identifies push, pull, anxiety, and habit forces to explain why users hire or fire solutions.
  • Prompt Rewriting for AI Collaboration: Translates vague requests into JTBD-anchored prompts with context, boundaries, deliverables, and acceptance criteria.
  • Use Case: A founder says "customers think my course is too expensive." The Skill reframes this as a task clarification problem, identifies the progress customers actually want, and outputs selection criteria plus a minimal validation action.

Quick Start

Ask the agent to use /dbs-jtbd to analyze why users choose a particular solution and rewrite your request as a JTBD-based task statement.

Frequently Asked Questions about dbs-jtbd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I use Jobs to Be Done to clarify user needs?

Start from the user's situation, identify the progress they want to make, and define the outcome they expect, using the format: when in situation X, I want progress Y, so that outcome Z. Avoid treating stated solutions or demographics as the task itself.

How to rewrite an AI prompt using the JTBD framework?

Place the task statement at the start of the prompt, then add your situation, available materials, boundaries, expected deliverable, and three checkable acceptance criteria. This lets the AI infer solutions from constraints instead of guessing from abstract labels.

What are the four switching forces in JTBD analysis?

The four forces are push (pain from the current solution), pull (promise of the new solution), anxiety (fear of switching costs or failure), and habit (attachment to the old way). Adoption requires push and pull to outweigh anxiety and habit.

When should I not use JTBD task clarification?

JTBD is not a substitute for user personas, feature lists, or a universal explanation of behavior. It only explains choices and progress within specific situations, and should not be used to fabricate interview data or reduce every task to money or efficiency.

Can JTBD analysis work with incomplete user information?

Yes. When materials are sufficient, the Skill forms a task hypothesis immediately rather than interrogating the user. It asks at most one minimal factual question, and clearly labels conclusions as assumptions pending verification when evidence is missing.