prepare-release-candidate

Audit release candidates, classify blockers by severity, and issue GO or NO-GO decisions.

Updated Aug 31, 2026
One-click install
npx skills add https://github.com/pikachu0310/codex-agent-ops-public --skill prepare-release-candidate-pikachu0310
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prepare-release-candidate
Source: https://github.com/pikachu0310/codex-agent-ops-public/tree/main/.agents/skills/prepare-release-candidate
Command: npx skills add https://github.com/pikachu0310/codex-agent-ops-public --skill prepare-release-candidate-pikachu0310

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Shipping a product without a structured readiness review risks launch failures, data loss, and broken user journeys. This Skill audits the actual product state before a public release, classifies findings by severity, and produces a defensible GO or NO-GO decision with a short human launch checklist. ## Core Features & Use Cases - Severity-Based Audit: Classifies every finding as P0 (stop immediately), P1 (release blocker), P2 (fix if safe), or P3 (defer), with evidence, reproduction steps, and rollback implications. - Release Lenses: Applies targeted checklists covering promise/first value, functional integrity, data/security/trust, operations/recovery, and experience quality via the references/release-lenses.md file. - Decision Report: Issues exactly one verdict (GO, CONDITIONAL GO, or NO-GO) with verification evidence, untested areas, and a roughly five-minute human launch checklist. - Use Case: Before launching a web app, ask for a release-readiness review. The Skill verifies core user journeys, checks that marketing claims match actual behavior, fixes safe P0/P1 blockers if authorized, and reports whether the release should proceed. ## Quick Start Use prepare-release-candidate to audit this project before launch, fix safe blockers, verify the core user journeys, and give me a GO or NO-GO recommendation.

Frequently Asked Questions about prepare-release-candidate

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

FAQPage Schema
How do I check if my product is ready for release?

Request a release-readiness audit of your product. The Skill defines the release boundary, verifies core user journeys against actual behavior, classifies findings by P0-P3 severity, and issues a GO, CONDITIONAL GO, or NO-GO decision with a human launch checklist.

What is the difference between P0, P1, P2, and P3 release findings?

P0 means stop immediately due to destructive behavior or critical security exposure. P1 blocks release because the primary journey fails. P2 covers significant issues fixable within the release window. P3 is low-impact polish deferred deliberately.

Can this Skill fix launch blockers or only audit them?

It supports both audit-only reviews and authorized fixes. When the request asks to finish the release candidate, it fixes P0 and P1 blockers locally with reversible changes, but never deploys, publishes, or mutates production without explicit authorization.

When should I not use a release readiness audit?

Do not use it for a simple already-validated deployment where no readiness review is requested. It is designed for pre-release audits and launch decisions, not routine deployment execution.

What does a GO or NO-GO release decision include?

The report includes candidate identity and scope, a severity table with fixes made, verification evidence and untested areas, the GO/CONDITIONAL GO/NO-GO verdict with rationale, a five-minute human launch checklist, and deferred work with rollback notes.