Content
85%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.
The body is a tightly written orchestrator for a complex four-phase workflow: it sequences phases with hard gates and explicit validation checkpoints while delegating executable detail to well-signaled, real reference files, and every bundle file is reachable with its purpose stated where it is needed. The only notable improvement is trimming a few redundant discipline statements.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and purely instructional with no padding about concepts Claude already knows, but a few passages could be trimmed — "A step is done only after it ran. Describing a measurement, dispatch, or checkpoint is not doing it." restates the 'Done when' discipline, and the Execution Surface paragraph packs three definitions into one block — matching anchor 4 rather than the fully lean anchor 5. | 4 / 5 |
Actionability | Concrete specifics appear directly (`git rev-parse --show-toplevel`, `<repo-root>/.compound-engineering/config.yaml`, `.context/compound-engineering/ce-optimize/<spec-name>/`, the `optimize/<spec-name>` branch, and gates like "Do not enter Phase 2 until the user explicitly approves"), but most executable detail (tick protocol, script invocations) is delegated to references, leaving minor gaps in the body itself — anchor 4, not 5's copy-paste-ready coverage. | 4 / 5 |
Workflow Clarity | Four phases run in explicit order, each naming the reference it "cannot start without", with hard gates (clean-tree, user approval, dependency pre-approval), eight enumerated stopping criteria, checkpoints CP-0 through CP-5, a measure-write-verify write order, an explicit error path ("If the run instead stopped at a check it could not pass, say what blocked it"), and a defined resume protocol — full validation and feedback loops per anchor 5. | 5 / 5 |
Progressive Disclosure | The body is a clear overview whose five phase references (persistence.md, spec.md, measurement.md, loop.md, wrap-up.md) all exist as real files and are boldly signaled ("**Read `references/loop.md`**") with stated purpose and phase binding; the remaining bundle files (schemas, example specs, templates, agents, scripts) are each cited with purpose at point of use one level deeper, with no chains that bury content — matching anchor 5. | 5 / 5 |
Total | 18 / 20 Passed |