Content
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is action-oriented with strong executable Go examples, but it opens with a redundant restatement of the description, lacks an explicit sequenced workflow with validation checkpoints, and references a DDD-RULES.md file that is missing from the bundle. These keep it in the mid-range rather than top-tier.
Suggestions
Remove the redundant opening sentence that restates the description, or replace it with a token-lean purpose statement that adds new information.
Add a short sequenced design workflow (e.g., define invariant → write validated factory → add actionable methods emitting events → expose via Export → verify invariants) with explicit validation checkpoints.
Provide the missing DDD-RULES.md in the bundle (or inline its essential rules) so the progressive-disclosure reference resolves to a real file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is largely lean and assumes Claude's competence, but the opening line 'Design and implement rich domain aggregates with proper encapsulation, domain events, and the Export pattern' nearly restates the frontmatter description and could be tightened, fitting the 'mostly efficient but could be tightened' anchor rather than the 'every token earns its place' level above. | 2 / 3 |
Actionability | Provides complete, executable Go examples — a validated NewOrder factory, an idempotent Ship method that emits events, and an Export() method — that are specific and copy-paste ready, matching the fully-executable top anchor. | 3 / 3 |
Workflow Clarity | Core Rules are numbered and the examples imply a factory→method→export flow, but there is no explicit sequenced design workflow with validation checkpoints or feedback loops, fitting the 'sequence present but checkpoints missing' anchor rather than the explicit-checkpoint level above. | 2 / 3 |
Progressive Disclosure | Structure is reasonable with a clearly signaled one-level reference ('Read [DDD-RULES.md] for all aggregate design rules'), but no bundle files exist and DDD-RULES.md is absent, so the reference is broken and navigation is incomplete — better than a monolithic wall but not the easy-navigation top anchor. | 2 / 3 |
Total | 9 / 12 Passed |