Content
77%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-engineered orchestrator document: tightly written, with a gated and ordered execution contract, concrete copy-paste commands, failure branches, and a completion checklist. The main defects are instructional sections that assume a bundle larger than what actually ships (missing routing config, tool-index, ops and journal files) and a few trimmable meta sections.
Suggestions
Ship or generate the files the contract hard-depends on (config/routing.json, tool-index.md) in the bundle, or state explicitly that case-init/bootstrap create them on first run, so the first NOW step is executable as bundled.
Remove the RFC 2119 semantics section and condense the "目录是动态扩充的" / "自动进化" housekeeping into one short pointer, cutting tokens that do not instruct the current task.
Verify every referenced path (ops/*.md, RULES.md, CONTRIBUTING.md, field-journal/) exists in the published bundle, or mark them as created-on-demand so navigation does not dead-end.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and telegraphic — the routing contract, module table, and bootstrap commands earn their tokens — but a few sections could be trimmed: the RFC 2119 MUST/SHOULD/MAY semantics Claude already knows, and meta-commentary sections like "目录是动态扩充的" and "自动进化" that describe repository housekeeping rather than instructing the task. | 4 / 5 |
Actionability | Concrete, copy-paste-ready commands are given for the core path (master-route.ps1/.sh, case-init, bootstrap-reverse with full command lines and placeholders) plus a concrete next-step menu example. The gap: the very first NOW step depends on config/routing.json and downstream steps on tool-index.md, neither of which exists in the provided bundle, so the primary instructions are not fully executable as bundled. | 4 / 5 |
Workflow Clarity | The CRITICAL contract gives a strictly ordered NOW/NOW/ACT/NEXT sequence with a hard authorization gate ("auth 未 granted 禁止对目标 ACT"), explicit error-recovery branches (routing miss → research and propose a new skill, never force-fit; missing tool → bootstrap), a read-order table for precedent files, and a terminal self-check checklist — matching the anchor for clear sequence with explicit validation, feedback loops, and checklists. | 5 / 5 |
Progressive Disclosure | References are clearly signaled with their purpose and stay one level deep (scripts, references/*.md, ops/*, field-journal/*), and the 40-row module table is appropriately inline for a router index. However, scored against the actual bundle, 7 of 16 referenced paths are absent (config/routing.json, routing.md, tool-index.md, ops/IDENTITY.md, RULES.md, CONTRIBUTING.md, field-journal/), so a reader following the contract immediately hits broken navigation — more than a minor organization gap. | 3 / 5 |
Total | 16 / 20 Passed |