Content
86%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 an exemplary lean operational procedure: validation-first argument handling, explicit dependency-ordered cancellation steps, concrete state-API commands with JSON examples, and a defined evidence report. The only meaningful gap is the absence of a re-verify/retry loop after cleanup and the vague pointer for `--force` cleanup details.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and imperative with zero padding — e.g. "Reject `--all`, unknown flags, repeated flags, and mixed flags before mutation" and "Clear standalone modes only after proving they are not linked" — explaining nothing Claude already knows and making every token earn its place. | 5 / 5 |
Actionability | Concrete executable commands appear throughout (`omx state list-active --json`, `omx state clear --input '{"mode":...}' --json`, `omx team shutdown <team>`), with minor gaps: the `--force` path delegates to unspecified "documented native-stop cleanup" without naming where that documentation lives. | 4 / 5 |
Workflow Clarity | The sequence is dependency-ordered with explicit validation gates (reject invalid flags before mutation, confirm session/root before cleanup, prove standalone modes are not linked, confirm post-conditions, report rollback failures). It falls short of 5 only because there is no fix-and-retry feedback loop after a failed clear or rollback. | 4 / 5 |
Progressive Disclosure | At ~40 lines with clean, well-organized sections, the body keeps only overview-level content inline and clearly signals its two one-level-deep references (`AGENTS.md#durable-runtime-invariants-canonical-ssot` and `docs/contracts/ralph-cancel-contract.md`); no bundle files exist, so nothing is inlined that belongs elsewhere. | 5 / 5 |
Total | 18 / 20 Passed |