Audit whether an enforced-coordination MCP has actually shrunk its ~19 legacy etiquette verbs into the 5 enforced tools — work/act/ask/recall/status — each carrying one denial shape and one transcript event, migrated through a real retirement path (intake-metadata, alias, or doc-history — never a parallel runtime), with zero legacy-verb calls once a body reaches compliance mode C4+. Use when reviewing a broker-collapse migration plan, gating a body's move from advisory (C0-C3) to enforced (C4+) coordination, or verifying IT-018 Broker Collapse compliance. NOT for the inbound trigger→spawn boundary that decides whether an event may spawn an agent at all (use fleet-event-spawn-trust), the capability-token cryptographic mechanism behind a denial (use agentic-zero-trust-security), designing how a swarm of agents invokes and shards work (use swarm-invocation-designer), or auditing an individual PR's mergeability (use agent-pr-authoring).
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Audit whether an enforced-coordination MCP has actually shrunk its ~19 legacy etiquette verbs into the 5 enforced tools — work/act/ask/recall/status — each carrying one denial shape and one transcript event, migrated through a real retirement path (intake-metadata, alias, or doc-history — never a parallel runtime), with zero legacy-verb calls once a body reaches compliance mode C4+. Use when reviewing a broker-collapse migration plan, gating a body's move from advisory (C0-C3) to enforced (C4+) coordination, or verifying IT-018 Broker Collapse compliance. NOT for the inbound trigger→spawn boundary that decides whether an event may spawn an agent at all (use fleet-event-spawn-trust), the capability-token cryptographic mechanism behind a denial (use agentic-zero-trust-security), designing how a swarm of agents invokes and shards work (use swarm-invocation-designer), or auditing an individual PR's mergeability (use agent-pr-authoring).
license
Apache-2.0
allowed-tools
Read,Write,Edit,Bash,Grep,Glob
metadata
{"category":"Agent & Orchestration","tags":["broker-collapse","verb-migration","coordination-mcp","compliance-gate","legacy-etiquette-verbs"],"provenance":{"kind":"first-party","owners":["port-daddy"]},"pairs-with":[{"skill":"fleet-event-spawn-trust","reason":"fleet-event-spawn-trust guards whether an inbound event may spawn an agent at all; this skill audits the enforced tool surface that call lands on once coordination is turned on."},{"skill":"agentic-zero-trust-security","reason":"This skill only checks that every broker tool DECLARES a denial shape and a transcript event; agentic-zero-trust-security supplies the cryptographic capability mechanism that actually backs the denial."},{"skill":"swarm-invocation-designer","reason":"swarm-invocation-designer decides how agents summon each other and shard work; this skill audits the etiquette-verb surface those invocations call through once coordination is enforced."},{"skill":"articles-of-agreement-auditor","reason":"The 5 broker tools are how agents exercise the tool-use and reporting clauses of the Articles contract that skill audits."}],"io-contract":{"kind":"deliverable","consumes":["[Truncated]","[Truncated]"],"produces":["[Truncated]","[Truncated]"]}}
Coordination Verb Broker Migration
Audit whether an enforced-coordination MCP has really shrunk — not grown — its legacy etiquette verbs into the 5 enforced tools, with a real migration path and a hard compliance gate.
Use This For
Reviewing a broker-collapse migration plan before it ships, confirming every legacy verb maps to exactly one of work/act/ask/recall/status.
Verifying each of the 5 enforced tools carries one denial shape and one transcript event before advisory bodies are asked to depend on it.
Gating a body's promotion from advisory coordination (C0-C3) to enforced coordination (C4+) against the IT-018 Broker Collapse requirement of zero legacy-verb calls.
Catching a "parallel runtime truth" migration — a legacy verb kept alive as a second live code path instead of being retired to metadata, an alias, or documented history.
Producing a deterministic pass/fail signal for CI or a governance review, not a prose opinion about how the migration "feels."
Do Not Use This For
Deciding whether an inbound event should be allowed to spawn an agent at all (fleet-event-spawn-trust).
Specifying the cryptographic mechanism (signed capability token, macaroon, etc.) behind a broker tool's denial (agentic-zero-trust-security).
Designing how agents discover and invoke each other or shard work across a swarm (swarm-invocation-designer).
Collapse Gate
flowchart TD
A[Enumerate every legacy etiquette verb] --> B{mappedTo one of work/act/ask/recall/status?}
B -->|null or unrecognized| C[verb-unmapped: FAIL]
B -->|yes| D{migrationPath is intake-metadata, alias, or doc-history?}
D -->|anything else, incl. parallel-runtime| E[parallel-runtime-migration: FAIL]
D -->|yes| F{Broker tool surface is exactly the 5?}
F -->|extra tool| G[broker-grew: FAIL]
F -->|missing tool| G2[broker-tool-missing: FAIL]
F -->|exactly the 5| H{Every tool has denialShape AND transcriptEvent?}
H -->|no| I[broker-tool-no-denial-or-transcript: FAIL]
H -->|yes| J{complianceMode is C4 or above?}
J -->|yes, and emitsLegacyVerbCalls| K[c4plus-emits-legacy-verbs: FAIL]
J -->|no, or yes with zero legacy calls| L[PASS: broker has actually shrunk]
Enumerate the full legacy-verb inventory. The documented collapse expects ~19 verbs; reconcile the spec's legacyVerbs list against that inventory before trusting anything downstream.
Confirm every verb's mappedTo target. A null mapping, or a value that isn't one of the 5 canonical tools, means an old client can still call that verb forever with no enforced counterpart.
Confirm every verb's migrationPath is a real retirement. Only intake-metadata, alias, and doc-history count. Anything else — named "parallel-runtime" or not — means a second live implementation still answers the same question as the new tool.
Confirm the broker tool surface is exactly the 5. No bridge/shim/compat tool, and none of the 5 missing — a legacy verb mapped to a tool that doesn't exist is not actually migrated.
Confirm every one of the 5 tools declares a denial shape and a transcript event. A tool that can't reject a call in one documented shape, or can't be proven to have run via one documented event, isn't auditable as enforced.
Check the declared complianceMode.C0-C3 may still emit legacy-verb calls without penalty; C4 and above must prove emitsLegacyVerbCalls: false (see references/compliance-mode-gate-ladder.md for how to prove it from a transcript, not source code).
Run scripts/broker_migration_audit.mjs and treat any critical finding as a hold on calling the migration done.
Output Contract
The scorer reads a JSON spec with these fields:
brokerTools[]: { name, denialShape: bool, transcriptEvent: bool } — should be exactly work/act/ask/recall/status.
Use scripts/broker_migration_audit.mjs to audit that spec and return { pass, score, findings, recommendations }.
Anti-Patterns
The Silent Unmapped Verb
Novice: Ship a migration plan where a legacy verb is just... left off the mapping table, on the assumption someone will get to it later.
Expert: Every legacy verb needs an explicit, valid mappedTo target before the plan counts as done — an absent or unrecognized mapping is exactly the verb an old client keeps calling forever with no enforced counterpart.
Detection: broker_migration_audit.mjs fires verb-unmapped (critical) when a legacy verb's mappedTo is null or is not one of the 5 canonical tools, and legacy-inventory-incomplete (high) when the total verb count doesn't match the documented ~19.
The Bridge Tool ("just for now")
Novice: Add a 6th tool (legacy_bridge, verb_router, a "compat layer") to shim old callers over to new tools temporarily, and let it become permanent — or quietly drop one of the 5 while adding it.
Expert: The broker surface is exactly 5 tools, forever, each fully equipped. Any 6th tool is the collapse failing to happen; any missing one of the 5 means legacy verbs are mapped to a tool that doesn't exist.
Detection: Fires broker-grew (critical) when brokerTools contains a name outside work/act/ask/recall/status, broker-tool-missing (critical) when one of the 5 is absent, and broker-tool-no-denial-or-transcript (critical) when a present tool lacks a denial shape or a transcript event.
Parallel Runtime Truth
Novice: Keep a legacy verb's original implementation live "just in case," routing some callers to it and some to the new tool — and call that the migration. Then declare enforced compliance while the old calls quietly keep flowing.
Expert: A legacy verb's real retirement path is intake-metadata, an alias, or documented history — never a second live code path. And a body claiming C4+ must prove, from its own transcript, that it makes zero legacy-verb calls — not just that its source code intends to stop.
Detection: Fires parallel-runtime-migration (critical) when any legacy verb's migrationPath isn't intake-metadata/alias/doc-history, and c4plus-emits-legacy-verbs (critical) when a C4+ body's emitsLegacyVerbCalls is still true.
References
File
Load When
references/verb-collapse-migration-paths.md
Building or reviewing the legacy-verb-to-tool mapping table, or deciding which of the 3 real retirement paths a verb should take.
references/compliance-mode-gate-ladder.md
Gating a body's compliance-mode claim, or figuring out how to actually prove emitsLegacyVerbCalls: false.
examples/expected-output.md
Need to see a bad migration audited, then the same migration fixed and passing.
examples/sample-input.json
Need a complete, passing broker-migration spec to start from.
templates/output-template.md
Need a reusable migration gap report template to fill in.
schemas/broker-migration-spec.schema.json
Need to validate a broker-migration-spec JSON payload's structure before auditing it.
scripts/broker_migration_audit.mjs
Need deterministic scoring of a broker-collapse migration's completeness.
agents/openai.yaml
Need a subagent descriptor for delegated broker-migration auditing.
README.md
Need the quick-start path through this skill's files.
CHANGELOG.md
Need this skill's version history.
Skill Bundle Index
Every file in this skill, and when to open it. Auto-generated; run scripts/index_references.py --fix.
examples/expected-output.md — Example Output: Coordination Verb Broker Migration — Scenario: a team ships a "broker collapse" migration plan that looks done — it has a mapping table and a compliance-mode declaration — but o
references/compliance-mode-gate-ladder.md — Compliance Mode Gate Ladder — Use this when you need to decide what a body's declared compliance mode (C0-C6) actually obligates it to, or when you're gating a body's
references/verb-collapse-migration-paths.md — Verb Collapse & Migration Paths — Use this when you need to build or review the legacy-verb-to-broker-tool mapping itself: which of the ~19 legacy etiquette verbs maps to whi