| name | launch-window-planner |
| slug | aaron-launch-window-planner |
| displayName | Launch Window Planner · 发布窗口规划 |
| summary | 发布择时/竞品日历/禁运期窗口/审核缓冲 |
| description | 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. 发布择时/发布窗口/竞品日历/禁运期窗口/审核缓冲 |
| version | 20.1.0 |
| license | Apache-2.0 |
| compatibility | Claude Code and compatible agent-skill hosts |
| homepage | https://github.com/aaron-he-zhu/aaron-marketing-skills |
| when_to_use | Use when choosing a launch date or window: scanning industry events and conference cycles, mapping the competitor launch calendar, padding for store-review latency, choosing a launch-week vs rolling format, or defining the embargo window and lift moment. The timing layer of launch research — the chosen window becomes canonical only after launch-registry records it. |
| argument-hint | <product / launch stage> [candidate dates or quarter] [tier] [constraints] |
| metadata | {"author":"aaron-he-zhu","version":"20.1.0","discipline":"launch","phase":"research","geo-relevance":"low","hermes":{"tags":["marketing","launch","research"],"category":"launch"},"openclaw":{"emoji":"🚀","homepage":"https://github.com/aaron-he-zhu/aaron-marketing-skills"}} |
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. 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 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), run the launch day itself (launch-day-conductor owns the hour-blocked runbook), declare the launch tier or own the risk register (launch-tier-planner), write the canonical date/stage/embargo record (launch-registry is the sole writer of memory/launch-registry/), or compute the RAMP profile result (launch-readiness-auditor). 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].
Map the competitor launch calendar and industry events around [candidate date] — should we move?
Define the embargo window for [launch]: lift moment, timezone, and who is committed to it.
Skill Contract
Expected output: a candidate-window comparison table (conflict / tailwind / risk per window), a launch-week vs rolling format call with rationale, store-review buffer padding (labeled Estimated), an embargo window definition (lift moment + timezone + committed parties), and the standard handoff summary.
