Agent skill · magnus919
production-excellence
Route cross-domain production evidence (readiness, migration, recovery, capacity/cost, incident-learning) into a launch or operational decision — go, no-go, defer, exception, or escalation — with an accountable owner and a post-launch learning path. Compose production specialists without copying their runbooks. Do not use for incident command, release-pipeline mechanics, platform architecture, threat modeling, data-pipeline design, or any task owned end-to-end by a single specialist skill; do not use as a generic checklist detached from service ownership, risk, evidence, and verification.
What it needs
About 5k tokens when loaded.
What this skill does
Production Excellence A thin composition bundle that assembles cross-domain production evidence into a defensible launch or operational decision. It owns the acceptance and handoff layer — the gate model that reads evidence from specialist skills and produces go / no-go / defer / exception / escalation outcomes with accountable owners. It does not own any specialist's runbook. When to load this Load when: A service or change is approaching a launch decision and evidence from multiple production domains must be assembled. You need a structured gate model (go/no-go/defer/exception/escalation) with conditions, evidence, and accountable owners. Cross-domain evidence (readiness, migration, recovery, capacity/cost, incident history) must be combined into one operational handoff record. A launch or change needs a post-launch learning path routed to incident-learning and product-lifecycle-learning. You are coordinating a production change across SRE, release, platform, security, data, and QA specialists and need a single acceptance contract. When not to use Do not load this bundle for: Incident command or SLO operations — those are owned by site-reliability-engineering. Release-pipeline mechanics, versioning, or deployment strategies — those are owned by release-engineering. Platform architecture or internal-developer-platform design — those are owned by platform-engineering. Threat modeling, security review procedure, or vulnerability assessment — those are owned by secure-software-engineering. Data-pipeline design, ETL, or storage architecture — those are owned by data-engineering. Test-strategy design, regression-suite management, or test-automation framework design — those are owned by qa-methodology. A generic checklist detached from service ownership, risk, evidence, and verification — every gate in this bundle requires a named service owner, assessed risk, verified evidence, and a declaration of the verification boundary. A bare checklist is never a valid outcome. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills magnus919/production-excellence