What problem does it solve? In multi-agent teams, rejected work often gets bounced back to the original author, creating defensive self-revision loops and weak independent review. This Skill defines a strict protocol so coordinators enforce lockout rules and route revisions to different agents. ## Core Features & Use Cases - Reviewer Rejection Protocol: Reviewers approve or reject work, and on rejection must choose reassignment to a different agent or escalation to a new specialist. - Strict Lockout Semantics: The original author is mechanically locked out of revising the rejected artifact, including as co-author or advisor, for the full revision cycle. - Deadlock Handling: When all eligible agents are locked out of an artifact, the coordinator escalates to the user instead of re-admitting a locked-out author. - Use Case: A tester rejects an authentication module written by one agent; the coordinator verifies the named revision agent is not the original author, spawns a different agent to produce v2, and keeps the lockout until the revision is approved. ## Quick Start Apply the reviewer-protocol rules whenever a reviewer rejects an artifact so the coordinator locks out the original author and assigns the revision to a different agent.
