Technical Launch Planner
jamesrochabrun/skills
Plan and execute technical product launches for developer tools, APIs, and technical products.
Generate a comprehensive pre-launch, launch day, and post-launch checklist for any product release.
Install Product Launch Checklist
$ npx skills add mohitagw15856/pm-claude-skills --skill product-launch-checklist -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills product-launch-checklist --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/product-launch-checklist .claude/skills/product-launch-checklist && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "product-launch-checklist" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/product-launch-checklist into .claude/skills/product-launch-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-launch-checklist", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/product-launch-checklistType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill product-launch-checklist -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills product-launch-checklist --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/product-launch-checklist .agents/skills/product-launch-checklist && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "product-launch-checklist" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/product-launch-checklist into .agents/skills/product-launch-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-launch-checklist", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill product-launch-checklist -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills product-launch-checklist --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/product-launch-checklist .cursor/skills/product-launch-checklist && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "product-launch-checklist" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/product-launch-checklist into .cursor/skills/product-launch-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-launch-checklist", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/product-launch-checklist--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill product-launch-checklist -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills product-launch-checklist --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/product-launch-checklist .gemini/skills/product-launch-checklist && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "product-launch-checklist" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/product-launch-checklist into .gemini/skills/product-launch-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-launch-checklist", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills product-launch-checklistInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill product-launch-checklist -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/product-launch-checklist .github/skills/product-launch-checklist && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "product-launch-checklist" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/product-launch-checklist into .github/skills/product-launch-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-launch-checklist", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill product-launch-checklist -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills product-launch-checklist --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/product-launch-checklist .opencode/skills/product-launch-checklist && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "product-launch-checklist" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/product-launch-checklist into .opencode/skills/product-launch-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-launch-checklist", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
product-launch-checklist- GitHub stars
- 1.4k
- Token cost
- ~2.3k tokens
- SKILL.md length
- 1,176 words
- Files
- 4 (incl. references)
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Generate a comprehensive pre-launch, launch day, and post-launch checklist for any product release.
- Preparing for a product launch
- SKILL.md covers Proposes Actions, Required Inputs, Reads from / Writes to the Brain and How to Use This Skill, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Feature release
What it does
Product Launch Checklist is an agent skill from mohitagw15856/pm-claude-skills. 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.
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/launch-tiering.md`, `references/worked-example.md` and `templates/launch-plan.md`).
It sits in Marketing & SEO, covering Product launch strategy. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Preparing for a product launch
- Feature release
Example prompts
- “/product-launch-checklist”
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Product Launch Checklist loads about 2.3k tokens when it runs, and up to ~5k if it reads all its reference files. Until then it costs about 83 tokens; SKILL.md has 1,176 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 1,176 words, ~2,261 tokens.
Download SKILL.mdSave it as
.claude/skills/product-launch-checklist/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- product-launch-checklist
- description
- 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.
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, 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 (brain/) exists, use it before asking:
- Read first: the
entities/feature being launched and relateddecisions/(scope, dates, owners). - Write after: log launch decisions and owners to
decisions/. This skill can also hand the checklist toaction-runnerto file the tickets — which records what was actually done back to the brain, closing the loop.
How to Use This Skill
Provide:
- Launch name and date
- Launch tier (1 = major, 2 = feature, 3 = incremental)
- Team members and their roles
The skill generates a tiered checklist. Tier 3 launches use only the Essentials section. Tier 2 adds Marketing & Comms. Tier 1 uses all sections.
Output Format
Launch Checklist — [Feature/Product Name] — Target Date: [Date]
Launch Tier: [1 / 2 / 3] Launch Owner: [PM Name] Engineering Lead: [Name] Go/No-Go Decision By: [Date and time — typically 24 hours before launch]
🔧 PRE-LAUNCH — Engineering & Product (T-2 weeks)
- Feature flag created and tested in staging
- All acceptance criteria signed off by PM
- Code reviewed and merged to main
- QA sign-off completed (regression + new feature)
- Performance testing completed (load, latency)
- Security review completed (if data or auth changes)
- Rollback procedure documented and tested
- Monitoring and alerting configured
- Error logging in place with correct severity levels
- Database migrations tested on staging with production data volume
📢 PRE-LAUNCH — Marketing & Comms (T-1 week)
- Blog post written, reviewed, and scheduled
- In-app announcement or tooltip configured
- Email campaign drafted and QA'd
- Social media posts drafted and scheduled
- Landing page or feature page live in staging
- Press outreach sent (Tier 1 only)
- Product Hunt / community posts prepared (Tier 1 only)
🎓 PRE-LAUNCH — Sales & Support (T-1 week)
- Sales enablement one-pager completed
- FAQ document shared with sales and support teams
- Help centre articles written and published
- Support team demo / training completed
- Customer success team briefed on top accounts
- Pricing updated (if applicable)
- Contracts / ToS updated (if applicable)
📊 PRE-LAUNCH — Analytics (T-1 week)
- Analytics events firing correctly in staging
- Dashboard configured for launch metrics
- Baseline metrics documented
- Success criteria documented and shared with team
- A/B test configured (if applicable)
✅ GO / NO-GO DECISION — T-24 hours
| Criteria | Status | Owner |
|---|---|---|
| All critical bugs resolved | 🟢 / 🔴 | Eng Lead |
| QA sign-off complete | 🟢 / 🔴 | QA |
| Rollback tested | 🟢 / 🔴 | Eng Lead |
| Help centre articles live | 🟢 / 🔴 | Support |
| Monitoring active | 🟢 / 🔴 | Eng Lead |
| PM sign-off | 🟢 / 🔴 | PM |
Go / No-Go Decision: [GO / NO-GO] Decision Owner: [PM + Eng Lead jointly]
🚀 LAUNCH DAY
- Feature flag enabled for [X%] of users (start low — 5–10%)
- Launch confirmed in team Slack/channel
- Metrics dashboard open and being monitored
- Error rate checked at T+15 min, T+1 hr, T+4 hr
- Blog post published / email sent
- Social posts live
- Support team on standby for first 4 hours
- PM available and reachable all day
- Feature flag expanded to 50% if T+2hr checks pass
- Feature flag expanded to 100% if T+4hr checks pass
📈 POST-LAUNCH (D+7, D+30)
- D+7 metrics review: adoption, errors, support tickets
- D+7 customer feedback synthesised
- Retrospective scheduled
- Learnings documented
- D+30 success metrics reviewed against targets
- Feature flag removed from codebase (clean up)
- Follow-up features added to backlog based on feedback
Deeper Materials
This skill ships with support files — use them when they are available:
references/launch-tiering.md— Launch Tiering: Matching Ceremony to Stakes. Apply it while producing the output; it carries the calibration and judgment calls the method summary above compresses.templates/launch-plan.md— a fill-in version of the deliverable with the quality gates inline. Offer it when the user wants to work the document themselves rather than have it generated.
Show full SKILL.md (469 more words)Show less
Scoring Rubric (0–40)
Score any output of this skill before handing it over; 32+ is ship-quality.
| Dimension | 0 | 5 | 10 |
|---|---|---|---|
| Tier calibration | No tier stated, or checklist depth obviously mismatched (full Tier 1 ceremony for a copy tweak, or a bare list for a new revenue line) | Tier stated but not justified; some sections included or dropped inconsistently with the tier | Tier stated with the reasoning (pricing, legal, blast radius — not engineering effort), sections match the tier, and any tier disagreement is resolved on record |
| Ownership & timing | Items and gates owned by "the team" or nobody; no dates | Most items have owners but key gates (Go/No-Go, expansions, retro) lack a named individual or a specific time | Every checklist item, gate, and decision has one named individual and a date/time, including the Go/No-Go decision time set ~24h before launch |
| Rollback & staged rollout | No rollback plan, or flag flips to 100% on day one | Rollback documented but untested; staging exists but expansion steps have no pass criteria | Rollback tested with a known revert time ("X minutes, tested on [date]"), flag staged 5–10% → 50% → 100%, and each expansion gated on specific named checks |
| Go/No-Go integrity | No gate, or a gate that is theatre — everything green by default, blocked work checked off | Gate exists with criteria, but blocked items are softened, statuses aspirational, or a NO-GO has no revised plan | Honest statuses (reds shown with blocker and owner), the decision follows the table even when that means slipping, and a NO-GO produces a dated re-gate — plus the retro booked at launch time |
Quality Checks
- Launch tier confirmed before generating checklist (scope determines depth)
- Go/No-Go decision has a named owner and a specific decision time
- Rollback procedure is documented and tested (not just planned)
- Feature flag expansion is staged (5% → 50% → 100%), not all-at-once
- Post-launch retrospective is scheduled at launch time
Anti-Patterns
- Do not apply a Tier 1 checklist to an incremental update — tier the launch appropriately before generating the checklist
- Do not launch on a Friday without confirmed weekend engineering coverage
- Do not leave the Go/No-Go decision owner as "the team" — it must be a named individual
- Do not skip the rollback plan for Tier 1 and 2 launches — know the revert time before going live
- Do not close the launch without scheduling the post-launch retrospective — it must be booked at launch time, not after
Guidelines
- The Go/No-Go decision must have a named owner — "the team" is not an owner
- Never launch on a Friday unless you have weekend engineering coverage
- Recommend starting all launches at <10% traffic — even for simple features
- Document rollback time: "We can revert this in X minutes" should be known before launch
Example Trigger Phrases
- "Prepare for a product launch."
- "Give me a launch-day checklist."
- "Plan the feature release."
- "What do we need before this major update ships?"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in skills/product-launch-checklist of mohitagw15856/pm-claude-skills.
- SKILL.md
- references/launch-tiering.md
- references/worked-example.md
- templates/launch-plan.md
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Product Launch Checklist next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Product Launch Checklist this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Technical Launch Plannerjamesrochabrun/skills | 216 | 1 repos | ~3.8k | Automated safety check: Pass | MIT | |
| Getxapi ConnectLeoYeAI/openclaw-marketing-skills | 1k | 1 repos | ~715 | Automated safety check: Pass | Custom licence | |
| ProducthuntReScienceLab/opc-skills | 1.8k | — | ~467 | Automated safety check: Pass | Apache-2.0 | |
| Micro SaaS Launchernicepkg/auto-company | 195 | 8 repos | ~1.3k | Automated safety check: Pass | None | |
| Directory Submissionscoreyhaines31/marketingskills | 54k | 2 repos | ~6.7k | Automated safety check: Pass | MIT |
Similar skills
Getxapi Connect
LeoYeAI/openclaw-marketing-skills
Connect GetXAPI to pull public X/Twitter marketing signals into OpenClaw workflows.
Producthunt
ReScienceLab/opc-skills
Search and retrieve content from Product Hunt. An agent skill from ReScienceLab/opc-skills.
Micro SaaS Launcher
nicepkg/auto-company
Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software.
Directory Submissions
coreyhaines31/marketingskills
When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery.
Producthunt
FoundDream/miniclawd
Discover trending tech products, apps, and tools from Product Hunt.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Product Launch Checklist
What does Product Launch Checklist do?
Generate a comprehensive pre-launch, launch day, and post-launch checklist for any product release. Product Launch Checklist is an agent skill from mohitagw15856/pm-claude-skills. Generate a comprehensive pre-launch, launch day, and post-launch checklist for any product release.
When should I use Product Launch Checklist?
Product Launch Checklist fits situations like: preparing for a product launch; feature release.
How do I install Product Launch Checklist in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill product-launch-checklist -a claude-code`. Or copy the skill folder (skills/product-launch-checklist in mohitagw15856/pm-claude-skills) into .claude/skills/product-launch-checklist in your project. Claude Code loads it when a task matches its description.
How do I install Product Launch Checklist in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill product-launch-checklist -a codex`. Or copy the skill folder (skills/product-launch-checklist in mohitagw15856/pm-claude-skills) into .agents/skills/product-launch-checklist in your project. Codex loads it when a task matches its description.
Can I use Product Launch Checklist in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill product-launch-checklist -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/product-launch-checklist, .gemini/skills/product-launch-checklist, .github/skills/product-launch-checklist and .opencode/skills/product-launch-checklist in your project.
What does Product Launch Checklist need to run?
SKILL.md names no scripts, command-line tools or credentials: Product Launch Checklist is instructions for the agent only.
Does Product Launch Checklist access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Product Launch Checklist safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Product Launch Checklist use?
Product Launch Checklist is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Product Launch Checklist use?
About 2.3k tokens (SKILL.md is roughly 9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.7k tokens, read only when the agent opens those files.
What are the alternatives to Product Launch Checklist?
Skills that share tags, products or a category with Product Launch Checklist: Technical Launch Planner (jamesrochabrun/skills, 216 stars), Getxapi Connect (LeoYeAI/openclaw-marketing-skills, 1k stars), Producthunt (ReScienceLab/opc-skills, 1.8k stars) and Micro SaaS Launcher (nicepkg/auto-company, 195 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Product Launch Checklist?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.