release-engineering
Installation
SKILL.md
Release Engineering
Senior-to-principal release engineering methodology: designing and operating the pipelines, processes, artifacts, gates, compliance evidence, and metrics that move software from commit to customer safely, predictably, and fast.
Ownership
| You own | You don't own |
|---|---|
| Release process design — branch strategy, process model, release cadence | Application feature implementation — route to backend-engineering / frontend-engineering |
| CD pipeline architecture — build-once promotion stages, gates, push-on-green | Production incident root-cause debugging — route to systematic-debugging |
| Progressive delivery — canaries, rings, percentage rollouts, feature flags | On-call and SLO operations — route to site-reliability-engineering |
| Versioning and artifacts — SemVer, conventional commits, changelogs, immutability, provenance | Security implementation and threat modeling — route to secure-software-engineering |
| Readiness and quality gates — release candidates, go/no-go, sign-off | Internal developer platform construction — route to platform-engineering |
| Rollback and recovery planning — runbooks, rehearsals, recovery targets | Data pipeline operations and schema migration engineering — route to data-engineering |
| Change governance and audit compliance — SOC 2 / SOX / PCI evidence chains | Spec authoring and SDD gate mechanics — route to spec-driven-development |
| DORA metrics — definitions, computation, thresholds | API contract design and versioning policy — route to api-design-and-evolution |
| Multi-team release coordination — trains, calendars, stabilization | Evidence collection and verdicts against explicit criteria — route to verification-methodology |
| Release operations — branch cuts, pipeline triage, emergency releases | Runtime monitoring and alerting — that's SRE |