release-gate-validator

Validate release readiness by checking milestone gates, residual risks, builds, and interop.

2|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/Treystu/SCMessenger --skill release-gate-validator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-gate-validator
Source: https://github.com/Treystu/SCMessenger/tree/main/skills/release-gate-validator
Command: npx skills add https://github.com/Treystu/SCMessenger --skill release-gate-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents incomplete or risky releases by verifying milestone gate completion, residual risks, build verification, interop readiness, and documentation continuity before declaring a release candidate.

Core Features & Use Cases

  • Milestone gate validation: Loads the active milestone plan and checks that all gates marked complete are actually ready.
  • Residual risk register verification: Confirms each remaining risk is addressed or explicitly accepted, aligned with the project’s tracking process.
  • Build and interop readiness checks: Runs workspace test verification plus platform build checks (Gradle Debug and iOS archive), and validates interop matrix gates.
  • Release readiness packaging: Produces a release-candidate status along with a blocking-issues list and risk-acceptance requirements for decision-makers.

Quick Start

Run the release-gate-validator skill to validate SCMessenger against the active milestone plan and generate a readiness status with any blockers and required risk acceptances.

Frequently Asked Questions about release-gate-validator

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

FAQPage Schema
How do I validate milestone completion before declaring a release candidate?▼

Milestone validation checks whether gates marked complete are actually ready by loading the active milestone plan, running declared build checks, and verifying interop matrix gates to produce a clear release readiness result.

What is release gating and how does it handle residual risks?▼

Release gating verifies release readiness by checking milestone completion and confirming each residual risk in the risk register is addressed or explicitly accepted before packaging a release candidate status.

Can I run release readiness checks for both Android Gradle and iOS archive builds?▼

Yes, release readiness checks support Android Gradle debug builds and iOS archive builds alongside workspace test suite verification to validate platform build readiness and cross-component interoperability.

How do I verify interop matrix gates and documentation continuity for a release?▼

Interop matrix gates and documentation continuity are verified by loading the specified milestone plan, running declared checks across test suites, and producing a readiness result that includes any blocking issues.

What is the best way to surface blocking issues and risk acceptance requirements before a release?▼

Surfacing blocking issues and risk acceptance requirements involves running release gate validation checks across builds and interop matrices, then generating a release-candidate status package for decision-makers.

When should I not use automated release gate validation?▼

Automated release gate validation should not be used when the active milestone plan is not loaded or when cross-component interoperability validation and platform build checks cannot be executed in the workspace test suite environment.