Content
50%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 cleanly sectioned into use/avoid/context/instructions/safety/output, but it duplicates the frontmatter description, offers only high-level refactor guidance, and points to a playbook file that is not present in the bundle. Validation is mentioned but lacks an explicit feedback-loop checkpoint.
Suggestions
Remove the verbatim repetition of the frontmatter description from the body's opening paragraph and tighten the 'Context' section to eliminate redundancy.
Name concrete refactor techniques (e.g. extract method, inline variable, extract class) or link to a working example so the guidance is actionable rather than directional.
Make the validation step an explicit checkpoint with a feedback loop ('run tests; if any fail, fix and re-run until green before proceeding') and either provide resources/implementation-playbook.md or remove the broken reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient and section-organized, but repeats the frontmatter description verbatim as the opening paragraph and includes a padded 'Context' restating the same intent, fitting anchor 3. | 3 / 5 |
Actionability | Instructions give directional steps ('Identify high-impact refactor candidates', 'Break work into small, testable steps', 'Validate with tests') but name no concrete refactor patterns or examples, leaving guidance incomplete per anchor 3. | 3 / 5 |
Workflow Clarity | A rough sequence exists (identify -> break down -> apply -> validate) and a validation step is present, but there is no explicit checkpoint or feedback loop (validate -> fix -> re-validate), matching anchor 3. | 3 / 5 |
Progressive Disclosure | Sections are reasonably organized and a one-level reference is signaled in the Resources section, but the referenced path 'resources/implementation-playbook.md' does not exist in the bundle (no references/scripts/assets dirs) and uses a non-standard folder name, creating a navigation defect per anchor 3. | 3 / 5 |
Total | 12 / 20 Passed |