launch-messaging
Skill5 starsChanged 2 months agoNo licenceView on GitHub
Build or refresh a complete B2B product or company launch messaging hierarchy — positioning framework, galvanizing narrative, messaging pillars, proof points, persona angles, competitive frame, and elevator pitches. Has two modes: FROM SCRATCH (no prior hierarchy exists) and QUARTERLY REFRESH (a prior approved hierarchy exists and needs updating against what changed). Creates a persistent, resumable project folder with a running CHECKLIST.md and a dated DECISIONS.md decision log, and delivers a formatted Word document. Also handles the owner review cycle: fold in review comments after the owner marks up the delivered document, running an owner review that turns each comment into a tracked task and closes with independent verification. Use this skill whenever someone wants to: develop launch copy or positioning for a product, create or refresh a messaging framework or messaging hierarchy, work on go-to-market (GTM) messaging, write positioning for a new product or feature, build out value props and pillars, nail down their company narrative, create a press release foundation, develop sales messaging, run a periodic refresh of an existing messaging hierarchy, or fold owner review comments and tracked changes into the next draft. Also trigger this skill for "what's our big idea", "how do we talk about X", "positioning statement", "elevator pitch", "quarterly messaging refresh", "update our narrative", "owner review", "review cycle", "fold in review comments", or any request to work through how a company or product should communicate its value. Works for any B2B product — SaaS, infrastructure, developer tools, AI products, enterprise software.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ejwhite7/product-release-checklisttheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ejwhite7/product-release-checklist★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
23 rules. About 0 are common, 16 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈16
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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
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.