Content
81%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 highly actionable — concrete git commands, a complete copy-paste subagent prompt, and an explicit verdict-to-action table with real validation checkpoints — and the workflow is clearly sequenced. Its main weakness is token efficiency: the anti-bloat rules appear twice and several passages over-explain git behavior Claude already knows.
Suggestions
State the anti-bloat rules once — inside the subagent prompt's 'Anti-Bloat & Proportionality' checklist — and reduce the outer 'Anti-Pattern' section to a two-line pointer to it, cutting roughly 30 duplicated lines.
Trim the git mechanics explanations (three-dot merge-base semantics, `git add -N` intent-to-add behavior, `.gitignore` interaction) to one-line tips; Claude already knows git and only needs the repo's conventions.
Consider moving the VeOmni test-workflow ownership details (which workflow runs which `tests/` paths, file-by-file listing rules) into a reference file under a `references/` directory and linking it from the checklist, shortening the subagent prompt.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Quotes: "Use three dots: it diffs from the merge base, so commits that landed on `<base>` after you branched do not show up as your changes" and "`git add -N` is what makes a brand-new module or test visible at all, and it respects `.gitignore`" tutor git mechanics Claude already knows, and the anti-bloat rules are stated twice — once in the body's "Anti-Pattern" section and again nearly verbatim in the subagent prompt's "Anti-Bloat & Proportionality" checklist. Not 4 because the duplication and git tutoring are more than minor trim instances; not 2 because nearly all content is repo-specific, non-obvious knowledge rather than generic padding. | 3 / 5 |
Actionability | Quotes: "git diff <base>...HEAD", "git add -N .", "Run `make quality` before pushing", plus a complete copy-paste subagent prompt and a verdict-to-action table ("risky | Output the report, do NOT open the PR, wait for the user"). Fully executable guidance covering the common cases; no gaps. | 5 / 5 |
Workflow Clarity | Numbered steps 1-5 in clear sequence with explicit validation checkpoints and feedback loops: "Address the listed issues, then open or update the PR", "do NOT open the PR, wait for the user", and the pre-push "Run `make quality`" gate. Not 4 because validation and escalation are explicit decision points, not implied. | 5 / 5 |
Progressive Disclosure | Well-organized sections with one-level-deep, clearly signaled references ("Read `.agents/knowledge/constraints.md`", "See `.agents/knowledge/testing.md`", "The full requirements are in 'Documenting an extension point' in `.agents/skills/veomni-develop/SKILL.md`"); no bundle files exist to verify. Not 5 because the ~60-line Anti-Pattern section duplicates rules already embedded in the subagent prompt — content that could be consolidated or split into a reference file; not 3 because the references that do exist are clearly signaled and navigation is easy. | 4 / 5 |
Total | 17 / 20 Passed |