From f349c940f0fea686f4253c8f295398e2290a2045 Mon Sep 17 00:00:00 2001 From: mesh-tools Date: Thu, 15 Oct 2026 11:21:37 +0000 Subject: [PATCH] Cap review rounds at three to five and report the allowance used, in playbook 07 A reviewer that does not know its round keeps finding the next smaller thing: one decision record went through nine rounds on 2026-10-15, each spending the operator's shared weekly allowance. The operator asked for three to five rounds, the round told to the reviewer, and the allowance in every report. Co-Authored-By: Claude Opus 5.5 --- 00-META/process/07-feature-branches.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/00-META/process/07-feature-branches.md b/00-META/process/07-feature-branches.md index 5a4acb24..bd8584cb 100644 --- a/00-META/process/07-feature-branches.md +++ b/00-META/process/07-feature-branches.md @@ -120,10 +120,16 @@ reviews and delivers at the end. The agents never push. through the forge, as step 4's push), that commit is a new one on the forge's current base: the reviewer confirms the forge commit's tree equals the reviewed one before posting its verdict on the pull request. +- **Three to five review rounds.** Tell every reviewer which round it is in ("round N of at most 5"): a + reviewer that does not know keeps finding the next smaller thing. From round 3 it asks changes only for a + finding that makes the change wrong, and lists smaller points as follow-ups that do not block. If it + still asks changes at round 5, stop revising and bring the operator the findings with a recommendation: + block, or follow as an issue of its own. The same holds for a decision record's review (issue 784). - **Report every ten minutes, and at once when something lands or needs the operator,** short, as a tree or a table: the issues done (of the total), each issue being fixed with its active time (minutes since its agent was sent, from a start time written down then, never guessed), the issues ready next, the ones waiting, and anything that - needs the operator. Times are local and absolute. + needs the operator, and the allowance used (`anthropic-licence-manager.usage`: the week's and the + session's share). Times are local and absolute. - **When this playbook meets a problem,** the lesson is added here, so the next feature avoids it. ## What this is not