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 a well-structured, highly actionable archive workflow with executable shell commands, explicit validation gates, and clear sequencing. Its main weakness is repetition of the mechanical-copy and diff -r mandates across multiple sections, and a long monolithic structure that does not offload detail into bundle files.
Suggestions
State the mechanical-copy / diff -r readback mandate once in the Mechanical Copy Contract and have Steps 2-4 and Rules reference it, removing the four restatements to tighten conciseness.
Consider moving the long Final-State Authority hierarchy and gate definitions into a referenced bundle file (e.g. references/archive-gates.md) to reduce the inline length and improve progressive disclosure.
Collapse the duplicated guidance between the Strict-vs-OpenSpec Archive Policy section and the Task Completion Gate, which restate overlapping block conditions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly substantive domain-specific governance rather than concepts Claude already knows, but the diff -r readback mandate and the mechanical-copy prohibition are restated in five places (Mechanical Copy Contract, Step 2, Step 3, Step 4, and Rules), which is more than minor padding; it is not anchor 2 because the content is not explaining known concepts, only repeating its own rules. | 3 / 5 |
Actionability | The openspec/hybrid paths provide fully executable copy-paste shell blocks (mktemp, trap, cp -R, mv/git mv, diff -r readback) and the merge path gives a concrete ADDED/MODIFIED/REMOVED/RENAMED algorithm with matching rules, covering the common cases with placeholder substitution rather than pseudocode. | 5 / 5 |
Workflow Clarity | Steps 1-6 are explicitly sequenced with validation checkpoints (Task Completion Gate STOP/return blocked, mandatory diff -r readback), feedback loops (diff failure FAILS the phase, fix and re-validate), and a Step 4 checklist; because validation is present and thorough the destructive/batch cap at 3 does not apply. | 5 / 5 |
Progressive Disclosure | No bundle files exist and the body is a well-organized single ~313-line file with clear section headers and one-level-deep signaled references to shared project docs ("Follow Section B from skills/_shared/sdd-phase-common.md"); it is not anchor 5 because substantial governance content is inlined rather than split into bundle files and the file is long. | 4 / 5 |
Total | 17 / 20 Passed |