product-launch · genspark-ai — Claude Code skill: launch plan in a Word doc
product-launch turns notes about a new product or feature into a launch plan: timeline, channel checklist, press release and FAQ, delivered as a Word document.
Apache-2.0 ★ 12,746 updated 2026-10-29
npx skills add genspark-ai/genoffice --skill product-launch -a claude-codeWhat product-launch does
The skill takes whatever you can say about a new product or feature and builds a Word document titled “<Product> Launch Plan”. It starts with one round of questions: who the product is for, what changes against the old solution, the launch date and its phases, pricing shifts, the channels you can use, anything that must stay quiet until release. Then it writes a one-sentence positioning and three key messages, and stops for your approval.
Six parts follow. An overview with goals and release tier; a timeline table (phase, time, audience, action, owner, deliverable) running from T-4 weeks to T+2 weeks; a channel checklist; a press release in news form; an FAQ of at least 10 answers written for support; an internal readiness list with metrics and rollback conditions.
The release stays near 600 words, and FAQ answers stop at three sentences. Claims come only from what you supplied, quotes sit as placeholders, beta details stay out of public copy. Building the file needs the document tools present in the session; without them nothing gets written to Word.
What it helps with
- draft a launch timeline with owners and deliverables
- write a press release without inventing quotes or numbers
- hand support an FAQ before release day
- split a phased launch into beta and general availability
- check sales and support readiness ahead of the announcement
Example prompts for the agent
- Put together a launch plan and press release for this new feature
- Build the channel checklist and timeline for our product launch
- Draft the launch document with a phased rollout and a support FAQ
How to install product-launch
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill product-launch -a claude-code2Manually: put the files in place
~/.claude/skills/product-launch/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/product-launch/
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill product-launch -a codex2Manually: put the files in place
.agents/skills/product-launch/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill product-launch -a cursor2Manually: put the files in place
.cursor/skills/product-launch/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install genspark-ai/genoffice skills/recommended/product-launch2Manually: put the files in place
.github/skills/product-launch/SKILL.md1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill product-launch -a gemini-cli2Platform CLI
gemini skills install https://github.com/genspark-ai/genoffice --path skills/recommended/product-launchManually: put the files in place
.devin/skills/product-launch/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about product-launch
How do I install product-launch in Claude Code?
Run npx skills add genspark-ai/genoffice --skill product-launch -a claude-code. The skill lands at ~/.claude/skills/product-launch/SKILL.md.
What does product-launch do?
It turns product notes into a Word document covering the launch overview, timeline, channel checklist, press release, FAQ and an internal readiness list. Before writing it collects the missing details and shows you the positioning and key messages first.
What if the launch date is not set yet?
The document then uses relative “T day” timing throughout instead of guessing a date. A phased launch gets one row per phase, each with its visibility scope and the condition for moving on.
Source text
SKILL.md · Apache-2.0
--- name: product-launch description: Turn new-product information into a launch plan with timeline, channel checklist, press release and FAQ, delivered as a Word document category: marketing scenarios: Product launches | Press releases | Go-to-market timelines quickPrompts: Make a launch plan and announcement for this new feature | Put together the channel checklist and timeline for our product launch metadata: version: 1.0.0 --- 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. ## Style - The press release lead says "who, when, what is released, and what it brings to whom" in one sentence; the whole release stays under roughly 600 words. - Each core-benefit paragraph opens with the benefit and then explains the feature; no empty words like "powerful" or "all-new". - FAQ answers are 3 sentences or fewer and can be pasted straight into the support knowledge base; technical detail goes behind a link placeholder, not inline. - Times in the timeline and channel tables use either T plus/minus N or absolute dates, never both. ## Rules - Feature, performance and pricing claims use only facts the user provided; competitor comparisons must be supportable by public information, otherwise compare with the previous version of the product itself. - When the launch date is not set, the whole document uses relative "T day" timing; never guess a date. - Features not yet confirmed never appear in the press release; they may appear in an FAQ "Future plans" entry worded as "under evaluation". - Quotes are never invented for real people; leave a "[spokesperson name / title] quote placeholder". - For phased launches, each phase gets its own row stating visibility scope and the condition for moving on; beta information does not go into public copy. - Customer or partner names in the release require the user's confirmation that permission has been granted; otherwise use a generic phrase such as "a leading customer".
© genspark-ai · Apache-2.0 · genspark-ai/genoffice
Similar skills
All skills for Marketing and content →product-launch by other authors comes first.