Agent skill · magnus919
production-readiness
Define the minimum production evidence packet by risk class and produce go/no-go/defer/exception launch decisions with accountable owners. Cover ownership, user/business outcome, dependencies, SLOs, observability, support, security, data, rollback, capacity, and cost — every category with a named source or explicit missing-evidence outcome. Route detailed checks to existing specialist skills. Do not use for release pipeline mechanics (release-engineering) or incident response and SLO operations (site-reliability-engineering).
What it needs
About 7k tokens when loaded.
What this skill does
Production Readiness Assemble cross-domain evidence into a launch decision. This skill defines the minimum production evidence packet by risk class, maps every evidence category to a named source or an explicit missing-evidence outcome, and produces one of four launch decisions with an accountable owner. It does not duplicate release checklists, does not produce a universal risk score, and routes detailed checks to the existing specialist skills. When to load this Load when any of these triggers matches: A service, feature, or change is approaching a launch decision and needs a production-readiness review. Evidence from multiple domains (ownership, SLOs, security, data, support, cost, observability) must be assembled into one reviewable record. A launch review board, readiness gate, or accountable owner needs a structured go / no-go / defer / exception recommendation. A migration-dependent release needs evidence that every dependency is ready. A low-risk documentation-only change needs proportional (not full-scale) readiness review. When not to use Release pipeline mechanics — promotion, canary stages, CI/CD gate configuration, versioning, and artifact management. Route to release-engineering. Release-engineering owns the pipeline gate; production-readiness owns the cross-domain evidence assembly and launch decision. Incident response, SLO operations, on-call, and reliability engineering. Route to site-reliability-engineering. SRE owns the live-service health boundary; production-readiness owns the pre-launch readiness boundary. Security implementation, threat modeling, or penetration testing. Route to secure-software-engineering or security-audit-methodology. Data pipeline operations, schema migration engineering, or ETL/ELT design. Route to data-engineering. Test strategy, regression planning, and quality gates. Route to qa-methodology. Platform infrastructure provisioning or IDP design. Route to platform-engineering. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills magnus919/production-readiness