project-shipper — Claude Code plugin: what it does, how to install
project-shipper coordinates releases, go-to-market planning, and post-launch monitoring inside Claude Code, tailored for a 6-day development cycle.
Apache-2.0 ★ 1,013 updated 2026-08-12
/plugin marketplace add ccplugins/awesome-claude-code-plugins
/plugin install project-shipper@awesome-claude-code-pluginsWhat project-shipper does
project-shipper acts as a coordination subagent during launch milestones, release cutoffs, and go-to-market planning in Claude Code. It orchestrates steps across engineering, marketing, and support teams to keep release dates intact.
The plugin structures tasks specifically around a 6-day development cycle. It builds staggered release schedules for concurrent sprint updates, formulates messaging around user pain points, and supervises the first 48 hours following launch.
Workflows outside a six-day cadence will need manual timeline adjustments, because the agent defaults its pacing directly to that timeframe.
What it helps with
- plan a release calendar for multiple updates in a sprint
- shape feature positioning for target audiences
- coordinate team actions around a major launch
- track metrics and triage issues in the first 48 hours post-launch
Example prompts for the agent
- We are launching our creator tools next week, help coordinate the rollout
- We need to ship three updates this sprint, map out a release schedule
- The collaboration feature went live yesterday, let's track the first 48 hours
How to install project-shipper
Plugin marketplace
/plugin marketplace add ccplugins/awesome-claude-code-plugins/plugin install project-shipper@awesome-claude-code-pluginsStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about project-shipper
How to install project-shipper in Claude Code?
Add the plugin catalog by running /plugin marketplace add ccplugins/awesome-claude-code-plugins. Next, install the agent using /plugin install project-shipper@awesome-claude-code-plugins.
What does project-shipper do?
It coordinates launch preparation, designs release calendars for multiple updates, and manages post-release tracking across the first 48 hours.
What release cycle does the plugin expect?
The agent operates around a 6-day development cycle, pacing marketing and engineering checkpoints according to that timeframe.
Source text
project-shipper · Apache-2.0
PROACTIVELY use this agent when approaching launch milestones, release deadlines, or go-to-market activities. This agent specializes in coordinating launches, managing release processes, and executing go-to-market strategies within the 6-day development cycle. Should be triggered automatically when release dates are set, launch plans are needed, or market positioning is discussed. Examples:\n\n<example>\nContext: When preparing for a major feature release\nuser: "We're planning to launch the AI creator tools next week"\nassistant: "Excellent! A major feature launch requires careful coordination. Let me use the project-shipper agent to ensure all launch activities are properly orchestrated and nothing falls through the cracks."\n<commentary>\nMajor launches need comprehensive coordination across engineering, marketing, and support teams.\n</commentary>\n</example>\n\n<example>\nContext: During release planning discussions\nuser: "We need to ship three updates this sprint"\nassistant: "Managing multiple releases requires careful orchestration. I'll use the project-shipper agent to create a coordinated release calendar and ensure each update gets proper attention."\n<commentary>\nMultiple concurrent releases need strategic spacing and resource allocation.\n</commentary>\n</example>\n\n<example>\nContext: When go-to-market strategy is needed\nuser: "How should we position the new viral video features?"\nassistant: "Positioning is crucial for feature adoption. Let me use the project-shipper agent to develop a comprehensive go-to-market strategy that resonates with our target creators."\n<commentary>\nEvery feature needs a story that connects with users' aspirations and pain points.\n</commentary>\n</example>\n\n<example>\nContext: Post-launch monitoring\nuser: "The collaboration feature launched yesterday"\nassistant: "Great! The critical first 48 hours determine success. I'll use the project-shipper agent to monitor launch metrics and coordinate any necessary rapid responses."\n<commentary>\nLaunch success requires active monitoring and quick pivots based on user reception.\n</commentary>\n</example>
© Michael Galpert · Apache-2.0 · ccplugins/awesome-claude-code-plugins