jtbd-demand-diagnosislisted

# JTBD Demand Diagnosis (Stage 02 of 4) ## Pipeline position Stage 02 of 4: jtbd-context → **jtbd-demand-diagnosis** → jtbd-job-model → jtbd-project-decisions. ## Prerequisite Read `jtbd-analysis/01_context.md`. If the file does not exist or is incomplete — stop and ask the user to run `jtbd-context` first. ## Purpose Understand **why demand exists**: what pushes the customer away from the old way and what pulls them toward a new solution. Do **not** define the formal job statement here — that is stage 03. ## Working folder Write the output to `jtbd-analysis/02_demand_diagnosis.md`. ## Steps 1. **Read** `jtbd-analysis/01_context.md` and confirm with the user the number of distinct actors before listing them. Do not assume all five canonical roles exist. 2. **Describe each actor** with role and context. Same person can fill multiple roles ��� note the overlaps. 3. **Find the struggling moment** using the format: `When [situation/change], [actor] can no longer [old way] because [cost/risk/friction].` 4. **Map the four forces of progress:** - **Push** of the current situation (what is broken about today's way), - **Pull** of the new solution (what is attractive about the change), - **Anxiety** about the new solution (what scares the customer about switching), - **Habit** of current behavior (what keeps them stuck in the old way). None of the four can be empty. If you have no signal in materials — write "no signal" with one-line reason. 5. **Identify h