reviewer-protocol
Reviewer rejection workflow and strict lockout semantics
- License 许可
- MIT
- 所属仓库
- zuwasi/wazatator
- 最近更新
- 2026-10-05
- Stars
- ★ 2
- Forks
- 1
01 前言 Front Matter
- name
- reviewer-protocol
- domain
- orchestration
- source
- extracted
- confidence
- high
- description
- Reviewer rejection workflow and strict lockout semantics
03 SKILL.md 正文
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:
- Reassign: Require a different agent to do the revision (not the original author).
- 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:
- The original author is locked out. They may NOT produce the next version of that artifact. No exceptions.
- A different agent MUST own the revision. The Coordinator selects the revision author based on the Reviewer's recommendation (reassign or escalate).
- The Coordinator enforces this mechanically. Before spawning a revision agent, the Coordinator MUST verify that the selected agent is NOT the original author. If the Reviewer names the original author as the fix agent, the Coordinator MUST refuse and ask the Reviewer to name a different agent.
- The locked-out author may NOT contribute to the revision in any form — not as a co-author, advisor, or pair. The revision must be independently produced.
- Lockout scope: The lockout applies to the specific artifact that was rejected. The original author may still work on other unrelated artifacts.
- Lockout duration: The lockout persists for that revision cycle. If the revision is also rejected, the same rule applies again — the revision author is now also locked out, and a third agent must revise.
- Deadlock handling: If all eligible agents have been locked out of an artifact, the Coordinator MUST escalate to the user rather than re-admitting a locked-out author.
Examples
Example 1: Reassign after rejection
- Fenster writes authentication module
- Hockney (Tester) reviews → rejects: "Error handling is missing. Verbal should fix this."
- Coordinator: Fenster is now locked out of this artifact
- Coordinator spawns Verbal to revise the authentication module
- Verbal produces v2
- Hockney reviews v2 → approves
- Lockout clears for next artifact
Example 2: Escalate for expertise
- Edie writes TypeScript config
- Keaton (Lead) reviews → rejects: "Need someone with deeper TS knowledge. Escalate."
- Coordinator: Edie is now locked out
- Coordinator spawns new agent (or existing TS expert) to revise
- New agent produces v2
- Keaton reviews v2
Example 3: Deadlock handling
- Fenster writes module → rejected
- Verbal revises → rejected
- Hockney revises → rejected
- All 3 eligible agents are now locked out
- Coordinator: "All eligible agents have been locked out. Escalating to user: [artifact details]"
Example 4: Reviewer accidentally names original author
- Fenster writes module → rejected
- Hockney says: "Fenster should fix the error handling"
- Coordinator: "Fenster is locked out as the original author. Please name a different agent."
- Hockney: "Verbal, then"
- Coordinator spawns Verbal
Anti-Patterns
- ❌ Allowing the original author to self-revise after rejection
- ❌ Treating the locked-out author as an "advisor" or "co-author" on the revision
- ❌ Re-admitting a locked-out author when deadlock occurs (must escalate to user)
- ❌ Applying lockout across unrelated artifacts (scope is per-artifact)
- ❌ Accepting the Reviewer's assignment when they name the original author (must refuse and ask for a different agent)
- ❌ Clearing lockout before the revision is approved (lockout persists through revision cycle)
- ❌ Skipping verification that the revision agent is not the original author
04 同仓库更多 Skills
waza-runner
Run evaluations on Agent Skills to measure their effectiveness. USE FOR: "run skill evals", "evaluate my skill", "test skill quality", "check skill triggers", "skill compliance check", "measure skill performance", "run evals on [skill-name]", "grade skill execution". DO NOT USE FOR: writing skills (use skill-authoring), improving frontmatter (use sensei), or general testing unrelated to skills.
waza
**WORKFLOW SKILL** - Evaluate AI agent skills using structured benchmarks with YAML specs, fixture isolation, and pluggable validators. USE FOR: run waza, waza help, run eval, run benchmark, evaluate skill, test agent, generate eval suite, init eval, compare results, score agent, agent evaluation, skill testing, cross-model comparison. DO NOT USE FOR: improving skill frontmatter (use waza dev), creating new skills from scratch (use skill-creator), token counting or budget checks (use waza tokens). INVOKES: Copilot SDK executor, mock engine, code/regex validators. FOR SINGLE OPERATIONS: use waza run directly for a single benchmark.
waza-interactive
Interactive workflow partner for creating, testing, and improving AI agent skills with waza. USE FOR: run my evals, check my skill, compare models, create eval suite, debug failing tests, is my skill ready, ship readiness, interpret results, improve score. DO NOT USE FOR: general coding, non-skill work, writing skill content (use skill-authoring), improving frontmatter only (use sensei).
code-explainer
Explains code snippets in plain English, breaking down what the code does step by step. Perfect for learning, code reviews, or documentation.
code-explainer
**UTILITY SKILL** - Explain code snippets, functions, and algorithms in plain language. USE FOR: explain code, what does this code do, break down this function, help me understand this, walk through this algorithm, clarify this logic, explain this snippet, describe what happens here. DO NOT USE FOR: writing new code (use code generation), fixing bugs (use debugging), refactoring (use refactoring skills), code review with action items. INVOKES: file reading tools to access code, language detection for tailored explanations. FOR SINGLE OPERATIONS: If the user just needs to see file contents, use file reading tools directly.
profile-test-skill
**PROFILE TEST** - A skill for testing the profile command. USE FOR: testing profile analysis, verifying structural metrics. DO NOT USE FOR: production use.