define-jobs-to-be-done

Installation
SKILL.md

Define Jobs To Be Done

Contract

Describe progress in the customer's world. Keep implementation, product names, and preferred solutions out of the job definition. Treat a draft inferred from feedback as unconfirmed until reviewed against source evidence or with the user.

Workflow

  1. Gather concrete struggling moments, current behavior, workarounds, consequences, and switching events.
  2. Identify the job owner and the specific situation that creates demand.
  3. Write the core job: When [situation], I want to [progress], so I can [outcome].
  4. Map forces: push from the current state, pull toward change, anxiety about change, and habit or switching cost.
  5. State functional, emotional, and social dimensions only when evidence supports them.
  6. Define observable success, failure, non-goals, and the alternatives the new solution must beat.
  7. Attach evidence and uncertainties. Test durability by imagining a complete rebuild: the job should remain true.

BuildBetter Acceleration

If BuildBetter MCP is available, search organization skills first. Use customer signals, transcripts, survey responses, people context, and documents to ground each clause. Cite source IDs and distinguish direct voice from internal interpretation.

Installs
1
GitHub Stars
4
First Seen
Oct 27, 2026