Feature Launch Playbook
gooseworks-ai/goose-skills
Take a new feature or product update and generate the full launch kit: changelog entry, email announcement, LinkedIn post variants, in-app banner text, Twitter/X thread, and internal sales…
Turn a release-readiness argument into one typed decision — ship, ship reduced, or slip — with a defined state, defined options, and a probability for each.
Install Ship Or Slip
$ npx skills add mohitagw15856/pm-claude-skills --skill ship-or-slip -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills ship-or-slip --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/ship-or-slip .claude/skills/ship-or-slip && 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 "ship-or-slip" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/ship-or-slip into .claude/skills/ship-or-slip/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-or-slip", 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/ship-or-slipType 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 ship-or-slip -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills ship-or-slip --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/ship-or-slip .agents/skills/ship-or-slip && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ship-or-slip" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/ship-or-slip into .agents/skills/ship-or-slip/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-or-slip", 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 ship-or-slip -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills ship-or-slip --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/ship-or-slip .cursor/skills/ship-or-slip && 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 "ship-or-slip" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/ship-or-slip into .cursor/skills/ship-or-slip/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-or-slip", 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/ship-or-slip--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 ship-or-slip -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills ship-or-slip --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/ship-or-slip .gemini/skills/ship-or-slip && 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 "ship-or-slip" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/ship-or-slip into .gemini/skills/ship-or-slip/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-or-slip", 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 ship-or-slipInstalls 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 ship-or-slip -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/ship-or-slip .github/skills/ship-or-slip && 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 "ship-or-slip" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/ship-or-slip into .github/skills/ship-or-slip/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-or-slip", 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 ship-or-slip -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 ship-or-slip --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/ship-or-slip .opencode/skills/ship-or-slip && 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 "ship-or-slip" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/ship-or-slip into .opencode/skills/ship-or-slip/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-or-slip", 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
ship-or-slip- GitHub stars
- 1.4k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 664 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Turn a release-readiness argument into one typed decision — ship, ship reduced, or slip — with a defined state, defined options, and a probability for each.
- Asked should we ship Friday
- SKILL.md covers Where this sits, What This Skill Produces, Required Inputs and Framework: A Typed Decision, plus 4 more sections
- Calls node
- Are we ready to release
What it does
Ship Or Slip is an agent skill from mohitagw15856/pm-claude-skills. Turn a release-readiness argument into one typed decision — ship, ship reduced, or slip — with a defined state, defined options, and a probability for each. Use when asked should we ship Friday, are we ready to release, do we slip the date, go/no-go for the release, or when a launch checklist is done and someone still has to call it. Produces a filled release state, the three-way decision with probabilities and confidence, the act-or-hold verdict against the thresholds, and the one fact that would flip it.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Feature launches and release readiness and 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
- Asked should we ship Friday
- Are we ready to release
- Do we slip the date
- Go/no-go for the release
Example prompts
- “/ship-or-slip”
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
Shell commands in SKILL.md call:
node
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
Ship Or Slip loads about 1.3k tokens when it runs. Until then it costs about 131 tokens; SKILL.md has 664 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). 664 words, ~1,307 tokens.
Download SKILL.mdSave it as
.claude/skills/ship-or-slip/SKILL.md (or your agent's skills folder).- name
- ship-or-slip
- description
- Turn a release-readiness argument into one typed decision — ship, ship reduced, or slip — with a defined state, defined options, and a probability for each. Use when asked should we ship Friday, are we ready to release, do we slip the date, go/no-go for the release, or when a launch checklist is done and someone still has to call it. Produces a filled release state, the three-way decision with probabilities and confidence, the act-or-hold verdict against the thresholds, and the one fact that would flip it.
- version
- 1.0.0
Ship or Slip
A go/no-go meeting is a decision pretending to be a discussion. This skill makes the decision typed: the release state is written down in a fixed schema, the three possible answers are defined before anyone argues, and the output is a probability for each option, not a paragraph. A program can act on the result; a person can overrule it, on the record.
Where this sits
After product-launch-checklist and launch-readiness have produced the evidence. Those skills gather; this one decides.
What This Skill Produces
- The release state — the six fields below, filled from evidence, gaps marked
unknown - The decision —
ship/ship_reduced/slip, with a probability for each option and a confidence score - Act or hold — whether the decision clears the thresholds (act) or goes back to the release owner (hold), and why
- The flip fact — the single unknown that, if resolved, would change the answer
- The record line — one line for the release log: decision, probabilities, who overruled (if anyone)
Required Inputs
Ask for these if not provided; never invent them:
- release — name and target date
- open_blockers — count and one line each: severity, owner, ETA
- test_status — pass rate, flaky count, when the last green build was
- rollback — tested or not, and time to roll back
- customer_commitments — who was promised what, by when
- scope_cuttable — what could be dropped without breaking the promise
Framework: A Typed Decision
The options are fixed, so the argument is about the state, not the answer.
| Option | It applies when |
|---|---|
ship | No open severity-1 blocker, rollback tested, tests green — the date holds and the residual risk is named |
ship_reduced | The promised core is ready but a non-core item is red — ship without it and say so to whoever was promised it |
slip | A severity-1 blocker, an untested rollback, or a red core path — the date moves, because slipping is cheaper than a bad release |
Thresholds. Act automatically only when confidence ≥ 0.6 and the winning option's probability ≥ 0.7. Otherwise hold: present the distribution to the release owner with the two closest options and the fact that separates them.
How to get probabilities. Any calibrated decision model that answers a defined multiple-choice question with a probability per option works — the contract is the state schema and the options above. The repo ships a ready adapter: node integrations/jev/decide.mjs ship-or-slip --state state.json (contract in integrations/jev/decisions/ship-or-slip.json). Without a model, the assistant estimates the distribution itself and labels it as an estimate.
Reading the distribution. 0.55 ship / 0.40 slip is not "ship". It is a hold with one question: what makes the 0.40? A distribution that moves when one field changes tells you which field to go verify.
Show full SKILL.md (226 more words)Show less
Output Format
Ship or slip: [release] · target [date]
State
| Field | Value |
|---|---|
| open_blockers | … |
| test_status | … |
| rollback | … |
| customer_commitments | … |
| scope_cuttable | … |
Decision
| Option | Probability |
|---|---|
| ship | 0.xx |
| ship_reduced | 0.xx |
| slip | 0.xx |
Confidence: 0.xx · Source: [model name / assistant estimate]
Verdict: [act: option] or [hold — closest: a vs b]
Flip fact: [the one unknown; who can answer it by when]
Record line: [date] [release] → [option] (p=0.xx, conf=0.xx) · overruled by: [none / name, reason]
Quality Checks
- Every state field is filled from evidence or marked
unknown— no invented test numbers - The three options are used exactly as defined; no fourth option invented mid-meeting
- Probabilities are shown for all options and sum to about 1
- The act/hold verdict cites the thresholds explicitly
- The flip fact names an owner and a time
- A hold result does not quietly become a ship
Anti-Patterns
- Deciding in prose — "we feel good about it" is not a decision anyone can audit
- Moving the options — adding "ship dark" at the last minute to avoid a slip
- Treating 0.55 as a yes — a close call is a hold, by definition
- Hiding the overrule — a human may overrule; the record must say so
- Letting the model own it — the release owner owns the decision; the distribution is evidence
Example Trigger Phrases
- "Should we ship on Friday or slip a week?"
- "Go/no-go for the 3.2 release — here's the state."
- "Two blockers open, rollback untested — call it."
© 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
Just SKILL.md in skills/ship-or-slip of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Ship Or Slip 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 |
|---|---|---|---|---|---|---|
| Ship Or Slip this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Feature Launch Playbookgooseworks-ai/goose-skills | 1.2k | 1 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Feature Launch Playbookrampstackco/claude-skills | 945 | — | ~6.6k | Automated safety check: Pass | MIT | |
| Sealeap Amazon New Product Launch Planxjli360/sealeap-amazon-skills | 251 | — | ~548 | Automated safety check: Pass | MIT | |
| Early Access Designeraaron-he-zhu/aaron-marketing-skills | 2.9k | — | ~3.4k | Automated safety check: Pass | Apache-2.0 | |
| Mvp Launchooiyeefei/ccc | 495 | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Feature Launch Playbook
rampstackco/claude-skills
The operational playbook for launching a feature well. An agent skill from rampstackco/claude-skills.
Sealeap Amazon New Product Launch Plan
xjli360/sealeap-amazon-skills
Create a quantified Amazon new-product launch plan by translating a sales target into comparable-product benchmarks, keyword economics, budget scenarios, milestones, and stop-loss rules.
Early Access Designer
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "design an early access program", "set up a waitlist and beta stages", or "define beta graduation criteria"; produces a waitlist→concept→alpha→beta→GA…
Mvp Launch
ooiyeefei/ccc
Web app MVP launch checklist knowledge. An agent skill from ooiyeefei/ccc.
60 Launch Playbook Global
minhnv0807/ai-business-skills
A skill your agent uses when a launch needs a repeatable EXECUTION playbook — a T-30 to D+7 timeline, per-function checklists for content, design, ads, sales, and engineering, a launch-day war room…
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 Ship Or Slip
What does Ship Or Slip do?
Turn a release-readiness argument into one typed decision — ship, ship reduced, or slip — with a defined state, defined options, and a probability for each. Ship Or Slip is an agent skill from mohitagw15856/pm-claude-skills. Turn a release-readiness argument into one typed decision — ship, ship reduced, or slip — with a defined state, defined options, and a probability for each.
When should I use Ship Or Slip?
Ship Or Slip fits situations like: asked should we ship Friday; are we ready to release; do we slip the date; go/no-go for the release.
How do I install Ship Or Slip in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill ship-or-slip -a claude-code`. Or copy the skill folder (skills/ship-or-slip in mohitagw15856/pm-claude-skills) into .claude/skills/ship-or-slip in your project. Claude Code loads it when a task matches its description.
How do I install Ship Or Slip in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill ship-or-slip -a codex`. Or copy the skill folder (skills/ship-or-slip in mohitagw15856/pm-claude-skills) into .agents/skills/ship-or-slip in your project. Codex loads it when a task matches its description.
Can I use Ship Or Slip 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 ship-or-slip -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ship-or-slip, .gemini/skills/ship-or-slip, .github/skills/ship-or-slip and .opencode/skills/ship-or-slip in your project.
What does Ship Or Slip need to run?
Going by SKILL.md and its folder, Ship Or Slip needs the command-line tools its instructions call (node).
Does Ship Or Slip 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 Ship Or Slip 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 Ship Or Slip use?
Ship Or Slip 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 Ship Or Slip use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Ship Or Slip?
Skills that share tags, products or a category with Ship Or Slip: Feature Launch Playbook (gooseworks-ai/goose-skills, 1.2k stars), Feature Launch Playbook (rampstackco/claude-skills, 945 stars), Sealeap Amazon New Product Launch Plan (xjli360/sealeap-amazon-skills, 251 stars) and Early Access Designer (aaron-he-zhu/aaron-marketing-skills, 2.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ship Or Slip?
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.