gtm-launch-planner skillA
gtm-launch-planner is agent-read markdown (skill) from rizwanzafaris/product-manager-os: Tier a launch, choose the first cohort, build the channel plan, and draft the comms and readiness lines so Gate 5 finds them already written. Use when a customer-facing release is coming and the GTM plan or the comms table is empty, when PM and PMM disagree on how big the launch is, when a release takes something away or changes what customers pay, or when a failed launch needs a second attempt. Takes the positioning, the success signal, the release scope and window, and the channel evidence; re.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# GTM Launch Planner: tier it, pick the cohort, write the stop rule first Launches fail in two mirror-image ways. Every release is treated as the big one, so none of them is, and the comms are drafted the night before. Or a release that changes what customers pay ships as a changelog line, and support hears about it from customers. Both get judged afterwards by applause. This skill sets the tier by rule, names a cohort you can list, and writes the one metric and the stop condition before anyone is excited. ## Files this skill drives - [../../templates/planning/gtm-plan.md](../../templates/planning/gtm-plan.md), every section - [../../templates/delivery/launch-comms-plan.md](../../templates/delivery/launch-comms-plan.md), for a tier that needs more than the readiness doc's comms table - [../../templates/delivery/release-readiness.md](../../templates/delivery/release-readiness.md), section 6 and the rollback trigger in section 4 …
Read the whole file at its exact version.
How to install
mdr add rizwanzafaris/product-manager-os/gtm-launch-planner@git:20260919.72235e0mdr add rizwanzafaris/product-manager-os/gtm-launch-planner@sha256:fdceff7687b4f18fPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_4kn66xqmyacklgxy)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260919.72235e0 latest | 2026-09-19 | 72235e0 | 10,124 B | A | view · diff |
| git:20260903.a2ef42e | 2026-09-03 | a2ef42e | 8,343 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 (10124 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
rizwanzafaris/product-manager-os · 4 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4kn66xqmyacklgxy GET https://markdownregistry.com/api/v1/resolve?ref=rizwanzafaris/product-manager-os/gtm-launch-planner GET https://markdownregistry.com/api/v1/blob/fdceff7687b4f18f73fd38ca7d3da1ccd89ed89a0dcf9025004361a47644b7b4
Your agent 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.