reviewer-protocol

To prevent authors from revising their own work after a rejection, you need strict lockout semantics. This Skill mechanically enforces lockout rules, blocking the original author from further revisions to ensure independent reviews.

A reviewer rejection workflow for independent reviews is a structured process where reviewers approve or reject work and can reassign or escalate. It includes strict lockout rules to prevent defensive feedback loops in team collaboration.

To handle deadlocks when all eligible agents are locked out of an artifact, the system escalates the issue to the user. This ensures collaborative project management workflows do not stall completely when strict lockout semantics are applied.

Yes, a coordinator can mechanically enforce lockout rules for software development reviews. This Skill applies coordinator enforcement to prevent original authors from self-revising their rejected artifacts during the review process.

Yes, this reviewer protocol works without external dependencies. It operates independently using its built-in scripts to enforce the structured rejection workflow and strict lockout semantics for your project management coordination.