Playbook 07: say how the agent-definition rule is checked
mesh/delivery closed: a newer head of the same pull request
mesh/check pass 6c395cc20667 on 7021d0cf5ac0 | unit 39 run, 0 kept, 1 skipped | integration 39 run, 0 kept, 1 skipped | composition passed
mesh/delivery closed: a newer head of the same pull request
mesh/check pass 6c395cc20667 on 7021d0cf5ac0 | unit 39 run, 0 kept, 1 skipped | integration 39 run, 0 kept, 1 skipped | composition passed
This commit is contained in:
@@ -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
|
||||
|
||||
|
||||
Reference in New Issue
Block a user