Content
72%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 exemplar of lean, well-structured progressive disclosure with a genuine one-level reference, and the instruction sequence is coherent. Its weaknesses are mid-level actionability and missing validation checkpoints: steps tell what to produce but not how concretely, and nothing instructs Claude to verify the resulting map (e.g., every pair has an owner and a failure mode).
Suggestions
Add an explicit validation step, e.g. '5. Verify every context pair has a named contract owner, a chosen pattern, and a documented failure mode before presenting the map.'
Inline a small example of the output (a 2-3 row relationship map or one ACL decision) so the abstract steps like 'Define translation rules' become concrete.
Name the specific relationship patterns to consider in the body (or point to the reference's pattern list at the choose-patterns step) so step 2 is executable without prior recall.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~40-line body is lean and assumes Claude's DDD knowledge: no background concepts, no padded sections, and each section (use/do-not-use, instructions, outputs, limitations) earns its tokens. | 5 / 5 |
Actionability | Numbered steps ('List all context pairs and dependency direction', 'Choose relationship patterns per pair') plus a real reference with a mapping template and ACL checklist give some concrete guidance, but steps like 'Define translation rules and ownership boundaries' remain high-level with no inline example of the decisions or output format, so it is incomplete rather than mostly executable. | 3 / 5 |
Workflow Clarity | A coherent four-step sequence is present, but there are no validation checkpoints (e.g., reviewing the finished map for coupling risks or verifying each contract has an owner), matching the 'sequence present but checkpoints missing' anchor rather than the level-4 anchor. | 3 / 5 |
Progressive Disclosure | The body is under 50 lines, well-sectioned, and its only reference ('If detailed mapping structures are needed, open references/context-map-patterns.md') is clearly signaled, one level deep, exists on disk, and correctly holds the detail (pattern catalog, mapping template, ACL checklist). | 5 / 5 |
Total | 16 / 20 Passed |