reviewer-protocol

Name: reviewer-protocol
Availability: InStock
Author: sudhakrms

Coordinate reviewer-driven rejection workflows that lock out original authors and assign new revision agents.

1|Updated Apr 17, 2026

Search Tags:#workflow #escalation #artifact #revision #rejection #reviewer #lockout

Ready to run

npx skills add https://github.com/sudhakrms/CalendarControl --skill reviewer-protocol-sudhakrms

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reviewer-protocol
Source: https://github.com/sudhakrms/CalendarControl/tree/main/coffee/.copilot/skills/reviewer-protocol
Command: npx skills add https://github.com/sudhakrms/CalendarControl --skill reviewer-protocol-sudhakrms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents post-rejection self-revisions by the original author by enforcing a reviewer-driven workflow that locks out the author until a new revision is produced.

Core Features & Use Cases

Enforce lockout on the original author after a rejection.
Allow reassignment or escalation to a new revision agent with appropriate expertise.
Ensure the revision is independently produced and reviewed before re-entry into the workflow.
Use Case: A tester rejects a module; the coordinator locks out the author and spawns a new agent to produce v2 for review.

Quick Start

Configure a workflow where a Reviewer rejects an artifact, locks out the original author, and spawns a new agent to produce the revised version.

Frequently Asked Questions about reviewer-protocol

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent an author from revising their own work after a reviewer rejects it?▼

A reviewer-driven rejection workflow enforces strict lockout semantics on the original author after rejection, requiring a new agent to independently produce revisions before re-entry into the review cycle.

What is a reviewer-driven rejection workflow with lockout semantics?▼

A reviewer-driven rejection workflow is a process where a reviewer rejects an artifact, locks out the original author, and spawns a new revision agent to ensure independent correction before re-entry into the review cycle.

How do I escalate a workflow deadlock when a revision agent cannot be assigned?▼

The reviewer protocol persists lockout through the revision cycle and triggers deadlock escalation to reassign or escalate the artifact to a new revision agent with appropriate expertise.

Does the reviewer-driven lockout persist across the entire revision cycle?▼

Yes, the lockout persists through the entire revision cycle, ensuring the original author remains locked out until a new agent independently produces and reviews the revised artifact for workflow re-entry.

When do I need to enforce independent revisions in an artifact review process?▼

You need to enforce independent revisions when a reviewer rejects an artifact and the original author must be locked out to prevent self-revisions, requiring a new agent to produce the revised version independently.

Can I reassign an escalated artifact to a specific revision agent after lockout?▼

Yes, after locking out the original author, the workflow allows reassignment or escalation to a new revision agent with appropriate expertise to independently produce the revised artifact for review.