reviewer-protocol Skill
Reviewer rejection workflow and strict lockout semantics Published by microsoft in frontier-agentic-devops-rvas.
Decision snapshot
Is this a fit?
Developers using frontier-agentic-devops-rvas, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is reviewer-protocol Skill?
Reviewer rejection workflow and strict lockout semantics Published by microsoft in frontier-agentic-devops-rvas. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using frontier-agentic-devops-rvas
Declared skill metadata
- Source file: .squad/templates/skills/reviewer-protocol/SKILL.md
Compatibility and setup
- Install or run with Copy skill directory
When to use reviewer-protocol Skill
- Use it for developers using frontier-agentic-devops-rvas.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/frontier-agentic-devops-rvas
- Skill file: .squad/templates/skills/reviewer-protocol/SKILL.md
What it does
Reviewer rejection workflow and strict lockout semantics
Skill instructions
Context When a team member has a Reviewer role (e.g., Tester, Code Reviewer, Lead), they may approve or reject work from other agents. On rejection, the coordinator enforces strict lockout rules to ensure the original author does NOT self-revise. This prevents defensive feedback loops and ensures independent review. Patterns Reviewer Rejection Protocol When a team member has a Reviewer role: - Reviewers may approve or reject work from other agents. - On rejection, the Reviewer may choose ONE of: 1. Reassign: Require a different agent to do the revision (not the original author). 2. Escalate: Require a new agent be spawned with specific expertise. - The Coordinator MUST enforce this. If the Reviewer says "someone else should fix this," the original agent does NOT get to self-revise. - If the Reviewer approves, work proceeds normally. Strict Lockout Semantics When an artifact is rejected by a Reviewer: 1. The original author is locked out. They may NOT produce the next version of that ar
Verified compatibility and discovery
Frequently asked questions
What is reviewer-protocol?
reviewer-protocol is a open-source AI agent skill with Copy skill directory. Reviewer rejection workflow and strict lockout semantics
Who is reviewer-protocol best for?
reviewer-protocol is best for reusing agent instructions, scripts, and references.
How do I install reviewer-protocol?
Install or run reviewer-protocol using Copy skill directory. Check reviewer-protocol for the latest setup command.
Is reviewer-protocol actively maintained?
reviewer-protocol may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
