Content
100%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 exemplary orchestration skill: the body is a lean router that sequences five phases with explicit gates, checkpoints, and validation, while deferring executable detail to well-signaled one-level-deep references that all exist in the bundle. Validation for batch/destructive operations (write-then-verify, clean-tree gate) is present, so no workflow-clarity cap applies.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body contains no concept explanations or padding; every sentence is an operational rule (e.g., 'Write order is measure, write, verify', 'A step is done only after it ran'), assuming Claude's competence throughout. | 5 / 5 |
Actionability | Concrete, executable specifics throughout: exact question phrasing for Phase 0, the branch pattern 'optimize/<spec-name>', 'scripts/decide.mjs', the config path '.compound-engineering/config.yaml', 'git rev-parse --show-toplevel', and all seven stop criteria enumerated inline. | 5 / 5 |
Workflow Clarity | Phases 0-4 run in explicit order with checkpoints CP-0 through CP-5 mapped to phases, three named gates (clean-tree, user approval, dependency pre-approval), write-then-verify discipline, an explicit resume-vs-fresh-run distinction, and a defined error path ('If the run instead stopped at a check it could not pass, say what blocked it'). | 5 / 5 |
Progressive Disclosure | A lean overview body in which each phase names exactly the reference it cannot start without ('Read references/spec.md', 'references/loop.md for this phase and Phase 3'); all referenced files exist, instruction content is one level deep, and second-level files are templates/schemas rather than buried instructions. | 5 / 5 |
Total | 20 / 20 Passed |