Agent skill · Content & Marketing

product-launch-checklist

Generate a comprehensive pre-launch, launch day, and post-launch checklist for any product release. Use when preparing for a product launch, feature release, or major update. Produces a role-assigned, tiered checklist covering engineering readiness, marketing and comms, support, and post-launch monitoring.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill product-launch-checklist --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 9 KB
Bundled scripts: none
Path: skills/product-launch-checklist/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Product Launch Checklist Skill Never launch without checking everything. Generate a complete, role-assigned checklist covering pre-launch readiness, launch day execution, and post-launch monitoring. ## Proposes Actions Once the checklist is approved, it can be *executed*: hand the items to [`action-runner`](../action-runner/SKILL.md), which previews them (dry-run, risk-rated), runs only what you approve via the connected action MCP (GitHub/Linear/Slack), and records what was done back to the brain. Typical: **open an issue per checklist item** in the named repo/project (🟡), and **post the launch summary to Slack** (🔴 — approved individually). This skill proposes; action-runner gates and runs — never silently. ## Required Inputs Ask the user for these if not provided: - **Launch name** and planned launch date - **Launch tier** (1 = major product launch, 2 = significant feature release, 3 = incremental update) - **Team members and their roles** (engineering lead, PM, marketing, support, etc.) - **Feature description** (what is being launched) - **Rollback capability** (can this be feature-flagged or reverted quickly?) ## Reads from / Writes to the Brain If a [`professional-brain`

What's inside
Steps it walks through
  1. Proposes Actions
  2. Required Inputs
  3. Reads from / Writes to the Brain
  4. How to Use This Skill
  5. Output Format
  6. Launch Checklist — [Feature/Product Name] — Target Date: [Date]
  7. 🔧 PRE-LAUNCH — Engineering & Product (T-2 weeks)
  8. 📢 PRE-LAUNCH — Marketing & Comms (T-1 week)
  9. 🎓 PRE-LAUNCH — Sales & Support (T-1 week)
  10. 📊 PRE-LAUNCH — Analytics (T-1 week)
  11. ✅ GO / NO-GO DECISION — T-24 hours
  12. 🚀 LAUNCH DAY
  13. 📈 POST-LAUNCH (D+7, D+30)
  14. Deeper Materials
Ships with 3 files
  • references/launch-tiering.md
  • references/worked-example.md
  • templates/launch-plan.md
More from pm-claude-skills
All skills →
About this skill
What does the product-launch-checklist skill do?

Generate a comprehensive pre-launch, launch day, and post-launch checklist for any product release. Use when preparing for a product launch, feature release, or major update. Produces a role-assigned, tiered checklist covering engineering readiness, marketing and comms, support, and post-launch monitoring.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill product-launch-checklist --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going