Installs just this skill. Get the whole plugin for auto-invocation.
⚡ How it fires
How this skill gets triggered: by you, by Claude, or both.
Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/skill-ship
👁️ Context preview
The summary Claude sees to decide when to auto-load this skill.
Package and finalize completed work for delivery — use when a feature is done and ready to ship
📊 Stats
Stars3,869
Forks362
LanguageShell
LicenseMIT
📦 Ships with octo
</> SKILL.md
skill-ship.SKILL.md
---name: skill-ship
user-invocable: true
description: "Package and finalize completed work for delivery — use when a feature is done and ready to ship"
trigger: |
AUTOMATICALLY ACTIVATE when user mentions:
- "ship" or "deliver" or "finalize"
- "done" or "complete the project"
invocation: human_only
---# Ship Project - Multi-AI Delivery Validation
Finalize and deliver completed work with Multi-AI security audit, lessons capture, and archival.
**Core principle:** Verify ready -> Multi-AI audit -> Capture lessons -> Archive -> Ship.
---## When to Use
**Use this skill when user asks:**
- "Ship the project" or "We're done"
- "Finalize this" or "Let's deliver"
- "Complete the project" or "Ready to ship"
- "Mark as shipped" or "Time to deliver"
**Do NOT use for:**
- Code review (use /octo:review or flow-deliver)
- Implementation (use /octo:develop)
- Research (use /octo:research)
---## The Process
"${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh" ink "Security audit for delivery - comprehensive review of all code changes for production readiness"
```
## MANDATORY COMPLIANCE
**CRITICAL: You are PROHIBITED from:**
- Skipping Multi-AI validation
- Doing single-provider analysis instead
- Claiming you're "simulating" the audit
- Proceeding without running orchestrate.sh
#### Step 3: Verify Audit Completed
```bash
# Find the latest validation file
VALIDATION_FILE=$(find ~/.claude-octopus/results -name "ink-validation-*.md" -mmin -10 2>/dev/null | head -n1)
if [[ -z "$VALIDATION_FILE" ]]; then
echo "AUDIT FAILED: No validation file found"
exit 1
fi
echo "AUDIT COMPLETE: $VALIDATION_FILE"
```
#### Step 4: Display Audit Summary
Read validation file and present:
- Overall status (PASSED / PASSED WITH WARNINGS / FAILED)
- Quality score
- Critical issues (must fix before ship)
- Warnings (should fix)
**If FAILED with critical issues:**
```markdown
## Audit Failed - Cannot Ship
Critical issues must be resolved before shipping:
1. [Issue 1 from validation]
2. [Issue 2 from validation]
Resolve issues and run `/octo:ship` again.
```
**STOP if critical issues found.**
---
### Phase 3: Capture Lessons Learned
#### Step 1: Ask User for Lessons
```markdown
## Lessons Learned
Before finalizing, let's capture what we learned from this project.
**Please answer the following:**
1. **What went well?** (What worked better than expected?)
2. **What could improve?** (What would you do differently?)
3. **Key learnings?** (What insights will you carry forward?)
*Reply with your answers, or type "skip" to proceed without capturing lessons.*
