agentleFS
Sach1ngSach1ng/PM-operating-OS/skills/launch-post/SKILL.md

launch-post

Skill3 starsChanged 18 days agoMITView on GitHub

Help PMs write Slack-native launch announcements. Use when shipping a feature, experiment, or release and want to announce it to the team.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When asked "help me write a launch post for Slack"

    line 15
  2. Distinctive:

    Call to action (try it, give feedback) or kudos

    line 48

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Launch Post

Help PMs write Slack-native launch announcements. Produces concise, celebratory posts that inform the team what shipped, who it's for, and why it matters.

When to Use

  • Shipping a new feature
  • Announcing an experiment rollout
  • Releasing a product update
  • When asked "help me write a launch post for Slack"
  • Celebrating a milestone or go-live

Process / Template

1. Gather Key Information

  • What shipped — feature name, experiment, or release
  • Who it's for — target users or segment
  • Key metrics — what success looks like (optional)
  • Links — docs, dashboards, Figma, demo
  • Kudos — who contributed (optional)

2. Use Slack-Native Format

  • Emoji — use sparingly for visual anchor (e.g., 🚀 for launch)
  • Short paragraphs — 1–2 sentences max
  • Bullets — for scannability
  • Links — inline, descriptive (not raw URLs)
  • Tone — celebratory but informative

3. Structure the Post

Opening

  • One-line hook: what shipped and why it matters

Body

  • What — brief description of the change
  • Who — target users or segment
  • Impact — expected benefit or metric (if known)
  • Links — where to learn more, try it, or see data

Closing

  • Call to action (try it, give feedback) or kudos

4. Keep It Concise

  • Aim for 3–5 short paragraphs or bullet blocks
  • Skip internal jargon when possible
  • Lead with customer value, not implementation details

Output

A Slack-ready launch post that:

  • Fits naturally in a #launches or #shipped channel
  • Is scannable in 30 seconds
  • Celebrates the team
  • Points readers to more detail if they want it

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.