release-management
Release Management
Turn a technically ready build into a deliberately coordinated release.
Context
Release management decides whether the current candidate should ship now, under what constraints, and with which communication and ownership model. It is broader than deployment strategy: deployment answers how code rolls out, while release management answers whether the organization is ready to do it.
Use this skill when a release has external coordination cost, meaningful risk, or stakeholders who need a single plan instead of scattered quality artifacts.
Inputs
- delivery-decision-record -- Optional but preferred handoff when
delivery-completionalready decided the branch outcome and preserved the exact verification evidence used. - test-report -- Functional readiness and known quality gaps.
- security-report -- Security findings and any accepted release risk.
- performance-report -- Performance readiness and capacity-sensitive concerns when one exists.
Process
More from yknothing/prodcraft
system-design
Use when reviewed requirements or specifications are ready and the team must decide high-level architecture, component boundaries, integration seams, or brownfield coexistence strategy before API design, technology selection, or task planning.
6ci-cd
Use when a reviewed implementation slice needs an automated build, test, and deployment pipeline, especially when brownfield rollback, release-boundary checks, contract/integration gates, and staged delivery must be explicit before shipping.
6intake
The mandatory gateway for all new engineering work. Triage and route new products, apps, features, migrations, tech-debt, or any 'not sure where to start' request to the correct lifecycle path. Use before starting design or implementation. Do not use for ongoing tasks, specific debugging, or PR reviews.
6feature-development
Use when a reviewed task slice has tests or acceptance targets and the team must turn it into a small, mergeable implementation increment without expanding scope, breaking contracts, or hiding release-boundary risk.
6monitoring-observability
Use when a live service or newly delivered release needs actionable telemetry, dashboards, and alerts that expose real user-impactful boundaries, especially when brownfield coexistence rules, unsupported-flow safety, rollback health, or queue/backfill behavior must be visible before incidents escalate.
6incident-response
Use when a live production issue needs coordinated containment, severity triage, stakeholder communication, and evidence capture, especially when a recent release, brownfield coexistence rules, rollback decisions, or unresolved contract boundaries must be handled before root-cause work.
6