release-manager

Coordinate post-Gate-2 production deployments with Agile V controls.

50|9|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/Agile-V/agile_v_skills --skill release-manager-agile-v
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-manager
Source: https://github.com/Agile-V/agile_v_skills/tree/main/release-manager
Command: npx skills add https://github.com/Agile-V/agile_v_skills --skill release-manager-agile-v

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-Gate-2 production deployments require formal governance to ensure traceability, rollback safety, and stakeholder sign-offs. This skill provides a structured framework to coordinate and validate post-release activities with Agile V rigor.

Core Features & Use Cases

  • Release Planning — define deployment timeline, scope, and approval gates
  • Rollout & Rollback — plan phased rollouts and pre-defined rollback procedures
  • Post-Release Validation & Incident Handoff — verify requirements, monitor outcomes, and hand off incidents for the next cycle

Quick Start

Initiate a controlled post-Gate-2 deployment using the pre-approved rollout plan and rollback procedure.

Frequently Asked Questions about release-manager

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

FAQPage Schema
How do I plan a production deployment with formal rollback procedures?

Plan a production deployment by defining the rollout timeline, scope, and approval gates, alongside pre-defined rollback procedures to ensure safe post-Gate-2 releases with formal governance.

What is post-Gate-2 release management and when do I need it?

Post-Gate-2 release management is the structured coordination of production deployments requiring formal governance, traceability to REQ IDs, and stakeholder sign-offs. You need it when rolling out changes that demand rigorous validation.

How does requirements traceability work during a production rollout?

Requirements traceability during a production rollout links deployment activities directly to REQ IDs, ensuring every release artifact passes formal validation gates and maintaining accountability across the post-Gate-2 workflow.

What's the best way to handle incident handoff after a production deployment?

Handle incident handoff after a production deployment by verifying requirements, monitoring post-release outcomes, and transferring any incidents through a structured workflow for resolution in the next cycle.

Can I use this release management workflow for phased rollouts in production environments?

Yes, you can use this workflow for phased rollouts in production environments. It supports planning phased deployment timelines, applying validation gates, and executing pre-defined rollback procedures at each stage.

Why do post-Gate-2 deployments require formal sign-off validation?

Post-Gate-2 deployments require formal sign-off validation to enforce risk management, ensure stakeholder accountability, and verify that production releases meet strict traceability and governance controls before completion.