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.
An extremely lean, rule-dense body with concrete commands, a clear workflow spine, and strong validation discipline and failure handling. Its main weaknesses are the missing bundle workflow files the body depends on and compression that intermittently trades clarity for brevity.
Suggestions
Ship the referenced workflow files (workflows/dev-implement.md, workflows/dev-fix.md, workflows/long-running-validation.md) in the skill bundle, since the body delegates its core step sequences and validation gate to them.
Move the dense policy material (Engineering Rules, the rebase-map and loaded-file-rebase rules) into a reference file and keep a short rule index in SKILL.md, so the overview stays navigable.
Unpack the most compressed rules (e.g. the rebase-map reply rule and the PREVIOUS_ROUND_COMMIT diff procedure) into short step lists — the token savings are currently offset by re-read cost.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is telegraphic with zero padding and no explanation of concepts Claude already knows ("Before adding a function, parser, stub or loop, grep the repo for the verb it performs"). It falls short of the top anchor because the compression occasionally sacrifices clarity — the "rebase-map:" rule and the loaded-file rebase-diff paragraph each require multiple re-reads to unpack. | 4 / 5 |
Actionability | Concrete commands and file shapes appear throughout ("git diff --no-renames --name-only [PREVIOUS_ROUND_COMMIT] HEAD -- <each loaded file's repo path>", the run-notes path format, and explicit --issue/--kind/--validate/--validate-note semantics). Not fully executable overall because the core workflow steps and the dev-return schema are deferred to referenced files that are not present in this bundle. | 4 / 5 |
Workflow Clarity | Sequences are explicit ("activate → plan → implement → validate → commit → QA labels → summary → artifact → return") with a dedicated validation gate, an investigation-run question/answer protocol with a two-inconclusive limit, and interruption handling ("report an interruption without a verdict as failure"). The full step-by-step workflow itself lives in the absent workflows/dev-implement.md, leaving the body at overview-plus-contract level. | 4 / 5 |
Progressive Disclosure | References are one level deep and clearly signaled with section anchors ([dev-implement.md § 5](workflows/dev-implement.md#5-validate), [../orch/references/skill-rules.md](../orch/references/skill-rules.md)), but the skill's own bundle files (workflows/dev-implement.md, workflows/dev-fix.md, workflows/long-running-validation.md) are missing from the bundle, and dense policy sections (Engineering Rules, Round Contract) are inlined that could live in reference files. | 3 / 5 |
Total | 15 / 20 Passed |