Content
77%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 rigorous, actionable batch workflow with outstanding validation and error-recovery checkpoints for a destructive multi-change operation. The costs are token weight: a large redundant guardrails section and a monolithic single-file layout that inlines material better suited to reference files.
Suggestions
Trim the Guardrails section to only rules not already stated in the steps (roughly a third of its bullets duplicate step 3d, 7, and 8 text on dates, target collisions, and excluded deltas), cutting significant tokens without losing information.
Move the Conflict Resolution Examples and the store-selection/project-check boilerplate into a references/ file (e.g., references/conflict-examples.md) referenced from the relevant steps, so SKILL.md stays a lean overview.
Condense the multi-paragraph advisory treatment of `context` and `operationGuidance` (steps 2 and 8a) into a short rule list, since the same separation-of-concerns rules are repeated nearly verbatim in both places.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense operational contract rather than concept explanation, but the ~25-bullet Guardrails section restates rules already spelled out in steps 3d, 7, and 8 (date computation, target-collision checks, excluded-delta reporting), and the advisory-instructions paragraphs could be tightened. This is 'mostly efficient but could be tightened' rather than the minor-trimming of a 4. | 3 / 5 |
Actionability | Fully executable guidance throughout: exact commands with JSON flags (`openspec list --json`, `openspec status --change "<name>" --json`), specific JSON fields to parse, copy-ready bash (`mkdir -p` / `mv`), and worked conflict-resolution examples covering the common cases. | 5 / 5 |
Workflow Clarity | Steps 1-9 are clearly sequenced with explicit validation checkpoints for this batch/destructive operation: pre-write target-collision checks, atomic specs-rule fetch before the first write, verify-main-specs-before-move, re-check plus mv-nest detection immediately before the move, and per-change outcome tracking with error recovery. The batch-operation validation cap does not apply because feedback loops are present. | 5 / 5 |
Progressive Disclosure | No bundle files exist; the 377-line body is a single well-sectioned monolith. Content that would naturally live one level deep (conflict-resolution examples, the store-selection and project-check boilerplate) is inlined in SKILL.md, matching the anchor for some structure but content that should be separate kept inline. | 3 / 5 |
Total | 16 / 20 Passed |