validating-production-readinesslisted

# Validating Production Readiness This skill is the **single source of truth** for the production-readiness gate in the lt-stack. Every consumer applies the same eight pillars, the same severity classification, and produces the same report block — so multiple runs across time can be compared. > **Goal:** Decide, with evidence, whether the system is safe to deploy to production. Anything Critical is a hard blocker. Anything Major must be tracked. Minor findings are advisory. ## When to Use This Skill | Caller | Phase | Trigger | |--------|-------|---------| | `/lt-dev:production-ready` | Phase 4 | Hard release gate | | `lt-dev:production-readiness-orchestrator` | Phase 4 | Owns the audit + remediation loop | | `lt-dev:devops-reviewer` | (cross-reference) | Cites this checklist when flagging deployment-relevant gaps | | Manual user invocation | Pre-deploy | Final sign-off before tagging a release | ## Severity Classification | Severity | Meaning | Effect on the release | |----------|---------|------------------------| | **Critical** | Loss of data, security breach, or undetectable downtime is plausible | **BLOCK** the release until fixed | | **Major** | Operability is degraded; recovery requires manual intervention | Tracked finding; release may proceed only with explicit owner sign-off | | **Minor** | Cosmetic, missing nice-to-have, or hygienic gap with no operational impact | Advisory only | A pillar with even a single Critical finding makes the whole release **NOT REA