skills.rest
ronniegeraghty
ronniegeraghtyCOMMUNITY
Explore all skills by this author →
GitHub

reviewer-protocol

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

3|5|Updated Mar 19, 2026
Search Tags:#workflow#protocol#governance#escalation#reviewer#lockout#revision-control
One-click install
npx skills add https://github.com/ronniegeraghty/hyoka --skill reviewer-protocol-ronniegeraghty
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewer-protocol
Source: https://github.com/ronniegeraghty/hyoka/tree/main/.agents/skills/reviewer-protocol
Command: npx skills add https://github.com/ronniegeraghty/hyoka --skill reviewer-protocol-ronniegeraghty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The reviewer rejection workflow and strict lockout semantics enforce independent revision after a rejection, preventing the original author from self-revising and ensuring traceable, governance-driven improvements.

Core Features & Use Cases

  • Enforces reviewer-based approvals and rejections with clear options to reassign or escalate revisions to a different agent.
  • Applies strict lockout rules so the original author cannot contribute to the revised artifact, while the coordinator selects a suitable non-author agent.
  • Supports deadlock handling and escalation protocols to ensure timely resolution across complex review cycles.

Quick Start

Instruct the system to apply the reviewer-protocol rules to a new artifact awaiting revision.

Frequently Asked Questions about reviewer-protocol

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

FAQPage Schema
How do I enforce a reviewer rejection workflow that prevents the original author from self-revising?▼

A reviewer rejection workflow with strict lockout prevents the original author from self-revising by assigning the rejected artifact to a non-author agent. The coordinator selects a suitable alternate agent to ensure independent, traceable revisions.

What is the best way to handle deadlocks and escalation during complex team review cycles?▼

Deadlock handling and escalation protocols resolve stalled complex team review cycles by triggering timely escalation procedures. This ensures governance requirements are met and artifacts continue progressing through the review workflow without indefinite delays.

How do I ensure governance compliance and auditability for agent assignment in revision control?▼

Governance compliance and auditability for agent assignment are ensured by enforcing strict reviewer-driven revision workflows. The protocol tracks reviewer approvals, rejections, and reassignments, satisfying auditability requirements across all team review cycles.

Can I reassign an artifact to a different agent after a reviewer rejection?▼

Yes, you can reassign an artifact to a different agent after a reviewer rejection. The protocol applies strict lockout rules so the original author cannot contribute, while the coordinator selects a suitable non-author agent for the revision.

When do I need a lockout mechanism for revision control in a governance workflow?▼

A lockout mechanism for revision control is needed when governance workflows require independent revisions after a rejection. It prevents the original author from self-revising the artifact, ensuring traceable, governance-driven improvements and maintaining strict reviewer-based approval integrity.

Related Skills

Explore More Legal & Compliance Skills→
rett-europerett-europe
2

reviewer-protocol

Enforce lockout semantics for reviewer rejections in coordination workflows.

Official
Advanced
bmad-code-orgbmad-code-org
88

bmad-testarch-nfr

Execute a tri-mode NFR audit workflow and generate a gate-ready YAML report.

Official
Advanced
Golnaz89Golnaz89

reviewer-protocol

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

Community
Advanced
PlagueHOPlagueHO
2

reviewer-protocol

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

Community
Advanced