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
- Assemble readiness evidence with
assets/release-readiness-checklist-template.md. - Evaluate go/no-go under
references/release-signoff-rules.md. - Record decision in
assets/go-no-go-decision-log-template.md. - Confirm rollout/rollback owner readiness.
- 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.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9