loom-shipping-and-launchlisted

# loom-shipping-and-launch Shipping and launch is a release-readiness playbook. It checks the graph, verifies the artifact, defines rollout and rollback, records launch evidence, and runs retrospective follow-up. ## Loom Routing Common routes use these Loom skills for durable records or follow-up workflow: `loom-plans`, `loom-tickets`, `loom-evidence`, `loom-audit`, `loom-specs`, `loom-knowledge`, and `loom-retrospective`. Follow any named Loom skill fully. This playbook adds workflow pressure; it does not shorten target-skill requirements. ## Use This Playbook When Use this playbook when: - deploying a feature or significant change to production - enabling a feature flag for users - launching beta, staged rollout, or early access - releasing a migration, API change, or infrastructure change - preparing rollback, monitoring, changelog, or release notes - launch claims need evidence and audit before communication ## Route Use this route: ```text readiness -> rollout -> observe -> decide -> communicate -> clean up ``` ## Readiness Start from the tickets, plan, specs, evidence, and audit records that define the release. Check: - ticket closure or review state - spec requirements and scenarios in scope - evidence for tests, builds, browser checks, migrations, and manual checks - audit findings and dispositions - known residual risk - feature flag state - migration and rollback readiness - docs, changelog, and operator-facing notes If the records cannot support the