---
name: ship
description: Prepare CI, releases, operations, documentation, and performance budgets without deploying or changing infrastructure.
---

# Ship preparation

Use for CI design, release planning, production-readiness documentation, observability, or performance and accessibility budgets. Do not use to deploy, publish, or modify infrastructure without a human approval recorded through `request-action`.

## Procedure

1. Read the stack ADR and acceptance criteria.
2. Load only the reference for the requested delivery need.
3. Verify changing version, syntax, action, and numeric guidance claims against official sources before recommending them.
4. Prepare reviewable local changes, a rollback plan, and verification evidence. Leave external actions approval-gated.

## Inputs and outputs

Inputs: stack ADR, release scope, deployment target, operational constraints, and observed checks. Outputs: pipeline plan, release notes, rollback and incident templates, docs structure, or measurable budgets with cited sources.

## Reference routing

| Need | Reference |
|---|---|
| CI pipeline, caching, permissions, pinned actions | [CI/CD](references/ci-cd.md) |
| Versioning, release notes, rollback, migration | [release](references/release.md) |
| Logs, health, alerts, incident response | [observability](references/observability.md) |
| README, ADR, runbook, API docs | [documentation](references/docs.md) |
| Web performance and accessibility budgets | [performance and accessibility](references/performance-a11y.md) |