zz-router

What problem does it solve? When working on the ZZ platform, delivery requests must follow an installed flow with declared stages, documents, and approval gates. This Skill removes the guesswork of choosing the right flow by inspecting the request and dispatching to the correct one, while preventing agents from resuming work from conversation memory instead of the platform's recorded state. ## Core Features & Use Cases - Flow selection: Distinguishes between sdlc-flow for software delivery work and zz-plugin-eval for grading or confirming readings of plugins, then loads the chosen flow via the zz-core skill_read MCP tool. - Initiative resumption: Calls initiative_status to compute the next move from the flow manifest and document envelopes when continuing existing work, never relying on conversation memory. - Governance enforcement: Ensures documents are written through document_write, document_patch, or document_revise into the team store, and that gates pass only through recorded document_approve calls. - Use Case: A team member says "continue the payment-service initiative" — the Skill first calls initiative_status to find the current stage, then loads sdlc-flow and follows its method exactly. ## Quick Start Ask the agent to continue an existing ZZ initiative or start new delivery work, and it will route the request to the right installed flow.