Claude Code skills for shipping: single PRs, parallel PR fan-out, multi-phase epics, and a ruthless pre-ship critic. One session chairs; context never splits.
davidtheproduct/claude-ship-skills
Skill Claude Code
Use when someone asks to critique, challenge, tear apart, stress-test, review, or find flaws in positioning, messaging, outreach, landing pages, USP, competitive positioning, GTM strategy, or any customer-facing work.
davidtheproduct/claude-ship-skills
Skill Claude CodeCodex
Execute a multi-phase epic end to end - one worktree and PR per phase, verified before merge, merged and cleaned up immediately, moving straight to the next phase without stalling for a prompt. Use when asked to run, ship, drive, or execute an epic (a phased plan doc), or "ship the epic", "run phase M", "continue the…
davidtheproduct/claude-ship-skills
Skill Claude CodeCodex
Ship 3+ related PRs in one session by fanning out background agents from the session that holds the analysis context - instead of writing a plan, generating a handoff prompt, and spinning up fresh sessions. Use when one piece of analysis or design work produces several independently shippable PRs across disjoint…
davidtheproduct/claude-ship-skills
Skill Claude Code
Ship a single change through a worktree -> branch -> PR -> squash-merge -> cleanup workflow - pick the right branch type (feat/fix/chore/docs/hotfix), implement, verify with this repo's real build/typecheck/test commands, open the PR, check CI, merge, and clean up. Use for any single PR-sized change in any git repo…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: