Shipping & Launch
Ships with confidence: every launch reversible, observable, and incremental. It runs a multi-section pre-launch artifact-launch-checklist (code quality, security, performance, accessibility, infrastructure, documentation), then a feature-flag lifecycle and staged rollout (deploy dark → team → 5% canary → 25/50/100%) governed by explicit advance/hold/roll-back thresholds, backed by monitoring and a documented rollback plan. It applies pattern-feature-flags to decouple deployment from release.
Its distinctive mechanism is fan-out orchestration: /ship spawns the three review personas — addy-code-reviewer, addy-security-auditor, and addy-test-engineer — concurrently, then merges their verdicts into a single go/no-go decision with a rollback plan (pattern-parallel-persona-review). This clusters it with GSD’s ship command, gsd-ship, which orchestrates launch the same way.
See Also
- gsd-ship — the GSD equivalent ship orchestrator.
- openspec-archive — OpenSpec’s finalize step (spec-merge + archive, no deploy).
- addy-code-reviewer — review persona spawned in the fan-out.
- addy-security-auditor — security persona spawned in the fan-out.
- addy-test-engineer — test persona spawned in the fan-out.
- artifact-launch-checklist — the checklist it produces.
- stage-release — the canonical stage this implements.