More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Product Launch Playbook

    1

    Plan a product launch end to end — readiness, audience, story, channels, launch week, and what to measure after.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Product Launch Playbook

    Product Launch Playbook

    Example session with this skill installed

    Plan the launch for PantryPilot, my meal-planning app for parents who cook on weeknights. It makes a week of dinners from what is already in the pantry. Launch is in about three weeks, I have a waitlist of 180 people from a parenting forum, and two parents outside my family use it every week. I can spend my time in two places well, not five.

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

    PantryPilot launch plan

    Readiness: one-person test passed. Two parents outside your household use it weekly and asked to keep it. Description test: "It is for parents who stare into a full pantry at 5:30 with no plan, and it gives them a week of dinners from what they already own in about ten minutes." That sentence goes on the signup page and both launch posts, word for word. Known gaps (no vegetarian filter yet, barcode scanning unreliable) go in the public FAQ now.

    Five-beat arc

    • Beat 1, the itch, now to day -10: post in the parenting forum where the waitlist came from about the 5:30 problem itself, failures included. No product name in the first post.
    • Beat 2, the invitation, day -10 to -3: open beta to the 180-person waitlist in two batches. One update only, with a 90-second video of a pantry becoming a week of dinners. Fix batch one's reports before batch two gets in.
    • Beat 3, the reveal, launch day, a Tuesday: one message in two places, the forum and Product Hunt, both pointing to one action on the signup page. Stay in both threads all day.
    • Beat 4, the proof, launch week: post the numbers in the same threads, signups and how many planned a second week. Ship the two most requested fixes and say so there.
    • Beat 5, the sustain, weeks 2 to 5: start a monthly changelog email: what changed, one meal plan that worked.

    Kit to build this week: the one sentence (above); a one-paragraph version for email; the 90-second video; a signup page with one email field; a FAQ covering the vegetarian filter, allergies (not handled yet, say so plainly), and post-trial cost; a metrics sheet with three numbers only: day-one signups, second-week planners, and which channel sent people who stayed. Ignore views and likes.

    Launch week: Day -7, dry-run the announcement on a non-tech parent and fix what they misunderstand. Day -1, check the signup page on a phone, FAQ live. Day 0, post early, forum first. Day +1, thank both threads, publish numbers, ship the first fix.

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

    About this skill

    Shipping and launching are different work. This skill covers the second one: a readiness check before you announce anything, building the audience before you need it, the story arc of the launch itself, channel selection (Product Hunt, communities, waitlist, early access), a launch-week sequence, and the metrics that tell you if it worked. Written from real launches, including the unglamorous parts.

    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 produces a launch plan, an announcement kit list, and a dated checklist. It does not write or send your posts, pitch journalists, or publish anything to Product Hunt or any community for you. The plan depends on honest inputs from you about readiness, existing users, and audience size, and a thin existing audience will show up in the plan as audience-building work first.

    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 25 days ago

    Permissions

    No special permissions declared or detected

    Listed25 days ago
    Updated21 days ago

    What's inside

    Frequently Asked Questions

    A plan you execute: readiness test results, a five-beat story arc with dates, the announcement kit to build, a two-channel shortlist, a launch week checklist, and the short list of metrics worth tracking. Posting, pitching, and publishing stay with you.

    Yes, and the plan will look different because of it. The early beats become audience-building work in the places your buyers already gather, plus a waitlist page, before any reveal date is set. Tell the skill your list size honestly, including zero.

    Any agent that supports the SKILL.md standard, including Claude Code, Cursor, VS Code Copilot, and Gemini CLI. Your agent loads the latest approved version each time you use it, so improvements reach you without a new download.

    New in Product Management