Menu
Use when running or documenting a quality gate check for a release milestone. Covers gate criteria verification, evidence collection, and reporting.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
AI feature engineering — llama, embeddings, RAG quality, inference reliability, cost/token discipline.
System architecture, structured code review bar, and technical documentation.
Backend HTTP API, SQLite, Qdrant, integration contracts, schema and migration safety.
Maturity / inspection pass over [ORG_NAME] code sections (BCS). Load your org’s code-sections ledger, run verify ladder, update shared_context summary on main when columns change.
Data pipelines, ingest, remediation, entity quality — PDF/docs through to vector store.
Decision continuity, handoffs, supersession — Engineering Orchestrator (Mike) accountable; pair with session-notes.
| 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. |
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 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]
gates/ or docs/gates/../../../shared_context/project_status_sync.STUB.md