launch-strategy

launch-strategy is a skill for Claude Code, Codex from exiao/pm-skills. It costs 58 tokens per session (1,018 once invoked), scanned A, original, Apache-2.0.

A framework for planning a product launch, feature announcement, or release. It organizes communication across channels such as a company’s own website or email, social platforms, and partnerships.

In plain words
What is it for?
Use it to plan launches, beta releases, waitlists, Product Hunt activity, feature announcements, and release checklists.
Why use it?
It helps turn a release into a coordinated communication plan instead of a single announcement. It also distinguishes channels the company controls from channels it only borrows or rents.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to plan launches, beta releases, waitlists, Product Hunt activity, feature announcements, and release checklists.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/exiao/pm-skills/launch-strategy
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add exiao/pm-skills --skill launch-strategy
Clone the repo
git clone --depth 1 https://github.com/exiao/pm-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for launch-strategy

README.md
[![agentmods](https://agentmods.dev/badge/skills/exiao/pm-skills/launch-strategy.svg)](https://agentmods.dev/skills/exiao/pm-skills/launch-strategy)
Your own site
<a href="https://agentmods.dev/skills/exiao/pm-skills/launch-strategy"><img src="https://agentmods.dev/badge/skills/exiao/pm-skills/launch-strategy.svg" alt="Measured on agentmods" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,018 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00058 $0.01018
Opus 5 $0.00029 $0.00509
Sonnet 5 $0.00012 $0.00204
Haiku 4.5 $0.00006 $0.00102

Measured 8d ago against content hash 833d85edcef7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

launch-strategy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

launch/launch-strategy/SKILL.md · 137 lines

How it starts

The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Launch Strategy

Expert in SaaS product launches and feature announcements. Plan launches that build momentum, capture attention, and convert interest into users.

Before Starting

Read .agents/product-marketing-context.md if it exists — it contains product name, audience, and positioning context.


Core Philosophy

The best companies don't launch once; they launch again and again. Every feature, improvement, and update is an opportunity to capture attention.


The ORB Framework

Structure launch marketing across three channel types. Everything funnels back to owned.

Owned Channels

You control the channel (email list, blog, podcast, community, website/product). Get more effective over time. No algorithm changes.

Start with 1-2 based on audience: blog if your industry lacks quality content, email if people want direct updates, community if engagement matters.

Rented Channels

Platforms providing visibility you don't control (social media, app stores, YouTube, Reddit). Pick 1-2 where your audience is active. Use them to drive traffic to owned channels.

Borrowed Channels

Tap someone else's audience (guest content, podcast interviews, collabs, speaking, influencer partnerships). Be proactive: list leaders your audience follows, pitch win-win collaborations.


Five-Phase Launch Approach

Phase 1: Internal Launch

Recruit early users to test for free. Collect feedback on usability gaps. Validate core functionality.

Phase 2: Alpha Launch

Create landing page with early access signup. Announce the product exists. Invite users individually.

Phase 3: Beta Launch

Work through early access list. Start marketing with teasers. Recruit friends, investors, influencers. Consider waitlist, "Beta" UI sticker, email invites.

Phase 4: Early Access Launch

Leak screenshots, GIFs, demos. Gather quantitative and qualitative data. Optionally run product/market fit survey. Expand via batch invites or open early access.

Phase 5: Full Launch

Open self-serve signups. Start charging. Announce across all channels.

Read the full file on GitHub · 137 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 137 lines · 58 tokens per session scan A 833d85edcef7

Subscribe to this mod's changes

launch-strategy is a skill published in the GitHub repository exiao/pm-skills (9 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 58 tokens to every session and 1,018 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens