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-completion already 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