Prompt file imported from asabocinski/bravo-edd (
.codex/prompts/ship.md). Copyright stays with the author.
Ship Command
Archive completed feature with lessons learned (Phase 4)
Usage
/ship <define-file>
Examples
/ship .codex/sdd/features/DEFINE_NOTIFICATION_SYSTEM.md
/ship DEFINE_USER_AUTH.md
Overview
This is Phase 4 of the 5-phase AgentSpec workflow:
Phase 0: /brainstorm → .codex/sdd/features/BRAINSTORM_{FEATURE}.md (optional)
Phase 1: /define → .codex/sdd/features/DEFINE_{FEATURE}.md
Phase 2: /design → .codex/sdd/features/DESIGN_{FEATURE}.md
Phase 3: /build → Code + .codex/sdd/reports/BUILD_REPORT_{FEATURE}.md
Phase 4: /ship → .codex/sdd/archive/{FEATURE}/SHIPPED_{DATE}.md (THIS COMMAND)
The /ship command archives all feature artifacts and captures lessons learned.
What This Command Does
- Verify - Confirm all artifacts exist and build passed
- Archive - Move feature documents to archive folder
- Document - Create SHIPPED summary with lessons learned
- Clean - Remove working files from features folder
Process
Step 1: Verify Completion
Read(.codex/sdd/features/DEFINE_{FEATURE}.md)
Read(.codex/sdd/features/DESIGN_{FEATURE}.md)
Read(.codex/sdd/reports/BUILD_REPORT_{FEATURE}.md)
# Verify build report shows success
Step 2: Create Archive Folder
mkdir -p .codex/sdd/archive/{FEATURE_NAME}/
Step 3: Copy Artifacts to Archive
cp .codex/sdd/features/DEFINE_{FEATURE}.md .codex/sdd/archive/{FEATURE}/
cp .codex/sdd/features/DESIGN_{FEATURE}.md .codex/sdd/archive/{FEATURE}/
cp .codex/sdd/reports/BUILD_REPORT_{FEATURE}.md .codex/sdd/archive/{FEATURE}/
Step 4: Generate SHIPPED Document
Create summary with:
| Section | Content |
|---|---|
| Summary | What was built |
| Timeline | Start → Ship dates |
| Metrics | Lines of code, files created |
| Lessons Learned | What went well, what to improve |
| Artifacts | List of all archived documents |
Step 5: Update Document Statuses
Update archived documents to "Shipped" status:
Edit: archive/{FEATURE}/DEFINE_{FEATURE}.md
- Status: → "✅ Shipped"
- Add revision: "Shipped and archived"
Edit: archive/{FEATURE}/DESIGN_{FEATURE}.md
- Status: → "✅ Shipped"
- Add revision: "Shipped and archived"
Step 6: Clean Up Working Files
rm .codex/sdd/features/DEFINE_{FEATURE}.md
rm .codex/sdd/features/DESIGN_{FEATURE}.md
rm .codex/sdd/reports/BUILD_REPORT_{FEATURE}.md
Step 7: Save SHIPPED Document
Write(.codex/sdd/archive/{FEATURE}/SHIPPED_{DATE}.md)
Output
| Artifact | Location |
|---|---|
| SHIPPED | .codex/sdd/archive/{FEATURE}/SHIPPED_{DATE}.md |
| DEFINE | .codex/sdd/archive/{FEATURE}/DEFINE_{FEATURE}.md |
| DESIGN | .codex/sdd/archive/{FEATURE}/DESIGN_{FEATURE}.md |
| BUILD_REPORT | .codex/sdd/archive/{FEATURE}/BUILD_REPORT_{FEATURE}.md |
Next Step: Start new feature with /define
Quality Gate
Before shipping, verify:
[ ] BUILD_REPORT shows all tasks completed
[ ] No critical issues in build report
[ ] All tests passing
[ ] Code deployed (if applicable)
When to Ship
Ship when:
- All acceptance tests from DEFINE pass
- Build report shows 100% completion
- No blocking issues remain
Lessons Learned Categories
Document lessons in these areas:
| Category | Example |
|---|---|
| Process | "Breaking tasks into smaller chunks helped" |
| Technical | "Config files work better than env vars" |
| Communication | "Early clarification saved rework" |
| Tools | "Using X library simplified Y" |
Tips
- Don't Skip This - Lessons learned prevent future mistakes
- Be Honest - Document what didn't work too
- Be Specific - "Better planning" → "Create architecture diagram before coding"
- Archive Everything - Future you will thank present you
References
- Agent:
.codex/skills/ship-agent.md - Template:
.codex/sdd/templates/SHIPPED_TEMPLATE.md - Contracts:
.codex/sdd/architecture/WORKFLOW_CONTRACTS.yaml - Previous Phase:
.codex/prompts/build.md
