agentleFS
matteotittamatteotitta/genesys-skills/skills/product-launch/SKILL.md

product-launch

Skill53 starsChanged 5 days agoMITView on GitHub

Plans a product launch from a brief: launch tier, 5-8 launch tactics, narrative angle, objectives, then the assets and a T-14 to T+30 timeline built from those tactics. Use when asked to plan a launch, a launch strategy or a go-to-market for a feature.

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use business-plan, email-marketing and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • walternateSkill

    business-plan

    Write, structure, and update a business plan for a solopreneur. Use when creating a plan from scratch, updating an existing plan after a pivot or new phase, or preparing a plan to share with investors, partners, or even just to clarify your own strategy. Covers executive summary, market analysis, competitive positioning, revenue model, operations plan, financial projections, and risk assessment — all adapted for a one-person business. Trigger on "write a business plan", "business plan", "create my plan", "business plan template", "update my business plan", "plan for my business", "investor pitch plan".

    Also in 3 projects that use this

  • claude-office-skillsSkill

    email-marketing

    Email marketing automation - campaign creation, sequence building, A/B testing, deliverability optimization, and analytics

    Also in 3 projects that use this

  • LangChainSkill

    competitor-analysis

    Analyze competitors in a given market segment. Trigger on: competitive landscape, competitor analysis, market comparison, competitive positioning.

    Also in 3 projects that use this

  • silvainfmSkill

    pricing-strategy

    When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' or 'monetization.' This skill covers pricing research, tier structure, and packaging strategy.

    Also in 3 projects that use this

  • AnthropicSkill

    content-strategy

    Analyzes sales data from PayPal and QuickBooks to find top performers and slow movers, layers in seasonality, and produces a prioritized 30-day content brief: what to push, what offers to run, what to hold. Strategic output only — no calendars or assets. Use when the user asks what to post, wants a content plan, asks what's selling, or what to promote this month.

    Also in 3 projects that use this

  • birne-skSkill

    market-research

    Professional market research and competitive analysis using McKinsey/BCG/Bain consulting methodologies. Use when analyzing markets, competitive landscapes, customer insights, or strategic positioning. Generates hypothesis-driven research with PPTX presentation deliverables.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before proceeding, verify the feature brief includes name, category, description, target personas, key capabilities.

    line 52
  2. Distinctive:

    If inputs are missing: ask the user for the brief, the messaging and the target personas, or draft them from the product page and confirm …

    line 54
  3. Distinctive:

    If you've ever shipped something that got crickets, this skill fixes it.

    line 107
  4. Very specific:

    Every launch happens in a cultural context.

    line 111
  5. Very specific:

    No invented metrics: Use provided proof points or mark as [PLACEHOLDER: metric].

    line 146
  6. Very specific:

    Mark placeholders clearly: Use [PLACEHOLDER: description] for unconfirmed details.

    line 148
  7. Distinctive:

    Use product-messaging output directly

    line 167

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Product launch

Architect and execute B2B SaaS product launches that drive sustained pipeline. Launches are built on the tactics around the event — not the channel checklist. Pick 5–8 tactics from the 16-tactic library; derive assets from the chosen tactics; orchestrate across pre-launch, launch day, and post-launch.


Claude Code triggers

Invoke when user says:

  • "Product launch for [feature/product]"
  • "Feature launch plan"
  • "Launch strategy for [company]"
  • "GTM launch plan"
  • "New feature announcement"
  • "Create launch assets"
  • "Launch timeline for [feature]"
  • "Launch checklist"
  • "Plan a launch for [feature]"
  • "Launch playbook"

Do NOT invoke when the user wants only landing page copy, product messaging, LinkedIn content, email copy, or live event production.


Input requirements

Required

InputDescriptionSource
Product feature briefWhat's launching, target release dateUser provides
Product messagingCapabilities, benefits, differentiatorsUser provides or existing doc
ICP researchTarget personas, pain points, proof pointsUser provides or existing doc

Optional (improve quality)

InputHow it helps
TOV guidelinesBrand voice for all copy assets
Competitor launchesDifferentiation framing
Sales objectionsFAQ and enablement content
Customer feedbackProof points and testimonials
Launch dateTimeline anchoring

Validation

Before proceeding, verify the feature brief includes name, category, description, target personas, key capabilities; product messaging available or generated; ICP research available or generated; launch date confirmed (or flexible window).

If inputs are missing: ask the user for the brief, the messaging and the target personas, or draft them from the product page and confirm before going further.


Core frameworks

Launch philosophy

The old launch playbook is dead. Most marketers launch by writing "we're excited to announce" on LinkedIn, ticking off a channel checklist (Product Hunt / Hacker News / Reddit / LinkedIn / X), and wondering why their CEO asks "wait, did we even launch?" the following Monday.

A great launch is built on the tactics around the launch — not the channel checklist. The skill encodes 16 tactics in the premium reference. Strategy phase picks 5–8 of them. Development phase derives assets from the chosen tactics, not from a default 18-asset list.

The order matters: tactics first, then assets. Reverse this and you're back to the channel checklist mentality.

A launch built this way:

  • Pre-builds audience before launch day (waitlist, teaser, ambassador, partner)
  • Stages a real moment (live event, drop, named version)
  • Sustains attention for 2+ weeks post-launch (recap cadence)
  • Compounds across cycles (60-day relaunch every quarter)

T-0 is the midpoint, not the destination. And the channel checklist is not the strategy.

Three-phase architecture

PhasePurposeDurationDeliverables
StrategyPick 5–8 tactics; define narrative, objectives, positioningT-14 to T-10Strategy brief with selected tactics, narrative angle, success metrics
DevelopmentProduce assets derived from chosen tacticsT-10 to T-1Asset list scoped to tactics (not a default 18-asset checklist)
DeploymentOrchestrate timeline and amplificationT-14 to T+14Timeline, coordination playbook

Launch tiers

TierDescriptionTactic countAsset scope
MajorNew product, category entry, platform shift7–8 tacticsLive event + waitlist + teaser + ambassadors + partner + recap + relaunch + paid
SignificantMajor feature, integration, pricing change5–7 tacticsSubset above; selective paid
StandardFeature improvement, capability expansion4–6 tacticsChannel-specific copy + recap + founder personal posts + 1–2 others
MinorBug fix, UX improvement3–4 tacticsChannel-specific copy + recap + grandfather (if applicable)

Anything counts as a launch

The 16-tactic library doesn't only apply to product launches. The same machinery runs for:

  • Stealth exits — coming out of stealth is a launch
  • Feature drops — significant feature releases
  • Hiring announcements — exec hires, team scale-ups
  • Pricing changes — new tiers, plan refactors (always pair with grandfather policy)
  • Big blog posts — flagship content, research releases
  • Funding announcements — Series A/B/C, secondary rounds
  • Partnership reveals — when a partner co-launch IS the launch
  • Geographic expansion — entering a new market

If you've ever shipped something that got crickets, this skill fixes it. The trigger isn't "is this a product?" — it's "are we asking the audience to pay attention?" If yes, run the playbook.

Seasonal alignment

Every launch happens in a cultural context. Check for adjacent cultural moments (±14 days from launch), score alignment fit (Strong/Medium/Weak/Negative), choose strategy (ride the wave, counter-program, ignore, or avoid), and adapt messaging (hooks, imagery, CTAs). See the premium reference.


Tactic library — Strategy starts here

Before anything else in the Strategy phase, pick 5–8 tactics from the premium reference. The 16-tactic menu covers waitlist, ambassador army, partner co-launch, channel-specific copy, founder personal posts, gamified drops, filtered giveaways, weird swag, audience-as-detective narratives, named versions, public roadmap voting, grandfather policy, teaser videos, live events, recap cadences, and 60-day relaunches.

Selection criteria: launch tier, audience size, ICP shape, resource constraints, existing community signal. The chosen tactics drive the Development phase asset list — not a default 18-asset checklist.

Three battle-tested stacks live in the premium reference as starting points:

  • Clicky stack — Waitlist → Teaser → Live event → Recap. Best for momentum into a live event.
  • Long-tail stack — Ambassador army → Partner co-launch → 60-day relaunch. Best for cold audiences and limited founder time.
  • Drama stack — Narrative campaign → Named version → Recap. Best for personality-led brands.

Most launches won't match a stack cleanly — combine across stacks. The 5–8 selection rule is the discipline.


Process

The launch runs in three phases. Read the premium reference for the full step-by-step (5 strategy steps, 8 development steps, 4 deployment steps, plus per-phase checkpoints and the process flowchart).

Phase summary:

  1. Strategy (T-14 to T-10) — feature brief, 5–8 tactics selected from the tactic menu, narrative angle, business objectives, kick-off agenda
  2. Development (T-10 to T-1) — derive assets from chosen tactics (not from a default 18-asset checklist), produce each via its template-spec
  3. Deployment (T-14 to T+14) — pre-launch / launch-day / post-launch timelines + coordination playbook with RACI

Anti-hallucination guardrails

  1. Ground all claims in inputs. Feature benefits must come from product brief or messaging.
  2. No invented metrics. Use provided proof points or mark as [PLACEHOLDER: metric].
  3. Quote verbatim. Customer quotes from ICP research only.
  4. Mark placeholders clearly. Use [PLACEHOLDER: description] for unconfirmed details.
  5. Cite sources. Link each asset to its input source.

MCP data integration

Level: 2 — PM Execution (inherits strategy, operational pulls)

Inherits from: product-messaging

Pulls fresh

SourceWhat to pullToolWhen
SlackLaunch coordination threadsslack_search_publicAlways

Fallback (no MCP)

  • Use product-messaging output directly
  • Manual launch coordination via shared docs
  • User-provided timeline and stakeholder info

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.