From 6c395cc206674d44ee4d836362e6bbd86a2c7e2c Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 2 Nov 2026 19:42:08 +0100 Subject: [PATCH] Playbook 07: say how the agent-definition rule is checked --- 00-META/process/07-feature-branches.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/00-META/process/07-feature-branches.md b/00-META/process/07-feature-branches.md index b4f9f972..785a2bdf 100644 --- a/00-META/process/07-feature-branches.md +++ b/00-META/process/07-feature-branches.md @@ -558,7 +558,8 @@ playbook starts (a reviewer, a watcher, a survey), is started a second time, it 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. +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