What problem does it solve? Delivery agents working on the ZZ platform need one authoritative set of rules for how initiatives are opened, documents are written and approved, gates are recorded, and plugins are reached — without each flow duplicating rules that drift out of sync. ## Core Features & Use Cases - Initiative and document state machine: Defines every allowed transition — initiative_open, document_write, document_approve, document_revise, initiative_close — and what the platform refuses, so agents never guess workflow state. - Gate and envelope governance: Enforces that approvals are recorded via document_approve in the same turn agreement is given, that envelope fields (status, approved_by, outcome) are platform-written only, and that revisions always carry a recorded cause. - Plugin discovery rules: Instructs agents to choose capabilities by reading skills via skill_list, to treat a missing tool as a signal that a plugin is not installed, and to confirm reachability when a flow commits to a plugin. - Use Case: An agent starting any flow (sdlc-flow, zz-plugin-eval, or future flows) loads this skill first to learn how to open an initiative, compute the next move with initiative_status, record approvals, and close with a truthful outcome. ## Quick Start Load the zz-platform skill at the start of any flow on the ZZ platform before the flow's own entry skill.
