Content
85%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.
An exceptionally actionable, well-sequenced multi-phase workflow: every branch has concrete commands, exact strings and explicit validation gates, with genuine error-recovery loops. Its main costs are length — the minimal-tier rules and '## Your systems' ordering are each specified twice — and heavy inlining of detail (field tables, output templates, error messages) that could live in reference files like the existing qa-lead-gate.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense, telegraphic and almost entirely project-specific operational detail Claude could not infer, with no padding about known concepts — but at ~378 lines it repeats itself in places, e.g. the '## Your systems' three-step ordering is specified in full in Phase 2 and again in Phase 6's minimal summary, fitting anchor 4 rather than the every-token-earns-its-place bar of 5. | 4 / 5 |
Actionability | Guidance is fully executable throughout: exact commands (md-section.sh extract, adr-status.sh with ADR-NNNN args), exact file paths, exact message strings to utter on each failure branch, and a field-value table for the minimal tier — matching anchor 5's copy-paste-ready bar for an instruction-only skill. | 5 / 5 |
Workflow Clarity | Eight explicitly numbered phases with a copy-and-tick checklist, validation checkpoints (report before drafting, QA gate before the ask, "Write nothing before the yes"), feedback loops for error recovery (missing ADR/EPIC/brief branches, dismissed question → ask again in plain text, declined write → BLOCKED verdict), and a terminal verdict block — a clear anchor 5 match with the destructive/batch cap not applying since write validation is present. | 5 / 5 |
Progressive Disclosure | The one bundle reference (references/qa-lead-gate.md) is real, clearly signaled and one level deep, but the main body inlines substantial content that belongs in separate reference files — the entire minimal-tier spec with its field table, the Phase 6 output templates, and the exact error messages — fitting anchor 3's 'content that should be separate is inline' rather than anchor 4's 'most content is appropriately placed'. | 3 / 5 |
Total | 17 / 20 Passed |