skills.rest
olivomarco
olivomarcoCOMMUNITY
Explore all skills by this author →
Website𝕏@olivomarcoGitHub

reviewer-protocol

Enforce reviewer rejection governance and lockout rules for revision tasks.

66|41|Updated Mar 4, 2026
Search Tags:#workflow#protocol#escalation#coordinator#rejection#reviewer#lockout
One-click install
npx skills add https://github.com/olivomarco/vbd-copilot --skill reviewer-protocol-olivomarco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewer-protocol
Source: https://github.com/olivomarco/vbd-copilot/tree/main/.copilot/skills/reviewer-protocol
Command: npx skills add https://github.com/olivomarco/vbd-copilot --skill reviewer-protocol-olivomarco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines and enforces a governance pattern for reviewer-based feedback, preventing self-revision after rejection and ensuring artifacts are revised by non-author agents.

Core Features & Use Cases

  • Reviewer Rejection Protocol: Reviewers may approve or reject work and choose to reassign or escalate to a new agent with appropriate expertise.
  • Strict Lockout Semantics: On rejection, the original author is locked out from producing the next version; a different agent must revise, and the Coordinator ensures this rule is followed.
  • Deadlock and Escalation Handling: If all eligible agents are locked out, escalate to the user; the protocol supports deadlock resolution and prevents bypassing the rules.

Quick Start

Integrate this protocol into your team workflow to automatically route rejected artifacts to non-author 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 a developer from revising their own code after a reviewer rejection?▼

You enforce reviewer rejection by applying strict lockout semantics that block the original author from producing the next version, requiring a Coordinator to spawn a non-author revision agent.

How does a reviewer rejection protocol handle deadlock when all eligible agents are locked out?▼

A reviewer rejection protocol handles deadlock by escalating the rejected artifact to the user when all eligible agents are locked out, ensuring deadlock resolution without bypassing the governance rules.

What is the role of a Coordinator in enforcing a reviewer rejection workflow?▼

In a reviewer rejection workflow, the Coordinator validates the rejection and spawns the correct revision agent, ensuring deterministic lockout rules are followed and independent revision ownership is maintained.

Can a reviewer reassign rejected work to a new agent instead of escalating?▼

Yes, a reviewer can reassign rejected work or escalate it to a new agent with the appropriate expertise, ensuring artifacts are revised by non-author agents within the governance protocol.

Does the lockout enforcement apply to QA tasks and artifact revisions as well as code reviews?▼

Yes, lockout enforcement applies to code reviews, artifact revisions, and QA tasks, ensuring that any rejected work is revised by a non-author agent rather than the original creator.

Related Skills

Explore More Content & Communication Skills→
WayneWalterBerryWayneWalterBerry

reviewer-protocol

Enforce reviewer rejection workflows with lockout rules preventing original author self-revision.

Community
Advanced
sudhakrmssudhakrms
1

reviewer-protocol

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

Community
Intermediate
Golnaz89Golnaz89

reviewer-protocol

Orchestrates reviewer-driven rejection workflows with enforced non-author revision lockouts.

Community
Advanced
webmaxruwebmaxru
49

reviewer-protocol

Enforce reviewer rejection workflows with lockout semantics on revisions.

Community
Advanced