← ClaudeAtlas

launch-readinesslisted

Audit a product before launch day. Checks the buy path end to end, the product page, the download, refunds, analytics and the announcement plan, and returns a go/no-go list with the fix for each blocker. Use when someone says "we launch tomorrow", "is this ready", or before announcing anything publicly.
leymish01-oss/claude-code-founder-skills-sample · ★ 0 · AI & Automation · score 72
Install: claude install-skill leymish01-oss/claude-code-founder-skills-sample
# Launch readiness audit ## When to use Before any public announcement of a product, price change or new version. Run it again the morning of the launch; things break overnight (expired links, unpublished drafts, wrong prices). ## Inputs - The product page URL or its source files, and the checkout/download URL. - The price and any discount codes. - Where the launch will be announced (list of channels). - Optional: the refund policy, the receipt/thank-you email text, the analytics setup. ## Steps 1. **Walk the buy path as a stranger.** Landing page → buy button → checkout → receipt → download → first-use instructions. Note every click. Every buy button on every page must point to the same live checkout. Flag any `#`, empty or draft links. 2. **Check the offer matches everywhere.** Price, discount code, what's included and the refund window must say the same thing on the page, the checkout, the listing and the announcement drafts. 3. **Open the deliverable.** Unzip or open it. Does it contain what the page promises? Is there a README or "start here"? Does the first command in the instructions actually work? 4. **Check trust signals are honest.** No invented numbers, reviews or logos. Claims are specific and checkable. There's a way to contact a human. 5. **Check the basics.** HTTPS, mobile layout (375px wide), page title and meta description, a social preview image, a 404 page, spelling of the product name. 6. **Check you can measure it.** Can you tell tomo