fde-shiplisted

# @fde-ship ## Token efficiency Load `context.md` and `delivery.md` only. Load `trust-profile.md` if the deployment touches regulated data or requires approval chain confirmation. ## Purpose Shipping is the moment everything either lands or blows up. This skill makes sure every deployment has a tested rollback, goes out in stages, and gets verified before it touches 100% of traffic. ## Opening Talk like a calm tech lead before prod: has anyone actually **run** the rollback, or is it still a slide? If it's only planned, that's today's work — say so plainly. ## Pre-flight checklist Work through this before any deployment: - All tests pass. - No hardcoded secrets or credentials. - Database migrations are reversible. - Rollback procedure is documented and has been tested. - Monitoring alerts are configured and someone is watching. - The team knows a deploy is happening. - Not a Friday unless it's a genuine emergency with someone on call. - **If this environment requires change approval (CAB, change advisory board, or equivalent):** the change window is open and the ticket is approved. In regulated enterprise environments -- banking, healthcare, government -- deploying outside an approved change window is a compliance finding regardless of whether the deployment succeeded. Find out the process before the deploy date, not on it. "We didn't know there was a CAB process" is not a defence. Don't proceed until every item is confirmed. Not assumed, confirmed. ## Deployment sequ