Quality Gate Management
Skill Purpose: Define, enforce, and report quality gates for testing, security, and performance.
Core Skill Pattern
Objective: Ensure releases meet agreed standards before promotion.
Universal Pattern:
- •Define gate criteria (tests, coverage, security)
- •Map gates to CI checks
- •Enforce pass/fail policies
- •Document exceptions and approvals
- •Report gate status per release
Key Decisions (Project-Specific):
- •Gate thresholds and owners
- •Exception and override process
- •Required evidence for approvals
Project-Specific Implementation Notes
Customize per project:
- •Align gates with department quality policies
- •Keep gates minimal but meaningful
Example Gate Checklist
code
- Unit tests pass - Coverage >= 80% - Security scan has no high severity issues - Performance budget within limits
Best Practices
- •Keep gates measurable and automated
- •Tie gates to business risk
- •Limit manual overrides
- •Publish gate status in release notes
- •Review gates quarterly
Stop Conditions
STOP and escalate if:
- •Gate criteria are undefined
- •Overrides are undocumented
- •CI cannot enforce gates
Skill Version: 1.0.0