Content
70%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 delivers a rigorous, well-validated workflow with copy-paste commands and strong error-recovery semantics appropriate to a destructive archive operation. Its main costs are token weight from repeated guardrail restatements and a monolithic structure that keeps reference-worthy material inline.
Suggestions
Remove the Guardrails lines that restate step-1 contracts verbatim (e.g., the 'never copy runtime context/guidance/rule text verbatim' rules) and keep only the genuinely additive guardrails, cutting redundant tokens.
Move the step-4 sync verification contract (title/purpose/heading rules and the post-sync comparison criteria) into a references/ file (e.g., references/sync-contract.md) and link to it from step 4, slimming the main body.
Condense the store-selection and root-null branching prose into a compact decision table or short bulleted contract to reduce the dense multi-clause paragraphs.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is domain-specific rather than explaining known concepts, but the Guardrails section restates rules already detailed in step 1 (e.g., 'Never copy runtime context, operation guidance, or artifact-rule text verbatim into output files'), and the store-selection and root-null paragraphs are dense prose that could be tightened. | 3 / 5 |
Actionability | Provides concrete executable commands with placeholders ('openspec status --change "<name>" --json', 'mkdir -p', 'mv') and specific JSON fields to parse, but the sync execution is delegated to the 'openspec-sync-specs workflow' and some comparisons are described only at prose level. | 4 / 5 |
Workflow Clarity | Six clearly sequenced steps with extensive validation checkpoints (artifact/task status checks, sync-blocked detection, post-sync verification re-run across every capability) and explicit feedback loops with recovery paths ('Nothing has moved and changeRoot is intact, so the user can fix the mismatch'), plus a guardrails checklist for a destructive move operation. | 5 / 5 |
Progressive Disclosure | No bundle files exist and the ~220-line body inlines content that plausibly belongs in reference files (store-selection rules, root-null branching, the step-4 sync verification contract), though internal section structure with numbered steps and headers is solid. | 3 / 5 |
Total | 15 / 20 Passed |