agentleFS
Sign inStart free
aroyburman-codesaroyburman-codes/pm-skills/skills/launch-checklist/SKILL.md

launch-checklist

Skill25 starsChanged 9 months agoMITView on GitHub

Generate launch readiness checklists for product releases. Covers engineering, QA, design, legal, marketing, support, and rollback planning. Adapts to launch size (feature flag, beta, GA) and AI/ML-specific requirements.

26 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use patch-notes, asset-audit and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CoralGameSkill

    patch-notes

    Generate player-facing patch notes from git history, sprint data, and internal changelogs. Translates developer language into clear, engaging player communication.

    Also in 4 projects that use this

  • CoralGameSkill

    asset-audit

    Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.

    Also in 4 projects that use this

  • +10 more from CoralGame

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 4

    Distinctive

    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
  1. Distinctive:

    Target date: When is this going live?

    line 22
  2. Distinctive:

    All P0 bugs resolved

    line 88
  3. Distinctive:

    All P0 and P1 bugs resolved

    line 93
  4. Distinctive:

    All P0-P2 bugs resolved

    line 99

“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Launch Checklist Skill

Generate a comprehensive, customized launch readiness checklist for any product release.

When to Use

  • User is preparing to launch a feature or product
  • User needs to ensure nothing is missed before go-live
  • User says /launch-checklist followed by what they're launching
  • Any pre-launch review or go/no-go decision

Framework: Launch Readiness Checklist

Step 1: Scope the Launch

  • What's launching? Feature name and brief description
  • Launch type: Feature flag → Internal → Beta → GA
  • Target date: When is this going live?
  • Blast radius: How many users are affected?
  • Reversibility: Can we roll back easily?

Step 2: Generate Checklist by Function

Engineering

  • Code complete and merged to release branch
  • Unit tests passing (coverage threshold met)
  • Integration tests passing
  • Load/performance testing complete (meets latency/throughput targets)
  • Feature flag configured and tested (on/off/gradual rollout)
  • Database migrations tested and reversible
  • API versioning handled (no breaking changes for existing clients)
  • Monitoring and alerting configured
  • Logging sufficient for debugging
  • Rollback procedure documented and tested

QA

  • Test plan executed (happy path, edge cases, error states)
  • Cross-browser/cross-platform testing complete
  • Accessibility testing (screen reader, keyboard nav, contrast)
  • Regression testing on adjacent features
  • Security review complete (auth, input validation, data handling)

Design

  • Final designs match implementation
  • Empty states, loading states, error states all designed
  • Mobile/responsive behavior verified
  • Copy reviewed and finalized
  • Animations/transitions smooth and performant

Legal & Compliance

  • Privacy review complete (data collection, retention, deletion)
  • Terms of service updated if needed
  • GDPR/CCPA compliance verified
  • Licensing for any third-party components cleared

Marketing & Communications

  • Launch announcement drafted
  • Help center / documentation updated
  • In-app messaging configured (tooltips, onboarding)
  • Social media / blog post scheduled (if applicable)
  • Internal comms sent to stakeholders

Support

  • Support team briefed on new feature
  • FAQ and troubleshooting guide prepared
  • Escalation path defined for launch-related issues
  • Known limitations documented

AI/ML-Specific (if applicable)

  • Model eval results meet quality bar
  • Safety/red-team testing complete
  • Content policy and guardrails configured
  • Hallucination rate within acceptable threshold
  • Cost per query within budget
  • Fallback behavior for model errors/timeouts
  • Data pipeline monitoring active
  • Bias testing on key demographic segments

Step 3: Go/No-Go Criteria

Define clear criteria for each launch stage:

Internal Launch Go/No-Go:

  • All P0 bugs resolved
  • Core user flow works end-to-end
  • Monitoring active

Beta Launch Go/No-Go:

  • All P0 and P1 bugs resolved
  • Performance meets targets
  • Support team briefed
  • Rollback tested

GA Launch Go/No-Go:

  • All P0-P2 bugs resolved
  • Load testing passed at 2x expected traffic
  • Documentation complete
  • Legal review signed off
  • Monitoring and alerting verified

Step 4: Rollback Plan

  • Trigger criteria: What signals would trigger a rollback?
  • Rollback steps: Exact steps to revert (feature flag off, DB rollback, etc.)
  • Communication: Who to notify and how
  • Timeline: Maximum time from decision to rollback complete

Output Format

Generate as a markdown checklist grouped by function. Mark items as applicable/not applicable based on the specific launch. Include a summary section with launch date, owner, and go/no-go criteria.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free