Content
90%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, repo-specific workflow: phased design-to-finalize structure, executable registration code, concrete test commands, and explicit pitfalls. Weakest points are the absence of an explicit error-recovery loop after validation failures and inline policy detail that could live in a reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~165-line body is dense and entirely repo-specific (registry identity tuple, patchgen rules, NPU eager restrictions, cache rules) with zero explanation of concepts Claude already knows; every section carries project constraints, matching the lean/efficient anchor. | 5 / 5 |
Actionability | It provides a copy-paste-ready register_op example covering both the wrapper and raw-pair forms, an exact test command (pytest -q tests/ops/<kernel_name>/ tests/ops/base/), and concrete verification commands (OP_REGISTRY.list_registered(...)), with the forward/backward contract precisely specified; specific examples cover the common cases. | 5 / 5 |
Workflow Clarity | Five clearly sequenced phases plus a 'Before You Start' section and validation checkpoints (per-input backward parity tests, /veomni-review, make quality, registry verification) give a clear sequence; however, no explicit fix-and-rerun feedback loop after validation failures keeps it below the anchor-5 example. | 4 / 5 |
Progressive Disclosure | Sections are well-organized with clearly signaled one-level-deep references to repo docs (veomni/ops/README.md, docs/design/op_selection.md, docs/design/module_config.md, the new-model coverage policy link) and no bundle files exist; dense policy sections like 'Configuration ownership' are inlined where a reference-file split would help, fitting the minor-organization-gaps anchor. | 4 / 5 |
Total | 18 / 20 Passed |