Content
60%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 delivers genuinely actionable, well-sequenced change-management guidance with useful diagnostic tables and checklists. Its main weaknesses are a redundant Keywords section, some conceptual padding, and a broken/missing references/change-playbook.md that both removes promised content and duplicates material inline that should live there.
Suggestions
Create references/change-playbook.md (or remove the broken pointer) so the promised communication templates, resistance counter-strategies, and fatigue detail are actually reachable, and trim the inline ADKAR/resistance/fatigue detail that the reference is meant to hold.
Delete the '## Keywords' section — it restates description trigger terms verbatim and consumes token budget without adding guidance.
Add an explicit recovery loop for failed checkpoints (e.g., 'If week-2 adoption is below X, run 1:1 diagnosis using the resistance table and adjust the next communication'), which would raise workflow clarity to fully validated.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient and opinionated, but the '## Keywords' section duplicates trigger terms already in the description and adds no guidance value, and background lines like 'ADKAR is a change management model by Prosci. Original version is for enterprises' explain context Claude already knows; the body could be tightened without losing substance. | 3 / 5 |
Actionability | Concrete, executable guidance throughout: week-by-week communication sequences ('Week -2: Announce the why + go-live date', 'Week 8: Old system deprecated'), a resistance-quote-to-response diagnostic table, and specific scripts ('Run a concerns and questions session within 48 hours'). It falls short of fully copy-paste-ready because the communication templates promised in the description are only deferred to the reference file. | 4 / 5 |
Workflow Clarity | Each change type has a clearly numbered sequence with explicit checkpoints ('Week 2: Adoption check-in (who is using it? Who isn't?)', 'Month 2: First retrospective') plus 'Key Questions' and 'Red Flags' checklists. Not a 5 because there is no explicit error-recovery loop spelling out what to do when an adoption check-in or retrospective reveals the change is failing. | 4 / 5 |
Progressive Disclosure | The body inlines substantial deep-dive material (full ADKAR expansion, resistance strategies, fatigue management) that the 'Detailed References' entry says belongs in references/change-playbook.md, and that referenced file does not exist in the bundle — the sole navigation pointer is broken, so the promised templates and counter-strategies are unreachable. | 2 / 5 |
Total | 13 / 20 Passed |