skills.rest
chdaly
chdalyCOMMUNITY
Explore all skills by this author →
GitHub

reviewer-protocol

Enforce reviewer rejection lockout rules and reassign revision authorship.

Updated Apr 10, 2026
Search Tags:#workflow#coordination#escalation#revision#rejection#reviewer#lockout
One-click install
npx skills add https://github.com/chdaly/eshop --skill reviewer-protocol-chdaly
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewer-protocol
Source: https://github.com/chdaly/eshop/tree/main/.copilot/skills/reviewer-protocol
Command: npx skills add https://github.com/chdaly/eshop --skill reviewer-protocol-chdaly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines how reviewers can approve or reject work and enforces strict lockout rules to prevent the original author from self-revising, ensuring independent revisions.

Core Features & Use Cases

  • Reviewer Rejection Protocol: Reviewers may reject and require either a different agent to revise or an escalation to bring in new expertise.
  • Strict Lockout Semantics: On rejection, the original author is locked out of the next revision; the coordinator assigns a new revision author and enforces the lockdown through the cycle.
  • The coordinator MUST enforce these rules automatically to prevent bypass or deadlocks.

Quick Start

When a reviewer rejects, instruct the system to reassign the revision to a different agent or escalate to a new expert, and enforce strict lockout on the original author.

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 rejection protocol enforces strict lockout semantics by automatically locking the original author out of the next revision and having the coordinator assign a different agent to handle the revision.

What is a reviewer rejection protocol in collaborative development workflows?▼

A reviewer rejection protocol is a workflow mechanism where reviewers approve or reject artifacts, and upon rejection, the coordinator escalates to bring in new expertise or reassigns the revision to a different agent.

How do I enforce secure revision ownership when coordinating multiple agents?▼

Secure revision ownership is enforced by coordinator logic that verifies agent eligibility, assigns a non-original author, and persists lockout rules across revision cycles to prevent bypass or deadlocks.

Can I escalate rejected artifacts to a new expert instead of reassigning to another agent?▼

Yes, when a reviewer rejects an artifact, the protocol allows the coordinator to either assign a different agent to revise the work or escalate to bring in new expertise for the revision cycle.

Do I need coordinator logic to manage lockout rules across revision cycles?▼

Yes, coordinator logic is required to assign a non-original author, verify eligibility, and automatically enforce lockout rules across revision cycles to prevent bypass or deadlocks.

Why does my revision workflow deadlock when enforcing author lockouts?▼

Revision workflows deadlock without coordinator logic to automatically enforce lockout rules and assign eligible non-original authors, which prevents bypass and resolves revision ownership conflicts.

Related Skills

Explore More Software Engineering Skills→
katylavakatylava

TDD Issues Workflow

Enforce a strict Test-Driven Development workflow for docs/ISSUES.md issues.

Community
Advanced
sudhakrmssudhakrms
1

reviewer-protocol

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

Community
Intermediate
webmaxruwebmaxru
49

reviewer-protocol

Enforce reviewer rejection workflows with lockout semantics on revisions.

Community
Advanced
lbouriezlbouriez

reviewer-protocol

Enforce reviewer rejection workflows with strict lockout of original authors.

Community
Advanced