gate-check

name	gate-check
description	Use when running or documenting a quality gate check for a release milestone. Covers gate criteria verification, evidence collection, and reporting.

Gate Check Procedure

When to Use

Invoke this skill when verifying that a version milestone (V1.5.1, V1.5.2, V1.6, etc.) has met its gate criteria before proceeding to the next phase.

Gate Check Steps

1. Load gate criteria from the relevant roundtable or roadmap document
2. For each criterion:
   • Verify with code evidence (test results, file existence, API behavior)
   • Mark as PASS or FAIL with evidence reference
   • If FAIL, document what's missing and who owns the fix
3. Run the full test suite — capture pass count, failure count, regression count
4. Document results in a gate report

Gate Report Format

# Gate Report: [Version] [Phase]

**Date:** YYYY-MM-DD
**Gate:** [Milestone name — from **PRODUCT_CONTEXT** / release plan]
**Evaluator:** [Agent Name]
**Test baseline:** [Record count from `pytest --collect-only` or CI — re-verify after pulls; no baseline ships in this pack]
**Tests passing:** [NNN]
**Regressions:** [N]

## Criteria Results

| # | Criterion | Status | Evidence |
|---|-----------|--------|----------|
| 1 | [Criterion text] | PASS/FAIL | [File or test reference] |

## Summary

- **Gate status:** PASS / FAIL / PARTIAL
- **Blocking items:** [list if any]
- **Recommendation:** [proceed / fix and recheck / escalate]

Filing

• Save gate reports in gates/ or docs/gates/
• If gate passes, update ../../../shared_context/project_status_sync.STUB.md
• If gate fails, create blockers in the Engineering session notes and notify HQ if cross-org impact