Product Launch
Turn a launch date into an evidence-gated operating plan. A launch is ready only when the promise, product path, owners, measurement, support, and reversal plan are ready at the risk level of the change.
Workflow
- Establish the launch type, launch date and timezone, audience, desired outcome, primary meaningful event, baseline, approved proof, channels, scope, dependencies, risk level, one accountable owner, backup, and decision-maker.
- Classify each input as
observed, inferred, proposed, stale, or conflicting. Record capability maturity as shipped, planned, or blocked. Claims also require source | as_of | confidence | allowed audience/surface.
- Read readiness.md. Scale the review to risk; a routine announcement does not need the controls of a migration, paid launch, regulated claim, or irreversible deployment.
- If the positioning spine or required proof is unapproved, stop the launch plan after producing only a draft messaging spine and readiness register. Do not create publish-ready channel assets or imply that copy can repair product, URL, instrumentation, security, capacity, or proof gaps. Route positioning approval to
brand-positioning.
- When the gates are clear, read sequence-assets.md. Derive every milestone from the actual launch date; assign owner, backup, dependency, review gate, and status to each deliverable.
- Immediately before external execution, obtain explicit authorization for the exact publishing, founder posting, relationship reply, outreach, spend, or live-system action. Earlier approval to plan or draft is not execution approval. Without authorization, prepare drafts and a launch-day command sheet only.
- Read measurement-postmortem.md. Verify the meaningful event and guardrails before launch, monitor launch-day decisions, then convert results into specific keep/change/stop actions.
No-Go Rule
A critical risk blocks launch until an authorized decision-maker closes it or explicitly accepts a reversible residual risk. No-go conditions include an unsupported material claim, broken core journey, missing meaningful-event instrumentation, unavailable owner or backup, unresolved security or compliance blocker, unsafe capacity, or an untested reversal path for a material live change.
Output
Return only sections that help the decision:
- diagnosis and launch classification;
- evidence, freshness, confidence, and conflicts;
- readiness register with
blocker | degrading gap | nice-to-have;
- dated sequence and asset register;
- launch-day owner/backup, reply and escalation guidance, no-go/rollback decision;
- primary outcome, guardrails, baseline, source, and review window;
- risks, assumptions, approvals, and next handoff.
Use unknown or unassigned rather than inventing a date, owner, baseline, proof, or approver. Collect and retain only the least sensitive customer, recipient, and account data required for the launch decision; keep reusable artifacts free of restricted identities and respect audience/surface permissions. Route metric design and broken attribution to startup-metrics, ongoing distribution to startup-marketing, pricing design or business-model logic to startup-strategy, and approval or execution of an already-designed operating commitment to founder-operations.
1---2name: product-launch3description: Use when preparing, sequencing, executing, measuring, or reviewing a startup product, feature, beta, market, or campaign launch; especially when readiness, proof, ownership, launch-day operations, rollback, or postmortem decisions are unclear.4---56# Product Launch78Turn a launch date into an evidence-gated operating plan. A launch is ready only when the promise, product path, owners, measurement, support, and reversal plan are ready at the risk level of the change.910## Workflow11121. Establish the launch type, launch date and timezone, audience, desired outcome, primary meaningful event, baseline, approved proof, channels, scope, dependencies, risk level, one accountable owner, backup, and decision-maker.132. Classify each input as `observed`, `inferred`, `proposed`, `stale`, or `conflicting`. Record capability maturity as `shipped`, `planned`, or `blocked`. Claims also require `source | as_of | confidence | allowed audience/surface`.143. Read [readiness.md](references/readiness.md). Scale the review to risk; a routine announcement does not need the controls of a migration, paid launch, regulated claim, or irreversible deployment.154. If the positioning spine or required proof is unapproved, stop the launch plan after producing only a draft messaging spine and readiness register. Do not create publish-ready channel assets or imply that copy can repair product, URL, instrumentation, security, capacity, or proof gaps. Route positioning approval to `brand-positioning`.165. When the gates are clear, read [sequence-assets.md](references/sequence-assets.md). Derive every milestone from the actual launch date; assign owner, backup, dependency, review gate, and status to each deliverable.176. Immediately before external execution, obtain explicit authorization for the exact publishing, founder posting, relationship reply, outreach, spend, or live-system action. Earlier approval to plan or draft is not execution approval. Without authorization, prepare drafts and a launch-day command sheet only.187. Read [measurement-postmortem.md](references/measurement-postmortem.md). Verify the meaningful event and guardrails before launch, monitor launch-day decisions, then convert results into specific keep/change/stop actions.1920## No-Go Rule2122A critical risk blocks launch until an authorized decision-maker closes it or explicitly accepts a reversible residual risk. No-go conditions include an unsupported material claim, broken core journey, missing meaningful-event instrumentation, unavailable owner or backup, unresolved security or compliance blocker, unsafe capacity, or an untested reversal path for a material live change.2324## Output2526Return only sections that help the decision:2728- diagnosis and launch classification;29- evidence, freshness, confidence, and conflicts;30- readiness register with `blocker | degrading gap | nice-to-have`;31- dated sequence and asset register;32- launch-day owner/backup, reply and escalation guidance, no-go/rollback decision;33- primary outcome, guardrails, baseline, source, and review window;34- risks, assumptions, approvals, and next handoff.3536Use `unknown` or `unassigned` rather than inventing a date, owner, baseline, proof, or approver. Collect and retain only the least sensitive customer, recipient, and account data required for the launch decision; keep reusable artifacts free of restricted identities and respect audience/surface permissions. Route metric design and broken attribution to `startup-metrics`, ongoing distribution to `startup-marketing`, pricing design or business-model logic to `startup-strategy`, and approval or execution of an already-designed operating commitment to `founder-operations`.
vaibhav0806