Initial commit

plugin.lock.json

@@ -0,0 +1,45 @@
+{
+  "$schema": "internal://schemas/plugin.lock.v1.json",
+  "pluginId": "gh:claudeforge/marketplace:plugins/agents/project-shipper",
+  "normalized": {
+    "repo": null,
+    "ref": "refs/tags/v20251128.0",
+    "commit": "cebb8fd6a0296da4d700de375d9fafd173b53d0f",
+    "treeHash": "ebfe421abe9ea083838673ec4dc4ecf377adb63f33abfed0bc7ee489074079c8",
+    "generatedAt": "2025-11-28T10:15:17.771953Z",
+    "toolVersion": "publish_plugins.py@0.2.0"
+  },
+  "origin": {
+    "remote": "git@github.com:zhongweili/42plugin-data.git",
+    "branch": "master",
+    "commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390",
+    "repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data"
+  },
+  "manifest": {
+    "name": "project-shipper",
+    "description": "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>",
+    "version": "1.0.0"
+  },
+  "content": {
+    "files": [
+      {
+        "path": "README.md",
+        "sha256": "94a35fea225091fbcff0203813061e7e30ce14dab20402e9c4c9887e8fe685dc"
+      },
+      {
+        "path": "agents/project-shipper.md",
+        "sha256": "fa9bf9d49ce1c0dea8cc6488ef7ba611f326e4db042690de313df1fcada1df19"
+      },
+      {
+        "path": ".claude-plugin/plugin.json",
+        "sha256": "a050f760207b1eac200530bf67e9d55bbb21ec63c5d7dc27ddcd708ab8231c75"
+      }
+    ],
+    "dirSha256": "ebfe421abe9ea083838673ec4dc4ecf377adb63f33abfed0bc7ee489074079c8"
+  },
+  "security": {
+    "scannedAt": null,
+    "scannerVersion": null,
+    "flags": []
+  }
+}