Agent skill · magnus919
release-engineering
Design, automate, and operate end-to-end software releases: release process models and pipelines (trunk-based development, CD stages, release trains), progressive delivery and feature flags, versioning and artifact management (SemVer, conventional commits, changelogs, SBOM/provenance), readiness and quality gates, rollback and recovery planning, change-management and audit compliance (SOC 2, SOX, PCI), DORA metrics, and multi-team release coordination. Do not use for application feature implementation (backend-engineering/frontend-engineering), production incident root-cause debugging or on-call/SLO operations (systematic-debugging / site-reliability-engineering), security implementation or threat modeling (secure-software-engineering), or internal developer platform construction (platform-engineering).
What it needs
About 7k tokens when loaded.
What this skill does
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 Core Principles Build once, promote many. The artifact that passed every gate is the only artifact that ships. Rebuilding per environment reintroduces risk and invalidates what was verified. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills magnus919/release-engineering