Content
88%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.
A highly actionable, well-sequenced instruction skill with concrete commands, exact templates, and a real verification checklist. The only improvements are trimming a few narrative asides and splitting the specialized oracle-mode guidance into a separate reference file. Both judges scored identically strong.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and prescriptive with essentially no explanation of concepts Claude already knows, and project-specific conventions (ID scheme, EARS table, modes A/B) earn their tokens. A few narrative passages — the '~118 merge sites' anecdote and the aside about agents letting specs and tests diverge — could be trimmed, matching the efficient-with-minor-trimming anchor rather than the every-token-earns-its-place anchor. | 4 / 5 |
Actionability | Guidance is fully concrete and executable: copy-paste commands ('ls specs/ | cut -d- -f2 | sort -u', "rg 'REQ-<ID>' --type rust specs/ src/ tests/"), an exact FDD naming template with worked examples, a complete EARS pattern table, and explicit file-naming rules. Specific examples cover the common cases, matching the top anchor for an instruction-only skill. | 5 / 5 |
Workflow Clarity | The authoring flow is clearly sequenced (numbered sections 1–6) with an explicit 'Done means' checklist, a concrete ID-collision verification command, a human-review checkpoint before implementation, and recovery rules ('If the change invalidates an anchor scenario, rewrite it — do not delete it without replacement'). Section 6 gives a clean 4-step sequence for modifying existing requirements. This matches the anchor for explicit validation steps and checklists. | 5 / 5 |
Progressive Disclosure | The body is well-sectioned with clear headers and one-level references to project artifacts (templates/requirement.md) and sibling skills (golden-parity, verification-ratchet), with no nested reference chains. However, at ~167 lines with no bundle files, the sizable oracle-mode section (4a) is specialized port/rewrite guidance that could live in its own reference file — good structure with a minor organization gap rather than an ideal split. | 4 / 5 |
Total | 18 / 20 Passed |