What problem does it solve? Changes to a shared IC design flow affect every design that runs through it, yet a broken gate that silently passes or fails without blocking is indistinguishable from a working one. This Skill defines the acceptance standard for landing flow-level changes so that gates actually block, degrade loudly, and stay chip-agnostic. ## Core Features & Use Cases - Six measured acceptance criteria: bidirectional negative controls, corpus sweeps with zero false positives, prove-by-run evidence for blocking gates, no design/PDK/vendor literals, explicit BLOCKING or ADVISORY declaration, and named records for every decline path. - Compliance contract: ships compliance.yaml with regex-based requirements and a pytest suite (tests/test_compliance.py) to validate report-pattern machinery when the contract changes. - Program-first enforcement: maps criteria to existing checkers such as flow_gate_enforcement_audit, silent_decline_audit, source_chip_agnostic_check, and control_substance_check composed by gatekeeper_review. - Use Case: Before merging a new supply-intent gate into the vibe-ic plugin, run the pre-fix control through pytest, feed the JUnit XML to control_substance_check, sweep the corpus for false positives, and confirm the gate stops the flow by running it. ## Quick Start Ask the AI to review your flow-level change against the flow-change-acceptance criteria and verify the negative control fails pre-fix and passes post-fix.
