release-protocol

Generate a RELEASE.md with deployment runbook, gates, rollback, and monitoring.

1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/AnjinMeili/Claude-ITIL-Planner --skill release-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-protocol
Source: https://github.com/AnjinMeili/Claude-ITIL-Planner/tree/main/planitil/skills/release-protocol
Command: npx skills add https://github.com/AnjinMeili/Claude-ITIL-Planner --skill release-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a formal framework to generate a reproducible RELEASE.md containing deployment runbooks, approval gates, rollback procedures, and success monitoring.

Core Features & Use Cases

  • Generates a complete RELEASE.md from a standard template, including Pre-Deployment Checks, Deployment Execution, Post-Deployment Verification, and Monitoring.
  • Encapsulates Gate definitions (QA Pass, Human Approval, and optional gates) and the required evidence locations for audits.
  • Supports built-in rollback procedures and test procedures in staging to validate recoverability before production.

Quick Start

Invoke release-protocol to generate a complete RELEASE.md containing the deployment runbook, approval gates, rollback steps, and monitoring window.

Frequently Asked Questions about release-protocol

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a deployment runbook with rollback procedures for production releases?

A deployment runbook formalizes production releases by generating a RELEASE.md that codifies pre-deployment checks, deployment execution, post-deployment verification, and rollback procedures. It provides a reproducible framework for auditable deployments.

What is the best way to formalize approval gates and QA validation for a production release?

The best way to formalize approval gates is to codify QA pass and human approval criteria within a RELEASE.md. This documents the required evidence locations for audits and ensures formal pre-deployment validation before production releases.

How do I generate a RELEASE.md for deployment governance and monitoring?

You generate a RELEASE.md for deployment governance by using a standard template that outputs pre-deployment checks, deployment execution steps, post-deployment verification, and monitoring windows. This creates a reproducible framework for auditable production releases.

Can I include test procedures in staging to validate rollback recoverability before a production deployment?

Yes, you can validate rollback recoverability by including built-in rollback procedures and test procedures in staging. This validates recoverability before executing the actual production deployment, ensuring formal pre-deployment validation.

When do I need a formal release protocol for my deployment workflow?

You need a formal release protocol when your projects require auditable production releases with formal pre-deployment validation and traceable rollback procedures. It ensures deployment governance through a reproducible runbook with defined gates and monitoring.