davidtheproduct

critic

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.

ship-pr

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 with a GitHub remote - a bug fix, a small feature, a doc edit, a dependency bump. For 3+ independently shippable PRs from one analysis pass, see parallel-ship. For sequential phases where each PR builds on the last, see epic-ship.

epic-ship

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 epic". For a single change use ship-pr; for independent parallel PRs use parallel-ship.

parallel-ship

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 files, in any repo. For a single PR use ship-pr; for sequential dependent phases use epic-ship.