| name | idea2product-p10-outcome-review |
| description | Review real outcomes after release, distinguish product-market-fit signal from launch noise, decide continue, scale, iterate, pivot, pause, or retire, and update assumptions, risks, decision log, PRD, or ADRs rather than only writing a retrospective. Use when the user explicitly asks for idea2product-P10-outcome-review, P10, phase 10, or this step of the idea-to-product pipeline. |
idea2product-P10-outcome-review
Review real outcomes after release, distinguish product-market-fit signal from
launch noise, decide continue, scale, iterate, pivot, pause, or retire, and update
assumptions, risks, decision log, PRD, or ADRs rather than only writing a retrospective.
Required Workspace
Work from the target project root when possible. If .pipeline/scripts/pipeline.py is missing, initialize the workspace first by invoking idea2product-p0-guided-flow, then run P10.
Run
From the workspace root, run:
python3 .pipeline/scripts/pipeline.py run P10
On Windows, use:
python .pipeline/scripts/pipeline.py run P10
Then follow the printed recipe exactly. The recipe separates required skills, conditional skills, optional skills, external tools, non-skill process steps, outputs, and completion commands for this phase.
Main Output
docs/40-delivery/outcome-review.md
Founder's Playbook Focus
Use the PMF instruments in the template: Sean Ellis "very disappointed" signal,
effort/pull test, and the three R's (retention, revenue, referral). Treat friends,
investor excitement, and launch spikes as weak evidence unless they predict
weeks-6-to-12 retention or repeated pull from the target segment.
Rules
- Do not skip earlier gates or approved dependencies.
- Do not invent a fake business idea for P1-P3 validation.
- If the command reports a blocker, report the blocker and the concrete missing input.
- After editing pipeline state, re-run
python3 .pipeline/scripts/pipeline.py status (or python on Windows) to confirm the workspace is consistent.
