Menu

Individual skill

launch-window-planner

0upvotes

Use when the user asks to "pick a launch date", "plan the launch window", or "set the embargo and lift time"; produces a candidate-window comparison table (conflict / tailwind / risk per window) built from industry-event cycles and the competitor launch calendar, a launch-week vs rolling-release format call, store-review buffer padding (labeled Estimated), and an embargo window definition (lift moment + timezone) submitted to the launch registry as a candidate. Not for judging the cultural moment itself — use trend-spotter; not for launch-day execution — use launch-day-conductor. 发布择时/发布窗口/竞品日历/禁运期窗口/审核缓冲

launch/research/launch-window-planner/SKILL.md

Read pinned source

Source commit 8be02f1f0b18253bd5f2b85f858278f042637b9a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
3,138
Repository last updated
Nov 12, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Declared tags are partial or unavailable.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Launch Window Planner

Picks **when** to launch — the timing lever of the RAMP loop Research phase. It scans industry-event and conference cycles, maps the competitor launch calendar, pads for store-review latency, chooses a launch-week vs rolling format, and defines the embargo window (lift moment + timezone). It feeds the RAMP-`R` timing sub-item ("timing window chosen deliberately — event cycles, competitor calendar, review-latency buffers") and the RAMP-`M` embargo-coordination sub-item ("embargo & partner commitments coordinated against one authoritative date/stage") per [ramp-benchmark.md](../../../references/ramp-benchmark.md). It works one lever — timing — and hands off.

The window this skill recommends is a *proposal*, not the record: date, stage, and embargo facts become authoritative only when [launch-registry](../../../protocol/launch-registry/SKILL.md) records them. This skill submits candidates and never writes the registry directly.

**Scope guard**: this skill picks the window only. It does **not** judge whether a cultural moment or trend is worth riding (that is [trend-spotter](../../../influencer/scout/trend-spotter/SKILL.md)), run the launch day itself ([launch-day-conductor](../../mobilize/launch-day-conductor/SKILL.md) owns the hour-blocked runbook), declare the launch tier or own the risk register ([launch-tier-planner](../launch-tier-planner/SKILL.md)), write the canonical date/stage/embargo record ([launch-registry](../../../protocol/launch-registry/SKILL.md) is the sole writer of `memory/launch-registry/`), or compute the RAMP profile result ([launch-readiness-auditor](../../mobilize/launch-readiness-auditor/SKILL.md)). It works one lever and hands off.

## Quick Start

```
Pick a launch window for [product] in [quarter]. Constraints: [team availability / store-review submission / partner commitments].
```
Back to top