Content
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A tight, highly actionable body that combines concrete file paths and test commands with a well-sequenced cross-surface checklist and clearly signaled doc references, with no wasted tokens or concept padding.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence — it never explains what Stalker/Ministra is, and every line (file paths, flag modes, field names, test commands) earns its place, matching the lean-and-efficient anchor. | 3 / 3 |
Actionability | It gives fully concrete, executable guidance — exact paths like `libs/portal/stalker/feature/src/lib/`, commands like `pnpm nx test portal-stalker-feature`, flag values `true`/`1`/`'1'`, and named functions such as `extractStalkerItemType()`. | 3 / 3 |
Workflow Clarity | The numbered `is_series` Cross-Surface Checklist sequences every downstream surface with explicit checkpoints ('Do not stop after making the detail view render', 'must not infer episode numbers'), and Regression Coverage provides concrete verification commands per surface. | 3 / 3 |
Progressive Disclosure | Content is organized into clearly signaled sections (Read First, Ownership, checklist, Regression Coverage) with one-level-deep references to repo docs annotated by purpose ('for ITV EPG work', 'for live remote-control work') and no nested indirection. | 3 / 3 |
Total | 12 / 12 Passed |