quality-gates

Define four quality gates between Dev, QA, UAT, and Production phases.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/devmuslim/pdm-skills --skill quality-gates-devmuslim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-gates
Source: https://github.com/devmuslim/pdm-skills/tree/main/pdm-quality-testing/skills/quality-gates
Command: npx skills add https://github.com/devmuslim/pdm-skills --skill quality-gates-devmuslim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents teams from progressing to the next stage of development until the current phase meets predefined quality standards, reducing the likelihood of bugs escaping to production.

Core Features & Use Cases

  • Formal Quality Gates: Establishes clear criteria for moving between Development, QA, UAT, and Production.
  • Bug Prevention: Catches quality issues early in the development lifecycle.
  • Use Case: When a feature is ready for QA, this skill ensures all unit tests are passing and code has been reviewed before QA begins their testing.

Quick Start

Use the quality-gates skill to define the quality gates for the current development phase.

Frequently Asked Questions about quality-gates

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

FAQPage Schema
How do I prevent bugs from escaping to production between delivery phases?

Quality gates prevent bugs escaping to production by enforcing predefined criteria before progressing between delivery phases. This four-gate framework ensures Development, QA, UAT, and Release Candidate phases meet agreed-upon standards before proceeding.

What criteria should be met before moving code from Dev to QA?

Moving code from Dev to QA requires passing unit tests and completing code reviews as defined by quality gates. This ensures the development phase meets predefined standards before QA begins formal testing.

How do I set up release management gates for UAT and production deployments?

Release management gates are set up by defining specific criteria for QA to UAT, UAT to Release Candidate, and Release Candidate to Production transitions. This framework provides a gate failure protocol and status tracker template to manage deployments.

What happens when a quality gate fails during the software delivery lifecycle?

When a quality gate fails during the software delivery lifecycle, a formal gate failure protocol is triggered. This prevents progression to the next delivery phase until the agreed-upon quality standards are fully met and verified.

Do I need specific testing frameworks to implement quality gates?

No specific testing frameworks are required to implement quality gates. The system provides a formal four-gate framework and criteria templates that define standards for delivery phases, independent of underlying testing tools.