project-shipper 1.0.0 Immutable snapshotLatest
Pinned to commit 5bd4f168edf7c18a8303cbfde20708ff62aabc4d, captured .
Download 1.0.0 source archive Choose something to compare with View commit on GitHub
More actions and subscriptions
Current package description (not historical)
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: "…
Install
This version is listed in the verified marketplace awesome-claude-code-plugins (repository ccplugins/awesome-claude-code-plugins). Run these in Claude Code, in order:
- Add the marketplace
/plugin marketplace add ccplugins/awesome-claude-code-plugins - Install the plugin
/plugin install project-shipper@awesome-claude-code-plugins
These commands install the marketplace's current upstream state, not the pinned commit snapshot on this page; the two can differ.
Contents 1
Agent1
-
project-shipper
plugins/project-shipper/agents/project-shipper.mdPermalink
Nothing matches.
Dependencies, compatibility and skill declarations
Recorded dependencies 0
No dependency requirements were recorded from plugin.json or marketplace entries. Only manifest fields saved with the snapshot are shown here; dependency declarations in other files are outside the current collection scope.
Recorded compatibility
No compatibility requirement was recorded for this snapshot from plugin.json or a marketplace entry. Only manifest fields saved with the snapshot are shown here. Declarations in a skill's SKILL.md header are collected separately and, when present, shown on their own under “Skill file declarations”; they never overwrite or fill in this value.