dragoon0x/everything-design-taste

jobs-to-be-done-practice

Practical JTBD interview techniques, job mapping, and translating jobs into features.

First seen Jul 18, 2026

Installation

$ npx skills add dragoon0x/everything-design-taste --skill jobs-to-be-done-practice

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from dragoon0x/everything-design-taste · top by installs.

npx skills add dragoon0x/everything-design-taste

Browse all from dragoon0x/everything-design-taste

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 11
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,152 B
  • docs SUMMARY.md 117 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Jobs To Be Done Practice

The Interview

Timeline Interview Format

Walk backwards from the moment of purchase/adoption:

  1. What triggered you to look for a solution?
  2. What were you using before?
  3. What didn't work about the previous solution?
  4. How did you find alternatives?
  5. What made you choose this option?
  6. What almost stopped you from switching?

Key Questions

  • 'Tell me about the last time you...' (gets specific, recent stories)
  • 'What were you hoping would happen?' (reveals desired outcome)
  • 'What was the hardest part?' (reveals pain points)
  • 'What would you do if this didn't exist?' (reveals the real competition)

Job Mapping

Break down the main job into steps:

  1. Define what needs to be done
  2. Locate inputs needed
  3. Prepare to do the job
  4. Confirm readiness
  5. Execute the job
  6. Monitor progress
  7. Modify as needed
  8. Conclude

Each step has potential for innovation (where is it hard, slow, or error-prone?)