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 a compact, well-sectioned overview of risk-management focus areas and a numbered approach, but it leans on generic instruction boilerplate and offers only one concrete formula with no validation checkpoints. Its single external reference is a broken path, undercutting progressive disclosure.
Suggestions
Replace generic Instruction bullets with concrete, executable guidance — e.g. explicit position-sizing formula, a VaR calculation snippet, or a stop-loss placement rule.
Add validation checkpoints to the Approach sequence (e.g. 'Confirm total portfolio risk stays below X% before adding a position') given the financial consequences.
Fix or remove the dangling 'resources/implementation-playbook.md' reference; if a playbook is intended, create it under references/ and link with a clear 'See ... for details' signal.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean, but generic Instructions boilerplate ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices and validate outcomes') adds little Claude doesn't already know; not a 4 because those padded lines could be trimmed, not a 2 because most content earns its place. | 3 / 5 |
Actionability | One concrete detail — the expectancy formula '(Win% × Avg Win) - (Loss% × Avg Loss)' — but most Approach steps are high-level ('Size positions based on account risk percentage') with no executable specifics; matches score-3 (some concrete guidance, incomplete), below 4 for missing key execution details. | 3 / 5 |
Workflow Clarity | A clear numbered 1–7 sequence exists, but there are no validation checkpoints or feedback loops despite stop-loss/position-sizing steps carrying financial risk; matches score-3 (steps listed, checkpoints missing/implicit), below 4 for absent validation. | 3 / 5 |
Progressive Disclosure | Sections are reasonably organized (Use when, Focus Areas, Approach, Output), but the sole external reference 'resources/implementation-playbook.md' points to a non-existent path with no such bundle file present; not a 4 because the only reference is broken, not a 2 because section structure is sound. | 3 / 5 |
Total | 12 / 20 Passed |