mh-cto-sdlc-phase7-gate

Automate final risk-based quality gate verification for software releases.

2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Imad-Oute/MicroHard --skill mh-cto-sdlc-phase7-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mh-cto-sdlc-phase7-gate
Source: https://github.com/Imad-Oute/MicroHard/tree/main/src/departments/cto/sdlc/phase-7-launch/mh-cto-sdlc-phase7-gate
Command: npx skills add https://github.com/Imad-Oute/MicroHard --skill mh-cto-sdlc-phase7-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the Phase 7 risk-based release quality gate verification process, ensuring that the highest-risk acceptance criteria are met before launch is authorized.

Core Features & Use Cases

  • Risk-Based Verification: Verifies the highest-risk acceptance criteria before launch.
  • Release Gate Review Agent: Spawns a release-gate-review agent for detailed analysis.
  • Cross-Session Memory: Retains decisions and context across sessions.
  • Use Case: Run after prod-readiness and before launch-plan is finalized to ensure the product is ready for launch.

Quick Start

Trigger the release gate by saying "phase 7 gate" or "release gate".

Frequently Asked Questions about mh-cto-sdlc-phase7-gate

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

FAQPage Schema
How do I automate risk-based release quality gate verification?

Automate risk-based release quality gate verification by spawning a review agent to assess high-risk acceptance criteria and ensure release readiness before launch authorization. It retains decisions across sessions for structured assessment.

What is a risk-based quality gate in software deployment?

A risk-based quality gate in software deployment is a verification process targeting the highest-risk acceptance criteria to ensure software release readiness before final launch authorization. It requires detailed inputs from previous SDLC phases.

When should I run a release gate review agent in the SDLC?

Run a release gate review agent after production-readiness checks are complete but before the final launch plan is authorized. This ensures all high-risk acceptance criteria are verified for software release readiness.

What inputs are required for release verification and risk assessment?

Release verification and risk assessment require detailed inputs from previous SDLC phases to evaluate high-risk acceptance criteria. A release gate review agent uses these structured inputs for final readiness assessment.

Does the release gate verification process retain context across sessions?

The release gate verification process retains decisions and context across sessions to maintain structured risk assessment continuity. This ensures consistent evaluation of high-risk acceptance criteria for software deployment.