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.
A well-structured overview body: an explicit compile-verify workflow with real safety checkpoints, and clean progressive disclosure into a single detailed reference. The main improvement area is making the body slightly more self-sufficient and tighter — a couple of generic workflow lines and the filler 'Scope' line could be trimmed or replaced with a minimal concrete example.
Suggestions
Trim filler lines such as the 'Scope' sentence and generic workflow steps (e.g., 'Identify requested outcomes, constraints, and the minimum safe set of changes to apply'), which state what Claude would do anyway.
Include one minimal good/bad test snippet (e.g., a MockitoExtension service test vs. an unnecessary @MicronautTest) in the body so the core pattern is actionable without opening the reference.
Name the compile/verify context explicitly in the workflow steps (where to run them relative to applying changes) rather than only in the separate Constraints section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean with no explanations of concepts Claude already knows, but a few lines are filler — "Scope: Apply recommendations based on the reference rules and good/bad code examples" and generic workflow steps like "Identify requested outcomes, constraints, and the minimum safe set of changes to apply" could be trimmed. It is not 5 because those minor padded spots exist, and not 3 because nearly all content earns its place. | 4 / 5 |
Actionability | It gives concrete executable commands ("Run `./mvnw compile` or `mvn compile`", "Run `./mvnw clean verify` or `mvn clean verify`") and points to a real reference file, but the body itself contains no code or test example — the executable detail is delegated entirely to the reference. This sits between level 3 (guidance present but key specifics delegated away) and level 5 (copy-paste ready content), matching 'mostly executable with minor gaps'. | 4 / 5 |
Workflow Clarity | The four-step workflow has explicit validation checkpoints and feedback handling: compile before any change ("If compilation fails, stop immediately"), verify after applying improvements, and stop-and-ask on ambiguous scope or missing tooling. This matches the top anchor of clear sequence with explicit validation and error-recovery behavior. | 5 / 5 |
Progressive Disclosure | The body is a genuine overview: a coverage list, constraints, triggers, and workflow, with all detailed rules and examples in a single one-level-deep, well-signaled reference file (referenced twice, once as a markdown link) that exists and is organized with a table of contents. Navigation is easy and nothing that belongs in a separate file is inlined. | 5 / 5 |
Total | 18 / 20 Passed |