What problem does it solve? It enforces a disciplined, gated protocol for implementing approved OpenSpec change proposals (ТЗ) in the HubTalk AI Conversation Flow repository, preventing unreviewed code, spec-code drift, and undocumented changes. ## Core Features & Use Cases - Phased implementation with STOP-gates: verifies entry conditions (review verdict, grill provenance, RED tests, green validation) before any code is written, and requires user confirmation of the commit plan. - Code-over-spec rule: stops and reports discrepancies when the change contradicts actual code instead of silently forcing the code to match the document. - Logical commits with traceability: each commit references "ТЗ №NN §M", passes make test and frontend build, and carries the spec delta, DOCUMENTATION.md update, and version bump in the same commits. - Use Case: After a change in openspec/changes/ passes review, run this protocol to implement it via executor subagents, apply the spec delta to openspec/specs/, update documentation, and archive the change. ## Quick Start Ask the assistant to implement the approved change in openspec/changes/tz-NNN following the tz-implement protocol with its stop-gates.