launch helps an agent plan a launch that builds over time. It checks whether the product is Simple, Lovable and Complete, structures channels with the ORB framework, and walks through five phases from internal testing to full launch.
Two references cover turning merged code into changelog and announcements, and a QA list for site launches and migrations.
What You Get
- A readiness check against Simple, Lovable and Complete before any launch mechanics
- A channel plan split into owned, rented and borrowed channels
- A five-phase plan from internal launch to general availability
- A Product Hunt plan for before, during and after launch day
- Pre-launch, launch-day and post-launch checklists plus a rule for how loudly to announce each update
Common Use Cases
- Planning the first public launch of a SaaS product
- Deciding how much marketing a new integration deserves
- Preparing a Product Hunt launch day
- Writing a weekly changelog and announcement drafts from merged work
- Running a QA pass on a redesigned or migrated site
What Makes It Unique
It puts a readiness gate before the launch phases, naming the two failure modes of hiding the product for too long and never shipping, and it treats launching as a repeating habit with a matrix for major, medium and minor updates. A reference turns merged code into customer-facing changes, and another covers site launch QA.
Under The Hood
The SKILL.md and two references are loaded as context. It ships no scripts. The agent reads the product marketing context file in your project when it exists. The shipped-changes reference tells the agent to read the repository history with git log and changed files to draft the week’s changelog, so it runs read-only git commands and reads your source files when you ask for that. The site QA reference is a checklist of things to verify on a live site. Output is written plans, checklists and drafts.