Playbook 07 keeps to feature work: the rule on agent definitions goes to an instruction section for every session (the operator, 2026-11-02)

2026-11-02 19:45:17 +01:00
parent 6c395cc206
commit 7470927a07
1 changed files with 0 additions and 8 deletions
@@ -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