release-management

Release management workflow for go/no-go governance, readiness evidence, and rollback preparedness. Use when release decisions require explicit criteria and cross-team sign-off; do not use for application-domain algorithm or schema decisions.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "release-management" with this command: npx skills add kentoshimizu/sw-agent-skills/kentoshimizu-sw-agent-skills-release-management

Release Management

Overview

Use this skill to run release decisions with auditable evidence and explicit risk ownership.

Scope Boundaries

  • Use this skill when the task matches the trigger condition described in description.
  • Do not use this skill when the primary task falls outside this skill's domain.

Shared References

  • Release signoff rules:
    • references/release-signoff-rules.md

Templates And Assets

  • Release readiness checklist:
    • assets/release-readiness-checklist-template.md
  • Go/no-go decision log:
    • assets/go-no-go-decision-log-template.md

Inputs To Gather

  • Release scope and risk profile.
  • Quality, security, and operational readiness evidence.
  • Rollout and rollback execution readiness.
  • Required approvers and escalation policy.

Deliverables

  • Readiness checklist with evidence status.
  • Go/no-go decision record with conditions.
  • Residual-risk log and follow-up owners.

Workflow

  1. Assemble readiness evidence with assets/release-readiness-checklist-template.md.
  2. Evaluate go/no-go under references/release-signoff-rules.md.
  3. Record decision in assets/go-no-go-decision-log-template.md.
  4. Confirm rollout/rollback owner readiness.
  5. Publish decision and unresolved risk actions.

Quality Standard

  • Go/no-go criteria are explicit and met.
  • Decision authority and ownership are auditable.
  • Rollback readiness is verified before release.

Failure Conditions

  • Stop when blocker evidence is missing.
  • Stop when rollback readiness is unverified.
  • Escalate when residual risk exceeds release policy.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Automation

architecture-clean-architecture

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

mlops-monitoring-drift

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

documentation-rfc

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

api-design-rest

No summary provided by upstream source.

Repository SourceNeeds Review