Content
68%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.
A strongly actionable, well-structured instruction skill with exact commands, paths, and decision rules for applying delta specs. The principal gap is the absence of validation or verification in a destructive batch workflow — there is no step to confirm merged specs are correct before reporting the summary. Minor redundancy and an inlined format reference keep conciseness and progressive disclosure at 4.
Suggestions
Add an explicit validation step after merging and before the summary, e.g. re-read each updated main spec to confirm requirement names match the delta intent and no unmentioned content was lost or duplicated.
Add an error-recovery loop for failure cases, such as a FROM requirement in a RENAMED block that cannot be found in the main spec — specify whether to ask the user, skip with a warning, or abort.
Consolidate the duplicated intelligent-merging guidance from step 3c and the "Key Principle" section into one place, and consider moving the delta spec format reference into a one-level-deep reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence — no concept explanations, just procedure, paths, and a format reference. It falls short of anchor 5 due to minor redundancy: the intelligent-merging guidance ("don't need to copy existing ones" in step 3c vs. "just include that scenario under MODIFIED - don't copy existing scenarios" in the Key Principle section) is stated twice, and the format reference block is slightly long. | 4 / 5 |
Actionability | Concrete, executable guidance throughout: the exact command `openspec list --json`, exact paths (`openspec/changes/<name>/specs/<capability>/spec.md`, `openspec/specs/<capability>/spec.md`), per-section decision rules, and a worked format example. It stops short of anchor 5 because the core merge operation relies on open-ended judgment ("Use your judgment to merge changes sensibly") and step 1 leaves filtering of changes-with-delta-specs implicit rather than specified. | 4 / 5 |
Workflow Clarity | Steps 1-4 are clearly sequenced with good pre-flight guardrails ("Read both delta and main specs before making changes", "Preserve existing content not mentioned in delta"), but the workflow involves destructive and batch edits (REMOVED requirements, edits across multiple main spec files) with no post-operation validation or verification step. Per the rubric's cap, a destructive/batch workflow without validation cannot score above 3. | 3 / 5 |
Progressive Disclosure | Well-organized single-file structure with clearly labeled sections (Steps, Delta Spec Format Reference, Key Principle, Output On Success, Guardrails) and no external references — appropriate for a self-contained skill. It misses anchor 5 because the ~127-line body exceeds the under-50-line simple-skill exception and content like the 25-line format reference could live in a one-level-deep reference file. | 4 / 5 |
Total | 15 / 20 Passed |