Run any Skill in Manus with one click

Get Started

release-readiness

Release gate for build verification, regression evidence, rollback planning, and final go/no-go decisions.

Run Skill in Manus

Overview

Release gate for build verification, regression evidence, rollback planning, and final go/no-go decisions.

Install command

npx skills add https://github.com/ynotfins/open--claw --skill release-readiness

Copy and paste this command into Claude Code to install the skill

Source

ynotfins/open--claw

Stars0

Forks0

UpdatedMarch 30, 2026 at 05:02

SKILL.md

readonly

name	release-readiness
description	Release gate for build verification, regression evidence, rollback planning, and final go/no-go decisions.
category	Development
roles	["devops-automator","reality-checker","qa-evidence-collector","sparky-chief-product-quality-officer"]

Release Readiness

Status: READY

Purpose

Define the minimum proof needed before a release or handoff is called ready.

Gate Checklist

Build passes in CI.
Critical tests pass.
QA evidence is current for primary journeys.
Accessibility issues have been reviewed for release impact.
Rollback or revert path is known.
Open risks are written down, not implied.

Verdicts

READY: evidence is complete and no critical issues remain.
NEEDS WORK: incomplete proof or unresolved release risk.
FAILED: known breakage, missing evidence, or blocked deployment path.

More from this repository

same repository

architecture-adr

ynotfins/open--claw

Architecture decision record workflow for design choices, trade-offs, rollback paths, and modular boundaries.

2026-03-300

code-review-gate

ynotfins/open--claw

High-signal review gate for correctness, security, maintainability, testing, and performance.

2026-03-300

design-token-theming

ynotfins/open--claw

Design token and theming system for light, dark, and system modes with accessible, reusable UI primitives.

2026-03-300

handoff-state

ynotfins/open--claw

Shared operating pattern for documenting current state, evidence, blockers, and next actions between employees.

2026-03-300

mcp-integration

ynotfins/open--claw

Pattern for designing and validating MCP integrations with typed parameters, descriptive tools, and graceful failure handling.

2026-03-300

nextjs-app-router

ynotfins/open--claw

Production Next.js App Router workflow for modern websites and apps with metadata, server/client boundaries, and build verification.

2026-03-300

Source

ynotfins

ynotfins/open--claw

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations15-1253L4

name	release-readiness
description	Release gate for build verification, regression evidence, rollback planning, and final go/no-go decisions.
category	Development
roles	["devops-automator","reality-checker","qa-evidence-collector","sparky-chief-product-quality-officer"]

Release Readiness

Status: READY

Purpose

Define the minimum proof needed before a release or handoff is called ready.

Gate Checklist

Build passes in CI.
Critical tests pass.
QA evidence is current for primary journeys.
Accessibility issues have been reviewed for release impact.
Rollback or revert path is known.
Open risks are written down, not implied.

Verdicts

READY: evidence is complete and no critical issues remain.
NEEDS WORK: incomplete proof or unresolved release risk.
FAILED: known breakage, missing evidence, or blocked deployment path.