AGENT SKILL

skill-ship

Package and finalize completed work for delivery — use when a feature is done and ready to ship

License 许可
Apache-2.0
最近更新
2026-11-14
Stars
★ 1.6k
Forks
491

01 前言 Front Matter

name
skill-ship
description
Package and finalize completed work for delivery — use when a feature is done and ready to ship
disable-model-invocation
true

02 资源文件 1

03 SKILL.md 正文

Host: Codex CLI — This skill was designed for Claude Code and adapted for Codex. Cross-reference commands use installed skill names in Codex rather than /octo:* slash commands. Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it. For host tool equivalents, see skills/blocks/codex-host-adapter.md.

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

Phase 1: Verify Project Ready to Ship

Step 1: Check .octo/ Exists

if [[ ! -d ".octo" ]]; then
    echo "No project initialized"
    exit 1
fi

If .octo/ does not exist:

## Cannot Ship

**Status:** No project initialized

No Claude Octopus project found in this directory.

Run `/octo:embrace [description]` to start a new project.

STOP. Do not proceed.

Step 2: Read STATE.md Status

# Check if STATE.md exists and read status
if [[ -f ".octo/STATE.md" ]]; then
    # Read current status
    STATUS=$(grep -E "^status:" .octo/STATE.md | cut -d':' -f2 | xargs || echo "unknown")
    CURRENT_PHASE=$(grep -E "^current_phase:" .octo/STATE.md | cut -d':' -f2 | xargs || echo "unknown")
else
    STATUS="unknown"
    CURRENT_PHASE="unknown"
fi

echo "Status: $STATUS"
echo "Current Phase: $CURRENT_PHASE"

Step 3: Validate Ready State

Ship is allowed when:

  • status = "complete" OR
  • current_phase = "4" (Deliver phase) OR
  • All four phases have entries in STATE.md history

If not ready:

## Project Not Ready to Ship

**Current Status:** {status}
**Current Phase:** {current_phase}

### To prepare for shipping:

1. Complete remaining phases:
   - [ ] Phase 1: Discover - Use `/octo:discover`
   - [ ] Phase 2: Define - Use `/octo:define`
   - [ ] Phase 3: Develop - Use `/octo:develop`
   - [ ] Phase 4: Deliver - Use `/octo:deliver`

2. Or override with: "ship anyway" (not recommended)

STOP unless user says "ship anyway".

Phase 2: Multi-AI Security Audit

Step 1: Display Visual Indicators

# Check provider availability
command -v codex &> /dev/null && codex_status="Available" || codex_status="Not installed"
command -v agy &> /dev/null && agy_status="Available" || agy_status="Not installed"

Output:

## Multi-AI Security Audit

**Providers:**
- Codex CLI: ${codex_status} - Code security analysis
- Antigravity CLI: ${agy_status} - Additional external-model challenge
- Claude: Available - Synthesis and final validation

**Estimated Time:** 3-5 minutes
**Estimated Cost:** 0.02-0.08 USD

Step 2: Execute orchestrate.sh Security Audit

You MUST execute this via native shell command tool:

Use the installation that loaded this skill for both execution and validation. If CLAUDE_PLUGIN_ROOT is absent, replace the OCTO_ROOT fallback below with the absolute plugin root derived from this loaded skill's path. Do not infer it from the project directory or an existing stable link. The root helper refreshes installed copies while preserving another session's working root when called from an inferred development checkout.

# Run Multi-AI security audit for delivery
OCTO_ROOT="${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_ROOT:-${HOME}/.claude-octopus/plugin}}"
bash "$OCTO_ROOT/scripts/helpers/ensure-plugin-root.sh" || exit 1
RUN_MARKER=$(mktemp) || exit 1
RUN_STATUS=0
OCTOPUS_WORKFLOW_INVOCATION_ID="${RUN_MARKER##*/}" "$OCTO_ROOT/scripts/orchestrate.sh" ink "Security audit for delivery - comprehensive review of all code changes for production readiness" || RUN_STATUS=$?
REPORT_STATUS=0
VALIDATION_FILE=$("$OCTO_ROOT/scripts/helpers/workflow-result.sh" ink "$RUN_MARKER" "$RUN_STATUS") || REPORT_STATUS=$?
rm -f "$RUN_MARKER"
[[ "$REPORT_STATUS" == 0 ]] || exit "$REPORT_STATUS"
echo "AUDIT COMPLETE: $VALIDATION_FILE"

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

Step 2 must exit successfully and validate a fresh delivery-*.md report whose launcher status is COMPLETE. A report from a previous deliver run, a partial report, or a failed command cannot pass this audit. Use the exact validated path printed by Step 2 for the summary.

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:

## 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

## 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.*

Wait for user response.

Step 2: Append to LESSONS.md

If user provides lessons (not "skip"):

# Generate timestamp
TIMESTAMP=$(date '+%Y-%m-%d')

# Ensure LESSONS.md exists
touch .octo/LESSONS.md

# Append lessons
cat >> .octo/LESSONS.md << EOF

## ${TIMESTAMP} - Project Delivery

### What Went Well
- ${USER_WHAT_WENT_WELL}

### What Could Improve
- ${USER_WHAT_COULD_IMPROVE}

### Key Learnings
- ${USER_KEY_LEARNINGS}

EOF

Count total lessons:

LESSON_COUNT=$(grep -c "^## " .octo/LESSONS.md 2>/dev/null || echo "0")
echo "Total lessons captured: $LESSON_COUNT"

Phase 4: Archive Project State

Step 1: Create Archive Directory

# Generate timestamp for archive
ARCHIVE_TIMESTAMP=$(date +%Y%m%d-%H%M%S)
ARCHIVE_DIR=".octo/archive/${ARCHIVE_TIMESTAMP}"

# Create archive directory
mkdir -p "$ARCHIVE_DIR"

Step 2: Copy State Files to Archive

# Archive STATE.md if exists
if [[ -f ".octo/STATE.md" ]]; then
    cp .octo/STATE.md "$ARCHIVE_DIR/"
fi

# Archive PROJECT.md if exists
if [[ -f ".octo/PROJECT.md" ]]; then
    cp .octo/PROJECT.md "$ARCHIVE_DIR/"
fi

# Archive ROADMAP.md if exists
if [[ -f ".octo/ROADMAP.md" ]]; then
    cp .octo/ROADMAP.md "$ARCHIVE_DIR/"
fi

# Archive ISSUES.md if exists
if [[ -f ".octo/ISSUES.md" ]]; then
    cp .octo/ISSUES.md "$ARCHIVE_DIR/"
fi

echo "Archived to: $ARCHIVE_DIR"

IMPORTANT: NEVER archive LESSONS.md - lessons are preserved across projects.

Step 3: Verify Archive

# List archived files
ls -la "$ARCHIVE_DIR"

Phase 5: Create Delivery Summary

Step 1: Update STATE.md

# Update status to shipped
sed -i '' 's/^status:.*/status: shipped/' .octo/STATE.md 2>/dev/null || \
    sed -i 's/^status:.*/status: shipped/' .octo/STATE.md

# Append history entry
cat >> .octo/STATE.md << EOF

## History - $(date '+%Y-%m-%d %H:%M')

- **Event:** Project shipped
- **Archive:** .octo/archive/${ARCHIVE_TIMESTAMP}/
- **Validation:** ${VALIDATION_FILE}

EOF

Step 2: Create Shipped Checkpoint

# Create git checkpoint tag
CHECKPOINT_TAG="octo-checkpoint-shipped-${ARCHIVE_TIMESTAMP}"

git tag -a "$CHECKPOINT_TAG" -m "Project shipped - $(date '+%Y-%m-%d %H:%M:%S')"

echo "Checkpoint created: $CHECKPOINT_TAG"

Step 3: Count Metrics

# Count resolved issues
ISSUES_RESOLVED=$(grep -c "^\- \[x\]" .octo/ISSUES.md 2>/dev/null || echo "0")

# Count total lessons
LESSONS_COUNT=$(grep -c "^## " .octo/LESSONS.md 2>/dev/null || echo "0")

echo "Issues resolved: $ISSUES_RESOLVED"
echo "Lessons captured: $LESSONS_COUNT"

Phase 6: Display Completion

Present final summary:

## Project Shipped!

**Delivered:** {timestamp}
**Phases Completed:** 4/4
**Issues Resolved:** {ISSUES_RESOLVED}
**Lessons Captured:** {LESSONS_COUNT}

### Multi-AI Audit Summary

- **Security Score:** {score}/100
- **Quality Score:** {score}/100
- **Providers Used:** Claude plus available external providers

### Archive

Location: `.octo/archive/{ARCHIVE_TIMESTAMP}/`

Contents:
- STATE.md
- PROJECT.md
- ROADMAP.md
- ISSUES.md

### Checkpoint

Tag: `{CHECKPOINT_TAG}`

Restore with: `/octo:rollback {CHECKPOINT_TAG}`


**To start a new project:** `/octo:embrace`

*Multi-AI validation powered by Claude Octopus*
*Providers: Codex | Antigravity | Claude*

Error Handling

Error Resolution
No .octo/ directory Suggest /octo:embrace
Project not ready Show remaining phases
orchestrate.sh fails Show error logs, suggest retry
Critical audit issues Block ship, show issues
Git tag fails Warn but continue (non-blocking)

Safety Measures

Measure Implementation
Pre-ship audit orchestrate.sh Multi-AI validation required
Lessons preservation LESSONS.md never archived, always preserved
Archive before ship State files copied to archive directory
Git checkpoint Tag created for rollback capability
No file deletion Archive copies, doesn't delete source files

Integration with Other Skills

With /octo:deliver

User runs /octo:deliver to validate
→ Deliver phase complete
→ User runs /octo:ship to finalize

With /octo:rollback

User ships project
→ Checkpoint created
→ Later: /octo:rollback octo-checkpoint-shipped-*

With /octo:status

After ship: status shows "shipped"
→ Suggests /octo:embrace for new project

Red Flags - Never Do

Action Why It's Wrong
Skip Multi-AI audit Security vulnerabilities missed
Archive LESSONS.md Loses accumulated project knowledge
Delete source files Should copy, not move
Ship without ready check Incomplete work shipped
Skip checkpoint creation No rollback recovery path

Quick Reference

Step Command Purpose
1 Check .octo/STATE.md Verify ready to ship
2 orchestrate.sh ink Multi-AI security audit
3 Ask user Capture lessons learned
4 mkdir + cp Archive state files
5 Update STATE.md Mark as shipped
6 git tag Create shipped checkpoint

The Bottom Line

Ship → Ready + Audit passed + Lessons captured + Archived + Checkpoint created
Otherwise → Not shipped

Verify ready. Run Multi-AI audit. Capture lessons. Archive state. Create checkpoint. Ship.

04 同仓库更多 Skills

hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-review-with-annotations

Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-find-and-synthesize-context

Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-create-or-update-docs

Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-create-or-manage-records

Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-create-or-manage-interactive-html

Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-collaborate-threads

Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.

★ 1.6k