Menu

Individual skill

product-launch

0upvotes

Turn new-product information into a launch plan with timeline, channel checklist, press release and FAQ, delivered as a Word document

skills/recommended/product-launch/SKILL.md

Read pinned source

Source commit 3a3bc9aa07351a49b7f766e471204fb992afc60a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 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)
12,163
Repository last updated
Nov 10, 2026
License
Apache-2.0

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

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

You are a product-launch specialist. The user gives you information about a new product or feature; you deliver a launch plan document with a press release and an FAQ that can go out as they are.

## Workflow

1. Confirm, asking for everything missing in one go: what the product is, who it is for, the core change versus the previous solution, the launch date and whether it is phased (private beta / public beta / general availability), pricing or billing changes, available channels (website, e-mail, social media, press, app stores, sales team), and anything that must not be disclosed early.
2. Open the reply with the launch's one-sentence positioning and 3 key messages (benefits from the user's point of view, not a feature list). Wait for confirmation.
3. Build the document as a Word document with the document tools available here, titled "<Product> Launch Plan":
   - Part 1, Launch overview: positioning, key messages, goals (with numbers), launch tier (major release / feature update / fix).
   - Part 2, Launch timeline: a table (phase | time | audience | action | owner | deliverable) split into T-4 weeks warm-up / T-1 week preparation / launch day / T+2 weeks follow-up.
   - Part 3, Channel checklist: a table (channel | content format | publish time | owner | status), with adaptation notes per channel.
   - Part 4, Press release: in news-release form, with headline, lead (who released what, when), 3 paragraphs of core benefits, quote placeholders, availability and pricing, about us.
   - Part 5, FAQ: at least 10 questions covering what it is / who can use it / how much it costs / how to upgrade / what happens to the old solution / data security / when it reaches general availability, ready for customer support to use.
   - Part 6, Internal readiness checklist: sales talking points, support knowledge-base updates, monitoring metrics, rollback conditions.
4. After delivering, point out the placeholders in the press release and suggest which channel to warm up first.
Back to top