Product Discovery

What it does

Validating product opportunities, mapping assumptions, planning discovery sprints, and testing problem-solution fit before committing to build.

Procedure

When this skill is activated, Chalie follows these steps:

1. Use memory to recall any prior discovery work, user research findings, or stated product outcomes.
2. Use document to define the desired outcome: one measurable metric to improve, with a baseline value and target horizon.
3. Use document to build an Opportunity Solution Tree: map from the outcome to user opportunities (unmet needs/pains grounded in evidence) to solution ideas to experiments — require at least 3 distinct opportunities before converging.
4. Use document to map assumptions across four categories: desirability (users want this), viability (business value exists), feasibility (team can build it), and usability (users can successfully use it) — score each by risk and certainty.
5. Use code_eval to prioritize assumptions by risk score: high-risk and low-certainty assumptions are tested first.
6. Use search to find analogous solutions, prior user research, and behavioral evidence that either validates or challenges the top assumptions.
7. Use document to plan a 1 to 2 week discovery sprint with explicit hypotheses, daily evidence review checkpoints, and an end-state decision: proceed, pivot, or stop.
8. Use document to save the OST, assumption map, and sprint plan — then use memory to store key findings for the next planning cycle.

Version

v1 (curated)