des-release-readiness-review

Validate release readiness and generate a Release Readiness Report from implementation artifacts.

2|Updated May 20, 2026
One-click install
npx skills add https://github.com/DKSang/DES-SKILL --skill des-release-readiness-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: des-release-readiness-review
Source: https://github.com/DKSang/DES-SKILL/tree/main/skills-support/des-release-readiness-review
Command: npx skills add https://github.com/DKSang/DES-SKILL --skill des-release-readiness-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents unsafe, incomplete, or ungoverned data engineering work from being released by verifying that scope, evidence, contracts, quality gates, security, CI/CD checks, observability, and rollback readiness are all present and consistent.

Core Features & Use Cases

  • Release evidence validation: Reviews implementation artifacts (story/sprint/code review/test/quality/contract/security/CI gates) to ensure release claims are supported by evidence.
  • Release scope and target enforcement: Confirms the release candidate inventory (stories/epics/sprint increment/data product outputs/pipelines/serving outputs) matches the selected release target (demo, internal review, dev/test, staging, production, or handoff).
  • Risk-aware release decisioning: Produces a Release Readiness Report with an explicit decision (Ready for Release/Demo/Internal Review, Ready with Risks, Changes Required, Blocked, Needs More Evidence) and routes to the next appropriate support skill.

Quick Start

Ask your agent to run the release readiness review for your current sprint increment and generate the release report from the available implementation artifacts.

Frequently Asked Questions about des-release-readiness-review

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

FAQPage Schema
How do I validate release readiness for a data engineering sprint increment?

To validate release readiness for a data engineering sprint, review implementation artifacts like story catalogs, code reviews, and test evidence. This ensures release claims are supported by structured input before generating a formal Release Readiness Report.

What is a release readiness review in CI/CD pipelines?

A release readiness review in CI/CD pipelines evaluates release scope, completion, and acceptance criteria against available evidence. It enforces HALT guardrails to prevent production promotion without sufficient evidence, security checks, or rollback readiness.

How do I enforce quality contracts and rollback planning before a production promotion?

You enforce quality contracts and rollback planning by applying HALT guardrails during the review process. This verifies that CI/CD gates, security, and observability are present, blocking any production promotion lacking rollback readiness.

Can I route a data product increment to demo or internal review if CI gates fail?

Yes, you can route a data product increment to demo or internal review if CI gates fail. The review assesses the release candidate inventory against the selected target, generating a decision like Changes Required or Needs More Evidence.

What evidence is required to approve a data pipeline release without rolling back?

Approving a data pipeline release requires structured input artifacts including sprint plans, code reviews, and quality contracts. The review enforces HALT guardrails, ensuring no approval is made without sufficient evidence and rollback readiness.

When should I block a data product release due to missing governance security checks?

You should block a data product release when governance security checks are missing or failed. The review process enforces HALT guardrails, producing a Blocked decision if release scope, contracts, or CI/CD gates lack sufficient evidence.