jtbd-buildinglisted

# PM - JTBD Analysis ## Agent mode (`--agent`) Supports `--agent`: runs autonomously in a subagent, drafts the artifact from existing inputs, and returns a short summary + coverage note. - **No flag** → interactive (default); if inputs are heavy, offer agent mode. - **`--agent`** → obey. First check inputs are complete. Anything missing: do NOT invent it - mark `[ASSUMED - what/why]` in the output and summary. Never hallucinate to fill a gap. - **Review required:** the artifact contains commitments - after drafting, require the user's review before finalizing; do not close decisions autonomously. --- ## What this skill does Applies Jobs-to-be-Done theory to the validated customer research and personas to produce: 1. Job Stories - When / I want to / So I can formulations per key persona 2. Forces Diagram - what pushes away from the current solution and pulls toward a new one 3. Switching logic - what triggers the decision to change, and what blocks it JTBD analysis goes deeper than persona pain points. It explains the causal mechanism behind why someone would switch - the forces operating on their decision. This is the input for design decisions in Phase 3a (Design Thinking). Run this after `pm-personas`. Personas give you who - JTBD gives you why. **Commissioned builds - two levels of job:** the commissioner (client/sponsor) has their own job - they "hire" the product at business level (earn more / spend less / reduce risk / comply / status). That is distinct from t