skills.rest
RichardGeorgeDavis
RichardGeorgeDavisCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

quality-gate

Define explicit completion criteria with required and optional checks.

2|Updated Mar 17, 2026
Search Tags:#verification#quality-assurance#risk-management#acceptance-criteria#definition-of-done#release-prep
One-click install
npx skills add https://github.com/RichardGeorgeDavis/Codex-Workspace --skill quality-gate-richardgeorgedavis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quality-gate
Source: https://github.com/RichardGeorgeDavis/Codex-Workspace/tree/main/tools/templates/skills/common/quality-gate
Command: npx skills add https://github.com/RichardGeorgeDavis/Codex-Workspace --skill quality-gate-richardgeorgedavis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use this skill when the task needs a visible definition of done instead of informal confidence.

Core Features & Use Cases

  • Provides a concrete criterion-driven approach to verify task completion, reducing ambiguity and rework.
  • Aligns team expectations by codifying observable checks and required vs. optional verifications.
  • Supports governance in release prep, refactors with regression risk, security-sensitive changes, migrations, and multi-contributor work.

Quick Start

Define and reference the explicit completion criteria for the current task before starting work.

Frequently Asked Questions about quality-gate

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

FAQPage Schema
What is a definition of done for software release preparation?▼

A definition of done for release preparation provides explicit, observable completion criteria that replace informal confidence to ensure verifiable delivery and reduce ambiguity.

How do I define acceptance criteria for a complex refactor with regression risk?▼

To define acceptance criteria for refactors with regression risk, specify observable checks categorized as required or optional, and document any residual risks to ensure verifiable completion.

When do I need explicit completion criteria for multi-contributor tasks?▼

You need explicit completion criteria for multi-contributor tasks across complex projects to align team expectations, codify verifiable checks, and replace informal confidence before release.

Does this approach work for security-sensitive changes and migrations?▼

Yes, this criterion-driven approach supports governance for security-sensitive changes and migrations by requiring observable checks and documenting residual risks to verify task completion.

What's the best way to manage residual risks during quality assurance verification?▼

The best way to manage residual risks during quality assurance verification is to document them alongside required and optional observable checks within your explicit completion criteria.

Related Skills

Explore More Software Engineering Skills→
LarussoLarusso
42

openspec-archive-change

Archive completed experimental workflow changes after verifying artifact and task statuses.

Community
Advanced
jchildreejchildree
1

verification-before-completion

Verify completion claims by executing and confirming command outputs before commits.

Community
Intermediate
TeiNamTeiNam
12

laravel-verification

Automate Laravel project verification for CI/CD pipelines.

Community
Advanced
EmasoftEmasoft
13

amoa-checklist-compilation-patterns

Compile verification checklists from requirements and specifications into markdown.

Community
Intermediate