Content
25%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 a generic template with no projection-specific substance: abstract instructions, no code or concrete steps, no validation workflow, and a dangling reference to a non-existent resources file. It fails to deliver the detailed patterns its own description promises.
Suggestions
Replace the generic Instructions with projection-specific steps: define the event schema, write the projection handler, idempotently apply events, rebuild from a checkpoint, and verify the read model against expected query results.
Add at least one concrete, executable example (e.g. a projection handler snippet or a replay command) so the guidance is actionable rather than abstract.
Create the referenced `resources/implementation-playbook.md` (or fix the path) so the progressive-disclosure reference resolves to a real file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Although short, the body is padded with generic non-informative lines ("Comprehensive guide...", "Clarify goals, constraints, and required inputs", "Apply relevant best practices and validate outcomes") that add no domain value, fitting the noticeably-verbose/padded anchor rather than a lean 4-5. | 2 / 5 |
Actionability | It offers only high-level hints ("Apply relevant best practices", "Provide actionable steps and verification") with no concrete code, commands, or projection-specific steps, matching the minimal-concrete-guidance anchor; not a 1 because it at least gestures at inputs and verification. | 2 / 5 |
Workflow Clarity | The Instructions are generic bullets with no real sequence and only a vague "validate outcomes" nod, with no checkpoints for the batch/rebuild operations projections involve, fitting the rough-sequence-many-gaps/validation-absent anchor. | 2 / 5 |
Progressive Disclosure | The body references `resources/implementation-playbook.md` for detail, but the `resources/` directory does not exist, so the reference is broken; this fits the minimal-structure/broken-references anchor and is not a 1 because there is at least one signaled reference. | 2 / 5 |
Total | 8 / 20 Passed |