plan-launch SKILL.md skillA
plan-launch from tomzx/agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tomzx/agents/plan-launch@git:20261007.b35fc4bPins git:20261007.b35fc4b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tomzx/agents
- Path
skills/pdlc/skills/plan-launch/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261007.b35fc4b, committed Oct 7, 2026
- First version recorded
- Aug 5, 2026
- Size
- 1,931 bytes
- Repository stars
- 12
- License
- MIT
Plan a product launch — readiness checklist, timeline, channels, and success criteria. Start of the PDLC Launch phase.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Plan Launch A launch is a coordinated release, not a deploy. This skill produces the launch plan: who needs to be ready, by when, through which channels, and how we will know it worked. It assumes SDLC has shipped (or is about to ship) the change. ## Prerequisites - Apply the shared PDLC conventions in `skills/pdlc/references/shared.md`. - A shipped or near-shipped change; `acceptance-contract.md` and `goals.md`. ## Steps 1. Define the launch type (minimal/quiet, beta, full GA, phased rollout) and justify it against risk and confidence. 2. Build the readiness checklist across functions: product, engineering, design, docs, support, sales, marketing, legal. Each item has an owner and a due date. 3. Define the timeline: readiness start, launch date, and post-launch review checkpoint. 4. Choose channels and sequencing (in-product, email, blog, sales) tied to the target segments. 5. State launch success criteria: the early-window signals (first hours/days) that indicate the launch succeeded, distinct from the long-term success metrics in `goals.md`. 6. Define the rollback / pause plan: what would trigger pulling back, and who has authority. …
Read the whole file at its exact version.
How to install
mdr add tomzx/agents/plan-launch@sha256:03b116892a102a86The line at the top of this page pins the label git:20261007.b35fc4b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_u557fy44rk7ijuty)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 5, 2026 and Oct 7, 2026, about one every 31 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.b35fc4b latest | 2026-10-07 | b35fc4b | 1,931 B | A | view · diff |
| git:20261004.00bb0c5 | 2026-10-04 | 00bb0c5 | 1,928 B | A | view · diff |
| git:20260805.6b62307 | 2026-08-05 | 6b62307 | 1,925 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1931 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
tomzx/agents · 12 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_u557fy44rk7ijuty GET https://markdownregistry.com/api/v1/resolve?ref=tomzx/agents/plan-launch GET https://markdownregistry.com/api/v1/blob/03b116892a102a863a8efa006eab3b7ea6b8d3aa8bf336cf5718c5814cbce2a6
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.