product-launch skillA
product-launch is agent-read markdown (skill) from cbrock84/headcount: Takes something built and gets it into the market — tiering the launch to match what it actually warrants, sequencing internal readiness before external announcement, preparing sales and support to answer the questions it creates, choosing the date for a reason, and measuring adoption rather than announcement reach. Use this to plan a launch, right-size one that is consuming more than it deserves, work out why a released feature nobody uses was launched loudly, or run the weeks after launch day..
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
# Product launch A launch is not an announcement. The announcement is the cheapest part and the part most likely to be mistaken for the whole thing, which is how features get press coverage and no adoption. ## Tier the launch before planning it Not everything deserves the same treatment, and treating everything as major is how a team burns its own attention and its audience's. - **Tier one** — changes the story you tell about the product, or opens a new segment. Full motion: positioning work, press, sales enablement, customer communication, campaign. - **Tier two** — meaningful to existing customers, not a new story. In-product announcement, documentation, a note to affected accounts, sales briefing. - **Tier three** — improvement. Release notes and nothing else. Agree the tier before work starts, and expect the pull toward tier one from whoever built it. Effort spent above the tier is taken from somewhere else, usually from the next launch. ## Sequence internal readiness ahead of the announcement The order matters and gets reversed constantly. Support and sales find out from the announcement, then spend launch week answering questions they were never briefed on, badly. …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/product-launch@git:20260916.e72e404mdr add cbrock84/headcount/product-launch@sha256:20f2d212c8af00afPin 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_q6otudyznbjxtvit)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.e72e404 latest | 2026-09-16 | e72e404 | 4,477 B | A | view · diff |
| git:20260901.3f04dfc | 2026-09-01 | 3f04dfc | 4,138 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 (4477 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
cbrock84/headcount · 1,664 stars · license MIT · pushed 2026-09-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_q6otudyznbjxtvit GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/product-launch GET https://markdownregistry.com/api/v1/blob/20f2d212c8af00afee90cef2f2581af4f0f1f61bcb07bca055051ef3b8740c21
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.
More from cbrock84/headcount
Every file in cbrock84/headcount