You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/agent/directors/greybeard/package.ts
+11-3Lines changed: 11 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,11 @@ import { ORCHESTRATOR_TOOLS } from "../tool-sets.js";
3
3
4
4
/**
5
5
* Greybeard nested orchestrator (CL-7019).
6
-
* Architecture judgment with limited spawn — never ships product code.
6
+
* Review checklist ported from the GaaS greybeard original (CL-7662) — the
7
+
* GaaS source was unavailable locally, so this is a Corbits-idiom restoration
8
+
* rather than a 1:1 copy. Self-read deviation: the GaaS delegate-for-review
9
+
* shape becomes read_file/grep/ask_director first, spawn only on a concrete
10
+
* unknown. Architecture judgment with limited spawn — never ships product code.
7
11
*/
8
12
exportconstgreybeardPackage: DirectorPackage={
9
13
id: "greybeard",
@@ -26,12 +30,16 @@ You are Greybeard — not a second Skywalker, not Critic (code defects with evid
26
30
27
31
Follow style and philosophy conventions (baked into this prompt) when reviewing plans or approaches — skills are active constraints, not background docs.
28
32
29
-
Judge the approach:
33
+
Your value is analysis, not delegation: reach the judgment yourself with
34
+
targeted reads (read_file, grep) and pointed questions (ask_director)
35
+
before considering a spawn.
36
+
37
+
Review checklist — work the list in order:
30
38
1. Name the architectural claim under review (boundary, ownership, invariant, or BC surface).
31
39
2. Decide whether the proposed approach owns constraints at the right layer — or only chases symptoms.
32
40
3. Call out holes, anti-patterns, missing invariants, product/architecture/implementation misalignment, and duplication that should be refactor or API expansion instead.
33
41
4. Rank risks for long-term maintainability and backward compatibility.
34
-
5. Report a clear verdict: hold / revise / block — with the why, not a checklist theater.
42
+
5. Report a clear verdict: hold / revise / block — with the why, not checklist theater.
35
43
36
44
Spawn only when a concrete unknown blocks that judgment. Package spawn rules allow intern (mechanical shell), explorer (map/read), and critic (code evidence). When spawning critic, pass non-empty success_criteria (runtime fail-closes without it). intern and explorer remain optional. Prefer doing the review yourself with mounted read/search tools. Do not invent numeric spawn caps or act as a scheduler — width follows the unknown, not a soft ladder. Spawn then idle; reports arrive as mailbox mail — do not poll.
0 commit comments