skills.rest
robpitcher
robpitcherCOMMUNITY
Explore all skills by this author →
GitHub

reviewer-protocol

Enforce reviewer-based rejection workflows that lock out original authors from revising.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Reviewer Rejection Protocol establishes clear rules to prevent the original author from re-editing work after a rejection, ensuring that revisions are produced by a different agent or a newly escalated expert.

Core Features & Use Cases

  • Reviewer Rejection Protocol: Reviewers can approve or reject work; on rejection, they can require a different agent to revise or escalate to bring in fresh expertise. The Coordinator enforces that the original author does not revise the artifact.
  • Strict Lockout Semantics: After a rejection, the original author is prevented from contributing to the revision; a non-original author must own the next iteration, and there are safeguards to avoid naming the original author as the fix agent.
  • Use Cases: Reassign after rejection to a different engineer, escalate to a new expert for critical gaps, and handle deadlocks by escalation when all eligible agents are locked out.

Quick Start

Upon reviewing, if you reject, require a different agent to revise (not the original author) or escalate and ensure the original author is locked out for the upcoming revision.

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 self-revising their work after a review rejection?▼

To enforce independent revision after a rejection, apply a reviewer rejection protocol with strict lockout semantics. The coordinator validates reviewer recommendations, blocks the original author from contributing, and ensures a different agent owns the next iteration of the artifact.

What happens during a reviewer rejection workflow when all eligible agents are locked out?▼

When all eligible agents are locked out in a reviewer rejection workflow, the protocol handles the deadlock by triggering an escalation. Escalation brings in fresh expertise to ensure the rejected artifact still receives an independent revision from a newly assigned expert.

Can I escalate a rejected artifact to a new expert instead of reassigning it within the team?▼

Yes, you can escalate a rejected artifact to a new expert instead of reassigning it. The reviewer rejection protocol supports escalation for critical gaps, bringing in fresh expertise while maintaining the lockout that prevents the original author from self-revising the work.

How does a coordinator enforce governance constraints during a team review?▼

A coordinator enforces governance constraints during a team review by validating reviewer recommendations and applying strict lockout semantics. This prevents the original author from self-revising after a rejection and requires a different agent or escalated expert to own the next iteration.

What safeguards prevent naming the original author as the fix agent after a rejection?▼

Reviewer rejection protocols include strict lockout safeguards specifically designed to avoid naming the original author as the fix agent after a rejection. These governance constraints enforce that a non-original author must own the next iteration of the revised artifact.

Related Skills

Explore More Content & Communication Skills→
quaid-appquaid-app
3

reviewer-protocol

Coordinate reviewer rejection workflows with enforced lockout rules preventing self-revision.

Official
Advanced
sudhakrmssudhakrms
1

reviewer-protocol

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

Community
Intermediate
yjwongyjwong
53

sheets

Fetch Lark Sheets data via the lark CLI and return structured JSON.

Community
Basic
PlagueHOPlagueHO
2

reviewer-protocol

Enforce reviewer rejection workflows with strict lockout preventing self-revision.

Community
Advanced