Content
53%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 admirably concise and free of padding, but it stays at the level of abstract direction: no executable code, commands, or library names, no validation checkpoints, and its only reference points to a non-existent `resources/` path. It reads as a skeleton rather than actionable guidance.
Suggestions
Add concrete, executable guidance — name tools (e.g. Playwright/Cypress), include a minimal runnable test snippet, and specify commands for running in CI.
Insert validation/feedback checkpoints into the workflow (e.g. after building selectors, verify the test runs green locally before parallelizing in CI) to lift workflow clarity above the destructive/batch cap of 3.
Fix the dangling reference: either create `resources/implementation-playbook.md` with the promised patterns/templates and link it correctly, or remove the broken pointer.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~36-line body is lean and assumes Claude's competence: "Identify critical user journeys and success criteria", "Build stable selectors and test data strategies" — no padding, no explaining what a test framework is, every line earns its place. | 5 / 5 |
Actionability | Instructions are high-level hints ("Implement tests with retries, tracing, and isolation", "Run in CI with parallelization and artifact capture") with no concrete code, commands, library names, or copy-paste examples — minimal concrete guidance, missing the specific steps to execute. | 2 / 5 |
Workflow Clarity | The four numbered steps give a rough sequence (identify → build → implement → run in CI) but there are no validation checkpoints or feedback loops, and destructive/CI batch operations lack the validate-then-proceed guidance the rubric requires — capping workflow clarity at 3. | 3 / 5 |
Progressive Disclosure | Structure is minimal: the single reference `resources/implementation-playbook.md` is mentioned but the `resources/` directory does not exist in the bundle, the path is not a working link, and detailed patterns/templates that clearly belong in a referenced file are instead absent entirely. | 2 / 5 |
Total | 12 / 20 Passed |