More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Product Launch Plan

    1

    Plan a product or feature launch as a five-beat story over weeks, not a one-day post: readiness scores, audience building, the announcement kit, channels, and launch week.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Product Launch Plan

    Product Launch Plan

    Example session with this skill installed

    I'm launching a small invoicing app for freelance translators in three weeks. I have about 200 people on an email list from my blog and no press contacts. Give me the launch plan.

    • Read your context and instructions
    • Compiled the product launch plan

    Readiness first. One-person test: you need at least one translator outside your circle using it on real invoices and asking to keep it — if that's not true yet, the next three weeks are a beta, not a launch. Description test: "It's for freelance translators who juggle invoices across currencies, and it lets them send a correct multi-currency invoice in under a minute." If a stranger can repeat that back, it passes. Score the rubric honestly; the usual weak row here is support readiness, so write the FAQ before anything else.

    Five beats, dated from today. Beat 1, the itch (weeks 1–2): one post in translator communities and on your blog about the real problem — chasing payment across currencies and formats — with no product mention until the comments ask. Your 200-person list gets one update when something real lands, not a drip. Beat 2, the invitation (week 2): open a 30-person beta from the list, watch them invoice unaided, fix the two worst confusions. Beat 3, the reveal (launch day, a Tuesday or Wednesday morning): email the full list first — they are owed first access and will be your warmest commenters — then post in the two translator communities where you have been participating, leading with the payment-chasing story, not the feature list. One action everywhere: the signup page. Beat 4, the proof (days 2–7): ship the first requested fix publicly and post whatever numbers you have, even small ones. Beat 5, the sustain: a monthly changelog email, so the list keeps compounding.

    Channels per the decision table: niche professionals lead with their own forum spaces, newsletter pitches support. Skip launch boards unless your translators actually read them. Measure activations and day-seven retention of launch-week signups, not page views.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Most launches fail before launch day: no audience built, no readiness check, an announcement that leads with features, and silence after the spike. This skill treats a launch as a story told over weeks — the announcement day is just the day an audience you already built finally gets the thing.

    It starts with three readiness tests (a real outsider who wants to keep using it, a one-sentence description that survives a stranger, and a core path that works unaided) converted into a scored rubric: launch at 7 of 10, never with a zero on the first two rows. Then it builds the audience before you need it — direct lines you control (email list, community, a publishing rhythm) over any algorithm — and plans the five beats: the itch (talk about the problem), the invitation (beta and waitlist), the reveal, the proof (visible fixes and numbers in week one), and the sustain (a rhythm that turns a spike into a base).

    You also get the reusable announcement kit (one sentence, one paragraph, demo, signup page, pre-written FAQ, metrics sheet), a fill-in launch plan template, a channel decision table keyed to audience type, a concrete launch-week schedule, failure-mode playbooks (dead post, fallen signup page, silent press, a competitor launching the same week), and a pre-launch quality gate that has to pass before anything is scheduled.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Product Management.

    This skill plans launches; it does not post, pitch, or send anything for you, and it cannot manufacture an audience you have not started building — if your direct lines are zero, the honest plan front-loads weeks of audience work before any date is set. Channel advice is calibrated to small and mid-size launches by founders and small teams; enterprise launches with sales cycles and analyst relations need a different apparatus. It also refuses to plan around an unready product: fail the readiness rubric and the output is a fix list, not a launch date.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 24 days ago

    Permissions

    No special permissions declared or detected

    Listed24 days ago
    Updated21 days ago

    What's inside

    Frequently Asked Questions

    No, but it will be honest with you. Run the readiness rubric and the quality gate first; whatever passes, compress the beats — the itch and invitation can run in days if you already participate in a community. What you cannot compress is having no audience at all; the plan will say so and prioritize your warmest channel.

    A runbook covers the operational go-live: deploys, monitoring, rollback. This skill covers the months-and-weeks layer — audience, story, channels, and measurement — that decides whether anyone shows up to the go-live.

    Yes, if something material changed: a real fix, a new audience, or a sharper story. The skill's failure-mode section covers re-approaching a community honestly. Relaunching the identical product with the identical post is the one move it will talk you out of.

    New in Product Management