Product Discovery

Deciding what to build and why before building it — framing outcomes, mapping opportunities, defining the customer's job, testing the riskiest assumptions, and scoping an MVP. Provenance and grounding sources live in skill.json; this file is runtime routing only.

Produces: an opportunity solution tree, a job map with desired-outcome statements, an assumption test plan, or an MVP definition; the frame-outcomes intent reframes the request in place.

Core principle

Reduce the risk of building the wrong thing; do not pretend to remove it. Discovery turns a request into a measurable outcome, the opportunities under it, the customer's job, the assumptions a bet rests on, and the smallest test of value. These frameworks are scaffolding for judgment — they cut the odds of shipping on faith, but they cannot manufacture strategy or substitute for real customer evidence.