completion-quality-gate-designer

What problem does it solve?

This Skill eliminates “all OK” and vague completion claims by designing explicit, evidence-based quality gates that separate Implementation, Verification, Acceptance, and Release readiness.

Core Features & Use Cases

• Reusable quality gate matrix: define gate IDs, entry/exit criteria, owners, approvers, pass rules, and carryover/exception behavior.
• Completion vocabulary that cannot be misused: standardize Implemented/Verified/Accepted/Released/Exception-approved so teams don’t conflate states.
• Evidence governance & reconciliation: pin SSOT evidence sources (often CI artifacts) and define how to resolve metric mismatches.
• Standard verification command set: fix canonical commands and required report fields so “tests passed” means the same thing everywhere.
• Exception register & governance: create exception fields, escalation rules, and expiration/renewal discipline for deferred items.
• Release readiness package: assemble release decision criteria, conditions, and documented limitations into a consistent assessment artifact.

Quick Start

Use the completion-quality-gate-designer skill to produce a gate matrix and Definition of Done for a new software release, ensuring every “done” claim is backed by specific evidence and clear exit criteria.