skills.rest
quaid-app
quaid-appOFFICIAL
Explore all skills by this author →
WebsiteGitHub

reviewer-protocol

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

3|3|Updated Apr 13, 2026
Search Tags:#workflow#governance#review#coordinator#team#rejection#lockout
One-click install
npx skills add https://github.com/quaid-app/quaid --skill reviewer-protocol-quaid-app
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewer-protocol
Source: https://github.com/quaid-app/quaid/tree/main/.copilot/skills/reviewer-protocol
Command: npx skills add https://github.com/quaid-app/quaid --skill reviewer-protocol-quaid-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When teams collaborate on artifacts, misaligned feedback can lead to self-revision and unsafe review loops. The protocol defines how reviewers can approve or reject work and enforces strict lockout rules to ensure the original author cannot revise after rejection.

Core Features & Use Cases

  • Reviewer Rejection Protocol: Reviewers may approve or reject artifacts; on rejection, the reviewer can either reassign revision to a different agent or escalate to involve new expertise.
  • Strict Lockout Semantics: When an artifact is rejected, the original author is locked out from producing the next version; a new revision owner is chosen by the Coordinator.
  • Governance & Safe Escalation: Ensures mechanical enforcement by the Coordinator, supports deadlock handling, and prevents dead-end cycles by escalation when needed.

Quick Start

In practice, implement the Reviewer Rejection Protocol to assign a different agent or escalate when a rejection occurs, ensuring the original author is locked out during 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 revising their own work after a team review rejection?▼

A reviewer rejection protocol enforces strict lockout rules to prevent self-revision after an artifact is rejected. The Coordinator mechanically assigns a different agent to produce the next version, ensuring non-original author revision and safe review loops.

What happens to a rejected artifact when a team reviewer escalates instead of reassigning?▼

Escalating a rejected artifact involves new expertise to resolve the review deadlock. The Coordinator manages this escalation to prevent dead-end cycles and ensure the artifact progresses through the governance workflow safely.

How does a coordinator enforce governance rules during a code or document review workflow?▼

The Coordinator mechanically enforces reviewer roles by managing rejection workflows, applying strict lockout semantics, and handling deadlocks. It ensures non-original author revision and prevents self-revision during team reviews of modules, code, or documents.

Can I use this rejection lockout protocol for team reviews of both code and documentation artifacts?▼

Yes, the reviewer rejection protocol supports team reviews across various artifacts including modules, code, or documents. It enforces lockout rules and coordinator governance regardless of the specific artifact type being reviewed.

How do I handle a deadlock when a reviewer keeps rejecting an artifact and no new revision owner is available?▼

The protocol handles deadlocks by allowing the reviewer to escalate the rejected artifact to involve new expertise. This safeguard prevents dead-end cycles when standard reassignment cannot resolve the review loop.

Related Skills

Explore More Product & Management Skills→
AshleyHollisAshleyHollis

reviewer-protocol

Enforce structured artifact review workflows with author lockout after rejection.

Community
Advanced
gaofeng21cngaofeng21cn
8

opl-workspace-handoff-writer

Generate five OPL handoff packet types with strict truth adherence.

Community
Intermediate
lbouriezlbouriez

reviewer-protocol

Enforce reviewer rejection workflows with strict lockout of original authors.

Community
Advanced
ronniegeraghtyronniegeraghty
3

reviewer-protocol

Enforce reviewer-driven revision workflows with strict lockout and non-author assignment.

Community
Advanced