| name | idea2product-p9-build-release |
| description | Drive engineering execution, verification, acceptance results, launch or GTM checklist, release decision, pre-release security review, and Release Gate preparation using disciplined build and review practices. Use when the user explicitly asks for idea2product-P9-build-release, P9, phase 9, or this step of the idea-to-product pipeline. |
idea2product-P9-build-release
Drive engineering execution, verification, acceptance results, launch or GTM
checklist, release decision, pre-release security review, and Release Gate
preparation using disciplined build and review practices.
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 P9.
Run
From the workspace root, run:
python3 .pipeline/scripts/pipeline.py run P9
On Windows, use:
python .pipeline/scripts/pipeline.py run P9
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/acceptance-results.md
Founder's Playbook Focus
Before Release Gate, run the lightweight security review named in the P9 recipe:
auth/session, API response information leakage, input validation/injection, and
dependencies with known CVEs. Agentic coding can produce code that works without
making it safe for real users.
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.
