From 7470927a07a005ef0f73e109b1eb4fc100f75ee7 Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 2 Nov 2026 19:45:17 +0100 Subject: [PATCH] Playbook 07 keeps to feature work: the rule on agent definitions goes to an instruction section for every session (the operator, 2026-11-02) --- 00-META/process/07-feature-branches.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/00-META/process/07-feature-branches.md b/00-META/process/07-feature-branches.md index 785a2bdf..fe15ed7a 100644 --- a/00-META/process/07-feature-branches.md +++ b/00-META/process/07-feature-branches.md @@ -553,14 +553,6 @@ Every agent the mesh runs draws on one weekly allowance shared by every session, spends it many times faster. Up to five agents on the smaller model at once, at most two subagents on the larger one (the lead not counted). -**A role started more than once has a definition.** When a role in the table above, or any other agent a -playbook starts (a reviewer, a watcher, a survey), is started a second time, it is taken from a definition in -the `.claude/agents/` of the repository whose work it serves, named in that repository's AGENTS.md and in the -playbook step that starts it; the lead writes the definition the second time it writes such a prompt, in the -same turn. Only what every session on a node or across the mesh needs is registered through the claude-code -module (the operator, 2026-11-02). hq's words test reads `.claude/`, so a definition uses the glossary's words. Whether a definition exists is the -reviewer's to check: a prompt for a role written by hand a second time, where none was made, is a finding of the review. - ## Following and reporting Most lost time is waiting nobody saw. The lead therefore keeps a **wait list**: everything the feature waits