quality-gate-design
Use this skill when you need evidence-bounded entry criteria, evidence requirements, owners, and exception paths for a delivery or release gate; triggers include 质量门禁 and quality gate.
SKILL.mdskills/en/testing-types/quality-gate-design/SKILL.md
GitHubQuality Gate Design
When to Use
- Use this skill when you need evidence-bounded analysis, design, or validation preparation for entry criteria, evidence requirements, owners, and exception paths for a delivery or release gate.
- Use it to review a plan, result, or metric and turn the review into executable improvements.
- Use it when input is incomplete but a bounded first pass with assumptions, gaps, and human-decision boundaries is still useful.
Output Format Options
- Default to Markdown organized by domain risk, evidence state, priority, and boundary.
- When the user requests tables, CSV, JSON, or ticket fields, preserve the same finding fields, evidence, and decision boundaries.
- Before machine consumption, confirm the schema, enums, required fields, and evidence sources.
How to Use
- Read and follow
prompts/quality-gate-design.md, including its input audit, domain coverage, and output order. - Extract scope, environment, version, time window, constraints, success criteria, and available evidence, with attention to gate objective, entry criteria, evidence source, owner role, exception and rollback.
- Separate confirmed facts, evidence-backed inferences, candidate recommendations, and Human decisions before ranking by risk and evidence strength.
- Turn high-risk items into preconditions, steps, expected behavior or decision criteria, required evidence, and a validation method.
- When input is incomplete, deliver a bounded first pass, state unsupported conclusions, and never present static material as execution evidence.
Reference Files
When calibrating domain outcomes, valid controls, or evidence gaps, read references/domain-decision-example.md for sanitized input, per-item oracles, and reproducible calculations.
Always read
prompts/quality-gate-design.md; it is the complete execution specification for this skill.For evaluation, read
evals/eval.yamland the matching cases underevals/cases/.Load
references/,examples/,scripts/, oroutput-formats.mdonly when those directories exist and the task needs them.
Domain Execution Essentials
- Define each obligation, evidence version/freshness, operator and PASS/FAIL/BLOCKED/UNKNOWN table. Execution prevented is BLOCKED; missing or indeterminate evidence is UNKNOWN; absence never means PASS.
- Apply project aggregation and fail-closed rules. Preserve unknown/blocked causes and recommend advancement only when all required gates have fresh valid evidence.
- Record exceptions separately with scope, authorizer, reason, approval, expiry, compensating controls and revocation. Invalid exceptions do not override or rewrite failures.
- State triggers, owners, revalidation and stop/rollback conditions. Separate design, evidence comparison and pipeline implementation; missing policy needs Human resolution.
Core Constraints
- Keep the analysis focused on entry criteria, evidence requirements, owners, and exception paths for a delivery or release gate; do not replace business owners or Human risk acceptance, exception approval, or release decisions.
- Never invent system behavior, fields, metrics, thresholds, data, root causes, execution records, or pass claims.
- Static design, plans, file presence, or a dry run retain their evidence state and cannot become proof of real execution.
- When evidence is insufficient, use pending confirmation, blocked, unassessed, or NOT_SCORED and give the smallest validation method.
- For production, privacy, or security work, use least privilege, masked data, mocks, dry runs, or isolation.
Delivery Checklist
- Covered gate objective, entry criteria, evidence source, owner role, exception and rollback, with source, evidence state, and validation method for each.
- Separated facts, inferences, candidate recommendations, gaps, and Human decisions.
- Gave high-risk items P0/P1/P2/P3 or an equivalent priority, owner role, and close condition.
- Did not turn plans, static checks, or dry runs into test execution, all-passed, or release-approved claims.
- Stated residual risk, stop/escalation conditions, and next actions.
Common Pitfalls
- Listing checks without triggers, expected concerns, owner roles, close conditions, and evidence.
- Treating adjacent metrics or tool names as a complete quality gate judgment.
- Using unexplained numbers for false precision or writing correlation as causation.
- Refusing incomplete input, or pretending that incomplete evidence is conclusive.
Best Practices
- Start with paths most likely to cause business loss, quality regression, or decision blockage.
- Use the smallest verifiable experiment to reduce uncertainty and record conditions, versions, sources, and evidence.
- Make the Skill independently installable, executable, and reviewable by another engineer.