What problem does it solve? Coordinators in a multi-agent build pipeline need a single source of truth for cross-feature API contract declarations (actors, resources, fixtures, error envelopes, test endpoints) and a way to arbitrate when feature leads disagree about shared flow declarations. Without it, feature files duplicate declarations, merge conflicts fire at load time, and builders keep failing against stale flow files. ## Core Features & Use Cases - _shared.json ownership: Seeds and maintains global actors (anonymous, bearer, Keycloak ROPC, api-key, oauth-scoped), cross-feature resources, fixtures, error-envelope config, and test-endpoint registry entries. - Cross-task flow arbitration: Resolves flow_escalation mails from leads, deciding which feature file owns a flow whose endpoints span multiple features using the leaf-action placement rule. - Worktree-aware edits: Writes mid-chunk fixes directly into each affected builder's git worktree so probe failures resolve in one commit instead of mail round-trips. - Use Case: After finishing a product plan, a coordinator seeds _shared.json with Keycloak-backed role actors and the project's error envelope, then later arbitrates a FLOW_MERGE_CONFLICT between two feature files by promoting the disputed actor into _shared.json. ## Quick Start Invoke this skill after completing product-plan to seed _shared.json with global actors, fixtures, and the error envelope for the new initiative.
