production-readiness git:20260919.4491844A

Immutable. This exact content is served forever at /api/v1/blob/f8bc1289ea77cf6e.

---
name: production-readiness
description: "Assess production readiness, including operability, recovery, rollout, and support evidence."
license: MIT
metadata:
  kind: task
  author: Médéric HURIER (Fmind)
  source: github.com/fmind/dot/tree/main/skills/production-readiness
  created: "2026-08-08"
  updated: "2026-09-19"
---

# Production Readiness

Decide whether the exact candidate can be operated safely. The audit produces a go/no-go recommendation; deployment, migration, and publication follow the user's existing authorization.

## Workflow

1. **Identify the candidate**: immutable revision/artifact, configuration, environment, schema/dependency versions, proposed rollout, and dirty-tree boundary.
1. **Define acceptance**: critical journeys, correctness/availability, capacity/cost, data-loss tolerance, owners, and hard stop conditions.
1. **Review the delta**: inspect security, identity, migrations, observability, recovery, support, and one-way transitions using the [detailed procedure](references/procedure.md) for the relevant risks.
1. **Qualify**: run `mise run all` against the materialized candidate and only authorized runtime checks; preserve exact evidence, failed gates, and unavailable proof.
1. **Plan recovery**: smallest reversible exposure, observation window, halt thresholds, rollback owner/mechanism, and verification after rollback.
1. **Decide**: GO, GO WITH CHANGES, or NO-GO; report blockers, evidence, remaining actions, and the highest proven state below.

## Proof Boundaries

Keep source readiness, local checks, CI for the exact commit, runtime behavior, target deployment, and published availability distinct. Every claim names the artifact, environment, observation, time, and source; a pass at one boundary does not establish the next.

Use [data-migration](../data-migration/SKILL.md) for migration implementation and rehearsal; this skill assesses its evidence for the launch decision.

## Gotchas

- **Implicit authority**: Reuse established authority for scoped runtime checks. Name missing authority for production mutation, external coordination, or spend; the presence of credentials alone supplies none.
- **Borrowed evidence**: A green run, probe, or deployment for a different revision or environment proves nothing about this candidate.

## References

- [Detailed procedure](references/procedure.md): read for complex or high-risk work requiring the full checklist.

## Documentation

- Companion skills: [quality-assurance](../quality-assurance/SKILL.md) (test campaign), [release](../git-delivery/references/release/GUIDE.md) (publishing), [cloud-run](../cloud-run/SKILL.md) (deploy and rollback), [incident-response](../incident-response/SKILL.md) (active outage), [product-loop](../product-loop/SKILL.md) (audience, positioning, public rollout), [threat-model](../threat-model/SKILL.md) (design risk), [security-review](../security-review/references/code-review/GUIDE.md) (repository evidence).