luanmorenommaciel/agentspec/sdd-ship
Claude Code and agent skill by luanmorenommaciel/agentspec
- community
Checking that the SKILL.md file is still in the repository.
Archive a completed feature and close the SDD cycle (Phase 4): verify the build is truly complete, archive every phase artifact, capture lessons learned, update all phase documents to Shipped, and clean the working folders. Carries the full ship methodology — verification order, ship readiness matrix, the concrete archive procedure, status transitions, lessons-learned categories, quality gate, and the end-of-cycle handoff. Executed by ship-agent and the /ship command; loadable directly when clo…
Install
npx vskill@latest install luanmorenommaciel/agentspec/sdd-shipSKILL.md
SDD Ship — feature archival and lessons learned (Phase 4)
Ship closes the 5-phase SDD workflow: it turns a completed feature's working documents into a permanent archive with lessons learned, marks every phase document Shipped, and leaves the working folders clean for the next feature. Nothing ships unless the build is verifiably complete.
Contract
| Aspect | Value | |
|---|---|---|
| Input (required) | .claude/sdd/features/DEFINE_{FEATURE}.md · .claude/sdd/features/DESIGN_{FEATURE}.md · .claude/sdd/reports/BUILD_REPORT_{FEATURE}.md | |
| Input (optional) | .claude/sdd/features/BRAINSTORM_{FEATURE}.md (if Phase 0 was used) | |
| Output | .claude/sdd/archive/{FEATURE}/ containing all artifacts + SHIPPED_{DATE}.md | |
| Template | ${CLAUDE_PLUGIN_ROOT}/sdd/templates/SHIPPED_TEMPLATE.md — the SHIPPED document's required shape; follow it, never improvise the format | |
| Contract source | ${CLAUDE_PLUGIN_ROOT}/sdd/architecture/WORKFLOW_CONTRACTS.yaml (ship:, status_transitions:, folder_structure:, naming:) |
Naming rules (from the contracts): feature names are SCREAMING_SNAKE_CASE (e.g., USER_NOTIFICATIONS); the archive folder is .claude/sdd/archive/{FEATURE_NAME}/; the shipped file is SHIPPED_{YYYY-MM-DD}.md, dated with the ship date.
Verification order
Resolve completeness in this order before anything is archived:
Ship Readiness Matrix
| Artifacts | Tests | Issues | Confidence | Action | |
|---|---|---|---|---|---|
| All present | Pass | None | 0.95 | Ship immediately | |
| All present | Pass | Minor | 0.85 | Ship with notes | |
| All present | Fail | Any | 0.50 | Cannot ship | |
| Missing | Any | Any | 0.30 | Cannot ship |
When NOT to ship
Any of these blocks the ship — stop and route back to /build:
- BUILD_REPORT shows incomplete tasks
- Tests are failing
- Blocking issues documented in the build report
- Missing required artifacts (DEFINE, DESIGN, BUILD_REPORT)
Ship only when all acceptance tests from DEFINE pass, the build report shows 100% completion, and no blocking issues remain.
Process
Step 1 — Verify completion
Run the verification order above. Confidence below 0.85 → do not proceed.
Step 2 — Create archive folder
Step 3 — Copy artifacts to archive
If Phase 0 was used, also archive the brainstorm:
Resulting archive structure:
Step 4 — Generate SHIPPED document
Compose the SHIPPED document following ${CLAUDE_PLUGIN_ROOT}/sdd/templates/SHIPPED_TEMPLATE.md — the template owns the format; do not improvise sections. It covers the summary, timeline, metrics, what was built, success-criteria verification against DEFINE, lessons learned, recommendations, and the archived-artifact list.
Step 5 — Update document statuses
Per WORKFLOW_CONTRACTS.yaml (status_transitions, trigger /ship completes), ship MUST update ALL phase documents to Shipped — this is the contract obligation that prevents stale "Ready for X" statuses:
| File | Field | Value | |
|---|---|---|---|
DEFINE_{FEATURE}.md | Status | ✅ Shipped | |
DESIGN_{FEATURE}.md | Status | ✅ Shipped | |
BUILD_REPORT_{FEATURE}.md | Status | ✅ Shipped |
Apply the updates to the archived copies (the working copies are removed in Step 6) and add a revision-history note to each:
Step 6 — Clean up working files
If a BRAINSTORM was archived in Step 3, remove its working copy too:
Step 7 — Save SHIPPED document
Lessons learned
Review all artifacts for insights and capture at least 2 specific lessons in these categories:
| Category | Example | |
|---|---|---|
| Process | "Breaking into 4 independent functions enabled parallel development" | |
| Technical | "Using config.yaml instead of env vars improved testability" | |
| Communication | "Clarifying v1/v2 scope early prevented feature creep" | |
| Tools | "Using X library simplified Y" |
Rules for good lessons:
- Don't skip this — lessons learned prevent future mistakes.
- Be honest — document what didn't work too.
- Be specific and actionable — "Better planning" → "Create architecture diagram before coding".
- Archive everything — future you will thank present you.
Avoid vague lessons:
Quality Gate
Before saving the SHIPPED document:
Close the cycle — end-of-cycle handoff
When the archive is complete, report closure to the user:
| Handoff item | Content | |
|---|---|---|
| Archive location | .claude/sdd/archive/{FEATURE}/ with the full artifact list | |
| SHIPPED document | Path to SHIPPED_{DATE}.md + one-line summary of what shipped | |
| Lessons headline | The 2-3 most actionable lessons captured | |
| Statuses | Confirmation that DEFINE, DESIGN, and BUILD_REPORT now read "✅ Shipped" | |
| Workspace | features/ and reports/ clean of this feature's working files | |
| Next step | Start the next feature with /define (or /brainstorm for an unshaped idea) |
Anti-Patterns
| Never Do | Why | Instead | |
|---|---|---|---|
| Ship with failing tests | Broken code archived | Fix tests first — route back to /build | |
| Ship incomplete builds | Missing functionality | Complete build first | |
| Vague lessons learned | Not actionable | Be specific and concrete | |
| Skip artifact verification | May be incomplete | Always verify all exist | |
| Leave working files | Clutter | Clean up after archive | |
| Re-inline the SHIPPED format | Drifts from the template | Follow SHIPPED_TEMPLATE.md |
References
- Template:
${CLAUDE_PLUGIN_ROOT}/sdd/templates/SHIPPED_TEMPLATE.md - Contracts:
${CLAUDE_PLUGIN_ROOT}/sdd/architecture/WORKFLOW_CONTRACTS.yaml - Executor:
${CLAUDE_PLUGIN_ROOT}/agents/workflow/ship-agent.md - Entrypoint:
${CLAUDE_PLUGIN_ROOT}/commands/workflow/ship.md - Previous phase:
${CLAUDE_PLUGIN_ROOT}/commands/workflow/build.md
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingplugin/skills/sdd-ship/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/luanmorenommaciel/agentspec/sdd-ship)