Content
48%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 strong, executable migration runbook with a clearly sequenced multi-step workflow and explicit validation checkpoints. The chief gap is that everything lives in one ~150-line file with no reference split for deeper material.
Suggestions
Move the detailed zero-downtime patterns (Patterns A–C) and the Emergency Safety Checklist into a referenced reference file to improve progressive disclosure.
Trim framing prose such as 'non-negotiable' statements to tighten conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is largely efficient — commands, code, and checklists carry the guidance — with only minor explanatory prose like 'non-negotiable' framing that could be trimmed, matching the efficient-but-slightly-padded score-4 anchor. | 4 / 5 |
Actionability | It provides fully executable, copy-paste-ready commands (dotnet ef migrations add/script/bundle/database update) with real flags plus concrete EF builder code, SQL verification, and a pg_index diagnostic query covering the common cases. | 5 / 5 |
Workflow Clarity | Steps 1–5 are clearly sequenced with explicit validation checkpoints (SQL Safety Inspection Checklist, Emergency Safety Checklist) and feedback loops ('If lock_timeout expires... do NOT force locks'), so the destructive-operation cap does not apply. | 5 / 5 |
Progressive Disclosure | The single file is well-organized with clearly numbered section headers, but at ~150 lines with all content inline and no separate reference files, it has minor organization gaps versus the one-level-deep-reference ideal. | 4 / 5 |
Total | 18 / 20 Passed |