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.
This bundle composes specialists. It never replaces them and never re-derives
their methods. If the task is wholly within one specialist's domain, load that
specialist directly.
Readiness routing table
The bundle routes each production concern to the specialist that owns it. The
bundle itself owns only the acceptance and handoff layer — the cross-domain
assembly and the gate decision.
Primary production-domain routes
| Domain |
Specialist skill |
What the specialist owns |
What the bundle adds |
| Production readiness |
production-readiness |
Risk-scaled evidence packet (11 categories), go/no-go/defer/exception launch decisions, accountable owners |
Cross-domain assembly with migration, recovery, capacity/cost, and incident evidence; gate integration |
| Migration |
migration-engineering |
Expand/contract, compatibility windows, dual-running, backfills, reconciliation, cutover, recovery paths |
Migration evidence as input to the gate model; handoff of migration verification to the operational record |
| Resilience and recovery |
resilience-and-recovery |
Failure modes, degradation choices, RTO/RPO, restore testing, DR, game days, failover, data integrity |
Recovery evidence as a gate condition; exercise results feed the handoff record |
| Capacity and cost |
capacity-and-cost-engineering |
Demand/capacity/scaling/utilization models, unit-cost connection to SLO decisions, cost-constrained scenarios |
Capacity/cost evidence as a gate condition; SLO/cost tradeoff decisions feed the gate model |
| Incident learning |
incident-learning |
Observed facts, causal hypotheses, contributing conditions, follow-up work mapping, verified closure |
Pre-existing incident evidence as a gate condition; post-launch incidents routed back to incident-learning |
Supporting specialist routes
Cross-domain entry evidence
Before the gate model runs, entry evidence must exist from every applicable
domain. The bundle does not gather this evidence — it requires it. The complete
evidence packet specification is in
references/evidence-packet.md.
Summary:
- Every evidence domain (readiness, migration, recovery, capacity/cost,
incident-learning) has a named source or an explicit gap with an owner and
due date.
- The packet is usable for both new services and changes to existing systems
— domains irrelevant to the change are explicitly marked "not applicable"
with a reason.
- Missing evidence is never silently omitted. Every gap is recorded.
Gate and exception model
The gate model produces exactly one of five outcomes for every production change.
Full definitions, conditions, and evidence requirements are in
references/gates.md.
| Outcome |
Meaning |
Key condition |
| Go |
Authorized to proceed to production |
All required evidence domains are sourced; no blocking gaps |
| No-go |
Blocked; must not proceed |
A required domain has a blocking gap, or an irreversible step has no verified recovery path |
| Defer |
Postponed with explicit conditions |
A non-blocking gap or dependency has a committed resolution date; re-evaluation is scheduled |
| Exception |
Proceeds under an explicit waiver |
A human authority (not the agent, not the service owner alone) approves a time-bounded, risk-bounded exception |
| Escalation |
Decision escalated to a higher body |
Irreconcilable gate conflict, trust-boundary security gap, cross-team authority gap, or regulatory boundary |
Every outcome is anchored to service ownership, risk, evidence, and
verification. No gate passes on a bare checklist. Each outcome names the
accountable owner and records the evidence that supports it.
Operational handoff and post-launch learning
After a gate outcome is reached, the operational handoff record
(references/handoff-record.md) is populated.
Post-launch learning paths
Launch outcomes and post-launch observations feed two learning routes:
Incident learning — post-launch incidents (SLO degradations, unexpected
failures, capacity breaches) are routed to
incident-learning. The handoff record
provides the launch context; the incident-learning skill's verified-closure
requirement ensures follow-up items are tracked to completion.
Lifecycle learning — expected outcomes recorded in the handoff (SLO
targets, capacity assumptions, cost projections) are routed to
product-lifecycle-learning
for expected-vs-observed comparison at the handoff's review cadence. The
lifecycle-learning skill's continue/improve/harvest/pivot/pause/retire
decisions are informed by the gap between predicted and observed production
behavior.
The handoff record is populated for every outcome — not only Go. No-go, Defer,
Exception, and Escalation each produce a handoff record with the blocking
condition, the follow-up path, and the accountable owner.
Loading and nested-skill behavior
This bundle is the discoverable entry point. It does not contain nested
sub-skills under a skills/ directory. All routed skills are top-level catalog
skills referenced via relative markdown links. Harnesses that support progressive
disclosure will discover this bundle through its SKILL.md frontmatter and load
the referenced specialists on trigger.
See AGENTS.md for agent-specific loading notes.
File map
| Path |
Loaded when |
| references/discovery-brief.md |
Understanding the bundle's boundary against existing production and release skills |
| references/evidence-packet.md |
Assembling cross-domain evidence for a production decision |
| references/gates.md |
Running the gate model — go/no-go/defer/exception/escalation |
| references/handoff-record.md |
Producing the operational handoff record and post-launch learning path |
| manifest.yaml |
Machine-readable composition contract (schema v1): purpose, audience, stages, included skills, prerequisites, outputs, handoffs, conflicts, and eval suite; consumed by the lifecycle capability matrix |
1---2name: production-excellence3description: >-4 Build cross-domain production evidence from readiness, migration, recovery,5 capacity/cost, and incident learning into launch or operational decisions. Do not use6 this skill for a single specialist's risk packet and launch gate; use7 `production-readiness` for that readiness review.8license: MIT9compatibility: Platform-agnostic methodology. No runtime dependencies, API keys, or external services required.10metadata:11 source: https://skillmd.com/skills/magnus919/production-excellence12 tags: production-excellence, launch-decision, gate-model, evidence-packet,13 operational-handoff, readiness-review, cross-domain, production-acceptance,14 go-no-go, exception-escalation, post-launch-learning15---1617# Production Excellence1819A thin composition bundle that assembles cross-domain production evidence into a20defensible launch or operational decision. It owns the **acceptance and handoff21layer** — the gate model that reads evidence from specialist skills and produces22go / no-go / defer / exception / escalation outcomes with accountable owners.23It does not own any specialist's runbook.2425## When to load this2627Load when:2829- A service or change is approaching a launch decision and evidence from multiple30 production domains must be assembled.31- You need a structured gate model (go/no-go/defer/exception/escalation) with32 conditions, evidence, and accountable owners.33- Cross-domain evidence (readiness, migration, recovery, capacity/cost, incident34 history) must be combined into one operational handoff record.35- A launch or change needs a post-launch learning path routed to incident-learning36 and product-lifecycle-learning.37- You are coordinating a production change across SRE, release, platform, security,38 data, and QA specialists and need a single acceptance contract.3940## When not to use4142Do **not** load this bundle for:4344- **Incident command or SLO operations** — those are owned by45 [site-reliability-engineering](../site-reliability-engineering/SKILL.md).46- **Release-pipeline mechanics, versioning, or deployment strategies** — those are47 owned by [release-engineering](../release-engineering/SKILL.md).48- **Platform architecture or internal-developer-platform design** — those are49 owned by [platform-engineering](../platform-engineering/SKILL.md).50- **Threat modeling, security review procedure, or vulnerability assessment** —51 those are owned by52 [secure-software-engineering](../secure-software-engineering/SKILL.md).53- **Data-pipeline design, ETL, or storage architecture** — those are owned by54 [data-engineering](../data-engineering/SKILL.md).55- **Test-strategy design, regression-suite management, or test-automation56 framework design** — those are owned by57 [qa-methodology](../qa-methodology/SKILL.md).58- **A generic checklist detached from service ownership, risk, evidence, and59 verification** — every gate in this bundle requires a named service owner,60 assessed risk, verified evidence, and a declaration of the verification61 boundary. A bare checklist is never a valid outcome.6263This bundle composes specialists. It never replaces them and never re-derives64their methods. If the task is wholly within one specialist's domain, load that65specialist directly.6667## Readiness routing table6869The bundle routes each production concern to the specialist that owns it. The70bundle itself owns only the acceptance and handoff layer — the cross-domain71assembly and the gate decision.7273### Primary production-domain routes7475| Domain | Specialist skill | What the specialist owns | What the bundle adds |76|---|---|---|---|77| **Production readiness** | [production-readiness](../production-readiness/SKILL.md) | Risk-scaled evidence packet (11 categories), go/no-go/defer/exception launch decisions, accountable owners | Cross-domain assembly with migration, recovery, capacity/cost, and incident evidence; gate integration |78| **Migration** | [migration-engineering](../migration-engineering/SKILL.md) | Expand/contract, compatibility windows, dual-running, backfills, reconciliation, cutover, recovery paths | Migration evidence as input to the gate model; handoff of migration verification to the operational record |79| **Resilience and recovery** | [resilience-and-recovery](../resilience-and-recovery/SKILL.md) | Failure modes, degradation choices, RTO/RPO, restore testing, DR, game days, failover, data integrity | Recovery evidence as a gate condition; exercise results feed the handoff record |80| **Capacity and cost** | [capacity-and-cost-engineering](../capacity-and-cost-engineering/SKILL.md) | Demand/capacity/scaling/utilization models, unit-cost connection to SLO decisions, cost-constrained scenarios | Capacity/cost evidence as a gate condition; SLO/cost tradeoff decisions feed the gate model |81| **Incident learning** | [incident-learning](../incident-learning/SKILL.md) | Observed facts, causal hypotheses, contributing conditions, follow-up work mapping, verified closure | Pre-existing incident evidence as a gate condition; post-launch incidents routed back to incident-learning |8283### Supporting specialist routes8485| Domain | Specialist skill | When routed |86|---|---|---|87| **Reliability / SLOs** | [site-reliability-engineering](../site-reliability-engineering/SKILL.md) | SLO/error-budget status required for gate entry; incident response for post-launch issues |88| **Release mechanics** | [release-engineering](../release-engineering/SKILL.md) | Release plan, rollout/rollback strategy required for gate entry |89| **Platform** | [platform-engineering](../platform-engineering/SKILL.md) | Service-catalog entry, paved-road status for new services |90| **Security** | [secure-software-engineering](../secure-software-engineering/SKILL.md) | Security review evidence for trust-boundary changes |91| **Data** | [data-engineering](../data-engineering/SKILL.md) | Data-quality and pipeline evidence for data-path changes |92| **QA** | [qa-methodology](../qa-methodology/SKILL.md) | Verification evidence for all launches |93| **Verification** | [verification-methodology](../verification-methodology/SKILL.md) | Boundary labeling and gap declaration for evidence assessment |9495## Cross-domain entry evidence9697Before the gate model runs, entry evidence must exist from every applicable98domain. The bundle does not gather this evidence — it requires it. The complete99evidence packet specification is in100[references/evidence-packet.md](references/evidence-packet.md).101102Summary:103104- Every evidence domain (readiness, migration, recovery, capacity/cost,105 incident-learning) has a named source or an explicit gap with an owner and106 due date.107- The packet is usable for **both new services and changes to existing systems**108 — domains irrelevant to the change are explicitly marked "not applicable"109 with a reason.110- Missing evidence is never silently omitted. Every gap is recorded.111112## Gate and exception model113114The gate model produces exactly one of five outcomes for every production change.115Full definitions, conditions, and evidence requirements are in116[references/gates.md](references/gates.md).117118| Outcome | Meaning | Key condition |119|---|---|---|120| **Go** | Authorized to proceed to production | All required evidence domains are sourced; no blocking gaps |121| **No-go** | Blocked; must not proceed | A required domain has a blocking gap, or an irreversible step has no verified recovery path |122| **Defer** | Postponed with explicit conditions | A non-blocking gap or dependency has a committed resolution date; re-evaluation is scheduled |123| **Exception** | Proceeds under an explicit waiver | A human authority (not the agent, not the service owner alone) approves a time-bounded, risk-bounded exception |124| **Escalation** | Decision escalated to a higher body | Irreconcilable gate conflict, trust-boundary security gap, cross-team authority gap, or regulatory boundary |125126Every outcome is anchored to **service ownership**, **risk**, **evidence**, and127**verification**. No gate passes on a bare checklist. Each outcome names the128accountable owner and records the evidence that supports it.129130## Operational handoff and post-launch learning131132After a gate outcome is reached, the operational handoff record133([references/handoff-record.md](references/handoff-record.md)) is populated.134135### Post-launch learning paths136137Launch outcomes and post-launch observations feed two learning routes:1381391. **Incident learning** — post-launch incidents (SLO degradations, unexpected140 failures, capacity breaches) are routed to141 [incident-learning](../incident-learning/SKILL.md). The handoff record142 provides the launch context; the incident-learning skill's verified-closure143 requirement ensures follow-up items are tracked to completion.1441452. **Lifecycle learning** — expected outcomes recorded in the handoff (SLO146 targets, capacity assumptions, cost projections) are routed to147 [product-lifecycle-learning](../product-lifecycle-learning/SKILL.md)148 for expected-vs-observed comparison at the handoff's review cadence. The149 lifecycle-learning skill's continue/improve/harvest/pivot/pause/retire150 decisions are informed by the gap between predicted and observed production151 behavior.152153The handoff record is populated for every outcome — not only Go. No-go, Defer,154Exception, and Escalation each produce a handoff record with the blocking155condition, the follow-up path, and the accountable owner.156157## Loading and nested-skill behavior158159This bundle is the discoverable entry point. It does not contain nested160sub-skills under a `skills/` directory. All routed skills are top-level catalog161skills referenced via relative markdown links. Harnesses that support progressive162disclosure will discover this bundle through its `SKILL.md` frontmatter and load163the referenced specialists on trigger.164165See [AGENTS.md](AGENTS.md) for agent-specific loading notes.166167## File map168169| Path | Loaded when |170|---|---|171| [references/discovery-brief.md](references/discovery-brief.md) | Understanding the bundle's boundary against existing production and release skills |172| [references/evidence-packet.md](references/evidence-packet.md) | Assembling cross-domain evidence for a production decision |173| [references/gates.md](references/gates.md) | Running the gate model — go/no-go/defer/exception/escalation |174| [references/handoff-record.md](references/handoff-record.md) | Producing the operational handoff record and post-launch learning path |175| [manifest.yaml](manifest.yaml) | Machine-readable composition contract (schema v1): purpose, audience, stages, included skills, prerequisites, outputs, handoffs, conflicts, and eval suite; consumed by the lifecycle capability matrix |