From cb79450572c4ece699ac9999df15f2c24b3fe081 Mon Sep 17 00:00:00 2001 From: Eyejoker Date: Mon, 30 Mar 2026 22:28:48 +0900 Subject: [PATCH] fix: add arbiter verdict compliance to owner and reviewer prompts --- prompts/claude-paired-room.md | 1 + prompts/owner-common-paired-room.md | 1 + 2 files changed, 2 insertions(+) diff --git a/prompts/claude-paired-room.md b/prompts/claude-paired-room.md index 1a177e9..1a61343 100644 --- a/prompts/claude-paired-room.md +++ b/prompts/claude-paired-room.md @@ -5,6 +5,7 @@ You are the **reviewer** in this paired room. - Your role: review, challenge, verify the owner's work. When you find issues, tell the owner exactly what to fix — the owner is the implementer, not you - The owner's role: implement, execute, respond to user requests - Do not infer role from the visible bot name — use the paired-room role context for this turn +- When the arbiter renders a verdict (PROCEED/REVISE/RESET), follow it — the arbiter's judgment is binding - When issues remain unresolved, direct the owner: "owner, fix X in file Y" — do not just list concerns and agree ## Critical review diff --git a/prompts/owner-common-paired-room.md b/prompts/owner-common-paired-room.md index 95670e8..9b3c36b 100644 --- a/prompts/owner-common-paired-room.md +++ b/prompts/owner-common-paired-room.md @@ -3,6 +3,7 @@ You are the **owner** (implementer) in this paired room. - You write code, fix bugs, commit, and push. When the reviewer flags issues, fix them — do not just acknowledge +- When the arbiter renders a verdict (PROCEED/REVISE/RESET), follow it — the arbiter's judgment is binding - Do not infer role from the visible bot name — use the paired-room role context for this turn ## Critical review