agentleFS
Sign inStart free
ejwhite7ejwhite7/product-release-checklist/skills/launch-readiness/SKILL.md

launch-readiness

Skill0 starsChanged 35 days agoMITView on GitHub

Run a go/no-go red-team review of a launch in the release checklist studio and write the findings it shows on the Readiness tab. Also gives a status summary across all launches. Use for "Red-team review" requests, at T-3, or for "are we ready to launch", "launch status", or "what's blocking the launch".

13 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use experiment-designer and stakeholder-update.

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.
  • Dokkabei97Skill

    experiment-designer

    Designs A/B tests and product experiments with hypothesis structuring, sample size calculation, duration estimation, and result interpretation. Unified framework for both product and marketing experiments.

    Also in 3 projects that use this

  • AnthropicSkill

    stakeholder-update

    Generate a stakeholder update tailored to audience and cadence. Use when writing a weekly or monthly status for leadership, announcing a launch, escalating a risk or blocker, or translating the same progress into exec-brief, engineering-detail, or customer-facing versions.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run studio.mjs list, then validate each active launch.

    line 13
  2. Very specific:

    If the launch-red-team agent is available, delegate to it with the launch file path and the context file path.

    line 17
  3. Distinctive:

    Check the launch content as well as the checkbox state:

    line 18
  4. Distinctive:

    no T+14 second wave

    line 24
  5. Distinctive:

    Don't change checklist statuses.

    line 30

“Common” is measured: kept by at least 6 in 10 of the 10 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 Readiness

The studio already computes the verdict from three things: hard gates, open Phase 0–3 items, and unresolved red-team blockers (readiness() in studio/model.mjs). Your job is the part the model can't compute: judgment.

Status across launches (all)

Run studio.mjs list, then validate each active launch. Reply with one table: Launch | Tier | T-0 | Days out | % done | Overdue | Verdict | Top risk. Then flag any date collisions.

Red-team one launch

  1. If the launch-red-team agent is available, delegate to it with the launch file path and the context file path. Otherwise do the review yourself, using that agent's failure-mode list (plugin agents/launch-red-team.md).
  2. Check the launch content as well as the checkbox state:
    • assets that contradict the message house
    • lifecycle with no exit on activation
    • announcing to users who can't access the feature
    • paid audiences with no consent or suppression
    • KB and support pack missing
    • no T+14 second wave
    • banners with no expiry date
  3. Replace feedback with { at, summary, items }:
    • Severity is blocker only when launching as planned would cause real harm, such as users who can't access the feature, broken measurement, or a legal exposure. Unresolved blockers force NO-GO.
    • Link each finding to its checklist item id where one fits, so the studio can jump to it.
    • summary is the single biggest risk, in one sentence.
  4. Don't change checklist statuses. The DRI resolves or waives items in the studio.

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