Skip to content

phuryn/product-engineering / app-stack/skills/embedded-agents-messages-api

embedded-agents-messages-api

Verified

Building, adding or wiring up an agent or an agent chat inside a Next.js app: embed Claude agents on the Messages API, the default way.

examples/knowledge-agent/knowledge/jtbd.md

View on GitHub
# JTBD — Jobs-to-be-Done

## Core idea

Customers do not buy products. They **hire** products to make progress on a job — a problem they want solved, a goal they want reached, or a situation they want changed. The job is stable over decades; the products people hire to do it change. Clayton Christensen's example: people hire a milkshake in the morning to make a long commute less boring and stave off hunger until lunch — competitors include bagels, bananas, and boredom itself, not other milkshakes.

## The job statement

A well-formed job statement has three parts:

> When [situation], I want to [motivation], so I can [expected outcome].

- **Situation:** the trigger — context, time, place, constraints.
- **Motivation:** the functional, emotional, and social progress sought.
- **Expected outcome:** how the customer measures success.

Example: *"When I'm stuck on a coding problem at 11pm and my team is offline, I want to get an answer fast without revealing I don't know it, so I can ship before standup tomorrow."* The functional progress (get an answer) sits alongside emotional (relief) and social (avoid looking incompetent).

## Jobs vs. features vs. needs

- **Jobs are stable.** "I need to move calories from a store to my mouth between meetings" hasn't changed in a century. The hired products (vending machines, energy bars, delivery apps) have.
- **Features serve jobs.** A feature is only valuable insofar as it helps a job get done better. Feature requests are clues about jobs, not the jobs themselves.
- **Needs are vaguer.** "I need productivity" is a need. "When my calendar is wall-to-wall, I want to catch up on email in 10-minute pockets, so I don't end the day with 200 unread" is a job.

## Forces of progress

Customers switch when the pull of a new solution and push of the current pain outweigh the anxiety of switching and the habit of the current solution. The **four forces**:

1. **Push of the current situation** — what's broken with today's solution.
2. **Pull of the new solution** — what the new option promises.
3. **Anxiety of the new solution** — risk, learning curve, lock-in fears.
4. **Habit of the current solution** — switching cost, familiarity, sunk cost.

A new product wins when forces 1 and 2 exceed forces 3 and 4. Most products focus on force 2 (features) while ignoring 3 and 4, which is why excellent products often fail to dislodge mediocre incumbents.

## How JTBD changes product decisions

- **Segmentation by job, not demographics.** Two customers in the same age and income bracket can hire your product for entirely different jobs. Group customers by job-to-be-done.
- **Competition is wider than you think.** Your real competitors are everything the customer might hire instead — including doing nothing.
- **Roadmap from outcomes, not features.** Ask "what job is hired here, and which expected outcomes are underserved?" Prioritize underserved outcomes.

## Common failure modes

- **Treating personas as jobs.** "Marketing Mary" is a persona. Her job is what she's trying to accomplish today.
- **Confusing the job with the solution.** "Use our dashboard" is not a job. "Know whether the campaign is working before the daily standup" might be.
- **Asking customers what they want.** They will tell you about today's solutions. Ask what they're trying to accomplish and what got in the way.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall