Content
67%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 well-structured, highly specific orchestration document: a clear sequenced workflow with verification checkpoints, concrete tool and resource pointers, and a well-signaled one-level reference system. Its main cost is token efficiency — redundant scheduling/transition sections and guardrails that restate standard database knowledge Claude already has.
Suggestions
Merge the 'Intent signature' and 'When to use' sections and fold the Transitions section into the guardrails to remove duplicated content.
Trim guardrails that restate knowledge Claude already has (e.g. 3NF/ACID definitions, 'measure before optimizing') and keep only the project-specific policy decisions.
Move the 18-item guardrails list or the Deliverables-by-Scope detail into a reference file, keeping a short summary inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly prescriptive rather than educational, but includes unnecessary repetition: the Transitions section restates guardrails 2-4, 'Intent signature' overlaps 'When to use', and several guardrails (3NF/ACID basics, 'measure, explain, then optimize') restate standard DB knowledge Claude already has. Not 4 because the redundancy and known-knowledge restatement is more than minor. | 3 / 5 |
Actionability | Gives mostly concrete, directive guidance: named code-intelligence tools (find_file, search_for_pattern, get_symbols_overview), precise section pointers (resources/anti-patterns.md §5), a concrete expand-contract procedure (additive expand, dual-write + batched backfill, verified read switch, delayed contract), and specific artifact specs. Not 5 because no executable commands or worked examples appear inline — the executable detail is delegated to the referenced resource files. | 4 / 5 |
Workflow Clarity | A clear 10-step canonical workflow with verification steps (run migration/query-plan/retrieval-quality commands, anti-pattern review, checklist sections), explicit exit criteria, and a failure-and-recovery section. Not 5 because the explicit validate -> fix -> re-validate feedback loop for migrations and destructive operations is delegated to checklist.md and error-playbook.md rather than stated inline, leaving a minor checkpoint gap. | 4 / 5 |
Progressive Disclosure | The body works as an overview with a well-annotated, one-level-deep References section where each file is scoped by purpose and condition ('check the sections relevant to the task before handoff', 'matching prior failure'). Not 5 because the 18-item guardrails list and deliverables detail are dense inline content that could be split out, and no bundle files are present to verify the referenced resources/*.md and ../_shared paths actually resolve. | 4 / 5 |
Total | 15 / 20 Passed |