Content
71%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 delivers concrete, well-sequenced instructional guidance with strong approval gates and little wasted explanation. Its main defect is that both referenced format files are missing from the bundle, breaking navigation and leaving the CONTEXT.md and ADR formats unspecified.
Suggestions
Create the referenced CONTEXT-FORMAT.md and ADR-FORMAT.md bundle files (or inline compact format templates), since both links currently point to files that do not exist.
Consolidate the Project Thread guidance, which currently appears in both <what-to-do> and <supporting-info>, into one section to remove redundancy.
Trim the second ASCII directory tree (the multi-context example) to a one-line description of the CONTEXT-MAP.md convention to tighten token use.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence, consisting almost entirely of project-specific non-obvious guidance (CONTEXT-MAP.md convention, #brain-joel Project Threads, the ADR three-condition gate). Minor padding exists in the two ASCII directory trees and the Project Thread guidance duplicated between <what-to-do> and <supporting-info>, fitting anchor 4 rather than 5. | 4 / 5 |
Actionability | Guidance is highly concrete for an instruction-only skill: verbatim question scripts ("Your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?"), an exact approval prompt to quote, and the three-condition ADR test. It falls short of anchor 5 because the CONTEXT.md and ADR formats are delegated to referenced files that are absent, leaving an executable gap. | 4 / 5 |
Workflow Clarity | A clear sequence is present — interview one question at a time, explore the codebase where a question is answerable there, grill for long-form rationale, update CONTEXT.md inline, gate ADRs on the three conditions, and ask operator approval before creating a Project Thread — with explicit approval checkpoints. Not anchor 5 because the ordering across the <what-to-do>/<supporting-info> split must be inferred by the reader. | 4 / 5 |
Progressive Disclosure | The body itself is well organized into clear sections, but both referenced format files — [CONTEXT-FORMAT.md](./CONTEXT-FORMAT.md) and [ADR-FORMAT.md](./ADR-FORMAT.md) — do not exist in the bundle, so the promised one-level-deep navigation is broken at runtime. This lands at anchor 3: decent structure but references that fail to resolve. | 3 / 5 |
Total | 15 / 20 Passed |