qa-delivery

Define quality gates and risk criteria for software delivery pipelines.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/hilaryosborne/skills --skill qa-delivery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-delivery
Source: https://github.com/hilaryosborne/skills/tree/main/quality-assurance/qa-delivery
Command: npx skills add https://github.com/hilaryosborne/skills --skill qa-delivery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the need for a structured approach to ensuring quality within software delivery pipelines, focusing on identifying and mitigating risks before they impact production.

Core Features & Use Cases

  • Quality Gate Definition: Helps define and document quality criteria for different stages of the delivery process.
  • Risk Assessment: Facilitates the identification of potential quality issues and their impact.
  • Use Case: When preparing for a major release, use this skill to define the essential quality checks that must pass before deployment to production.

Quick Start

Use the qa-delivery skill to define the quality gates for the upcoming production release.

Frequently Asked Questions about qa-delivery

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

FAQPage Schema
What are quality gates in software delivery pipelines?

Quality gates in software delivery are predefined criteria that must pass before code progresses to production. They ensure structured risk assessment and mitigate potential failure modes during continuous integration and release management workflows.

How do I define quality gates for a production release?

To define quality gates for a production release, articulate clear acceptance criteria and document potential failure modes. This structures your quality checks to identify and mitigate risks before they impact production environments.

When do I need risk assessment criteria for continuous delivery?

You need risk assessment criteria for continuous delivery when preparing for major releases. It facilitates the identification of potential quality issues and their impact, ensuring risks are mitigated before deployment to production.

Can I use this approach for continuous integration workflows?

Yes, you can apply quality gate definition and risk assessment to continuous integration workflows. It requires clear articulation of acceptance criteria and potential failure modes to ensure quality throughout the delivery pipeline.

What is the best way to document acceptance criteria for release management?

The best way to document acceptance criteria for release management is to define them as structured quality gates. This approach identifies potential quality issues early and documents essential checks that must pass before production deployment.