ai-launch-playbook
Skill1 starsChanged 23 days agoMITView on GitHub
Produces a launch plan built for Artificial Intelligence (AI) products and features: a demo-led narrative, waitlist and early-access design with capacity gates, a channel plan for Product Hunt, Hacker News, LinkedIn, and developer communities, evaluation-backed proof, a day-0 to day-30 runbook, and pre-written failure-mode communications. Use when launching an AI product, agent, or AI feature; planning a waitlist or private beta for a model-backed product; preparing for a Product Hunt or Hacker News launch; or de-risking a launch where output quality, cost, or safety could go wrong in public.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Gingiris-1031/gingiris-skillstheir own version, first seen Oct 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Gingiris-1031/gingiris-skills★ 89same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository41 other files it gives its agents.
- ai-activation-optimizerSkill
- ai-content-quality-gateSkill
- ai-feature-experiment-designerSkill
- ai-pricing-margin-modelerSkill
- ai-product-positioningSkill
- ai-search-visibility-optimizerSkill
- agent-autonomy-level-mapperSkill
- ai-failure-state-designerSkill
- ai-usability-test-plannerSkill
- ai-ux-auditSkill
- human-in-the-loop-designerSkill
- prompt-surface-designerSkill
- uncertainty-and-explainability-patternsSkill
- ai-agent-financial-analystSkill
- burn-rate-runway-plannerSkill
- capital-allocation-frameworkSkill
- dcf-valuation-builderSkill
- financial-statement-analyzerSkill
- saas-cohort-analyzerSkill
- competitive-response-modelerSkill
- mechanism-design-plannerSkill
- nash-equilibrium-solverSkill
- negotiation-strategistSkill
- repeated-game-strategistSkill
- ai-decision-engineSkill
- ai-product-strategySkill
- ai-stakeholder-translatorSkill
- customer-interview-synthesizerSkill
- jobs-to-be-done-extractorSkill
- opportunity-solution-treeSkill
- product-discovery-coachSkill
- product-roadmap-prioritizerSkill
- blue-ocean-strategy-canvasSkill
- go-to-market-strategySkill
- gtm-engineeringSkill
- market-sizingSkill
- okr-cascade-plannerSkill
- porters-five-forces-analyzerSkill
- pricing-strategy-analyzerSkill
- strategic-landscape-mapperSkill
- swot-tows-analyzerSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
No plan for the viral screenshot of a wrong, biased, or unsafe output
- Distinctive: line 50
No Tier 1 launch with any Red gate.
- Distinctive: line 148
Treat launch-day signups as success before activation and week-4 retention are known
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AI Launch Playbook
AI launches fail in public in ways normal software launches do not - plan the demo, the capacity, and the bad screenshot before day 0.
What this skill is
A launch workflow for products whose core output is generated by models. It complements a general go-to-market plan by handling what is specific to AI: demos that must be reproducible, inference capacity and cost that scale with hype, evaluation results as the main proof, technical audiences who will try to break the product, and the near-certainty that someone will post a bad output. It produces a sequenced runbook with owners and pre-approved responses.
What it solves
- Cherry-picked demos that users cannot reproduce, turning launch-day interest into "it does not work like the video"
- Waitlists that collect emails but never convert, or let in more users than inference budget can serve
- Launch posts on technical communities that read as marketing and get flagged or ignored
- Quality claims with no benchmark or evaluation behind them
- No plan for the viral screenshot of a wrong, biased, or unsafe output
- Cost spikes from free-tier abuse in the first 72 hours
When to invoke
- Planning a public launch or open beta of an AI product or agent
- Shipping a major AI feature into an existing product with a broad user base
- Designing a waitlist, invite system, or staged rollout for a model-backed product
- Preparing a Product Hunt, Hacker News, or developer-community launch
- Re-launching after a weak first launch or a quality incident
Phase 1: Launch tier and readiness gate
| Tier | Scope | Typical channels | Readiness bar |
| 1 | New product or flagship agent | All channels, press, community | All gates green |
| 2 | Major feature | Owned channels, community, customer email | Quality and cost gates green |
| 3 | Incremental improvement | Changelog, in-product | Quality gate green |
Readiness gates (score each Red / Amber / Green):
| Gate | Green means |
| Quality | Offline evaluation pass rate meets target on a held-out set of realistic tasks |
| Reproducibility | 8 of 10 fresh attempts of the demo task succeed for a new user |
| Capacity | Rate limits and inference quota cover 3x the expected peak concurrent users |
| Cost | Cost per active user at peak known; abuse limits on free usage set |
| Safety | Red-team pass on misuse, prompt injection, and sensitive-topic prompts |
| Support | On-call rota, status page, and failure-mode responses approved |
No Tier 1 launch with any Red gate.
Phase 2: Demo-led narrative
Build the story around one hero task the target user does weekly.
| Element | Requirement |
| Hero task | Real, common, and painful; shown end to end in under 90 seconds |
| Before and after | Time, steps, or error rate without and with the product |
| Live versus recorded | Recorded demos labeled; at least one unedited live run published |
| Limits | One sentence on what it does not do well yet |
| Try-it path | The viewer can reproduce the hero task within 5 minutes of signup |
The limits sentence builds trust with technical audiences and preempts the "gotcha" thread.
Phase 3: Waitlist and early-access design
Weekly invites = min(inference budget / cost per active user per week, support capacity / tickets per user per week)| Design choice | Recommendation |
| Qualification | 2-3 questions (role, use case, data source) to prioritize Ideal Customer Profile (ICP) fit |
| Prioritization | ICP fit first, then referrals, then sign-up order |
| Cadence | Fixed weekly waves so capacity and feedback are manageable |
| Activation | Every invite lands on a guided first task, not an empty screen |
| Expiry | Unused invites expire after 7-14 days and are reissued |
| Feedback | In-product thumbs and a short survey after the first successful task |
Track waitlist-to-invite, invite-to-signup, and signup-to-first-good-output conversion per wave.
Phase 4: Channel plan
| Channel | What works | What fails | Owner |
| Product Hunt | Clear hero task, short demo video, founder replying to every comment all day | Vote-begging, vague taglines | |
| Hacker News | "Show HN" by a builder, technical detail, honest limits, free path to try | Marketing copy, gated signup, defensive replies | |
| Founder or leader post with the before-and-after and a customer quote | Generic announcement graphics | ||
| Developer communities | Code samples, Software Development Kit (SDK) or Application Programming Interface (API) quickstart, evaluation methodology | Posting the same link everywhere | |
| Customers and waitlist | Personal email with the hero task and invite | Mass blast with no next step | |
| Press and analysts | Data story or customer outcome under embargo | Feature list without proof |
Stagger channels across launch week instead of one spike, so capacity and the team can absorb each wave.
Phase 5: Evaluation-backed proof
- Publish the evaluation method: task set description, size, scoring rubric, and comparison baseline
- Report results against the realistic alternative (manual process or a general-purpose assistant), not only other tools
- Include failure categories and their frequency, not just the headline pass rate
- Date every benchmark and name the model version behind it
Phase 6: Day-0 to day-30 runbook
| Window | Focus | Key actions | Metrics watched |
| Day -14 to -1 | Readiness | Gates review, demo lock, channel drafts, failure responses approved | Gate status |
| Day 0 | Launch | Staggered posts, all-hands comment coverage, live dashboard | Signups, errors, latency, cost per hour |
| Day 1-3 | Stabilize | Fix top 3 failure patterns, tighten abuse limits, publish known issues | Error rate, first-good-output rate |
| Day 4-14 | Convert | Onboarding fixes, follow-up content, case-study outreach | Activation, day-7 retention |
| Day 15-30 | Prove | Publish early outcome data, launch retrospective, decide next wave | Week-4 retention, cost per retained user |
Phase 7: Failure-mode communications
Pre-write and pre-approve responses for:
| Scenario | First response within | Response pattern |
| Viral wrong or harmful output | 2 hours | Acknowledge, reproduce, state fix or mitigation, no blame on the user |
| Capacity outage or slowdown | 30 minutes | Status page, waitlist pause, timeline |
| Cost runaway from abuse | 1 hour | Rate limits tightened, free tier adjusted with notice |
| Data or privacy concern | 2 hours | Clear statement of what data is used and retained, escalation to legal |
| Benchmark disputed | 24 hours | Share method and raw examples; correct publicly if wrong |
Output
- Launch tier and readiness-gate scorecard
- Demo script with hero task, before-and-after, and limits statement
- Waitlist design with capacity formula and wave schedule
- Channel plan with owners and staggered timing
- Evaluation summary ready for publication
- Day-0 to day-30 runbook and pre-approved failure-mode responses
Operating rules
Always
- Make the demo reproducible by a new user before announcing it
- Size invites to inference budget and support capacity, not to hype
- State known limits in the launch materials
- Have a builder, not only marketing, present on technical channels
- Watch cost per active user hourly during the first 72 hours
Never
- Launch Tier 1 with a Red quality, capacity, or safety gate
- Publish benchmarks without method, date, and model version
- Gate a Hacker News launch behind a sales call or waitlist with no try-it path
- Argue with users posting bad outputs; reproduce and respond with facts
- Treat launch-day signups as success before activation and week-4 retention are known
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
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.

