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.
A highly actionable, well-sequenced workflow with strong validation checkpoints and feedback loops. Its weaknesses are redundancy — guardrails restate inline step guidance, and the context/operationGuidance rules appear twice — and a single-file structure that inlines niche edge-case handling.
Suggestions
Deduplicate the Guardrails section against the inline step guidance: the pause conditions, sourcePath/line rule, and context/operationGuidance contract are each stated twice.
Move the store-selection and root-null edge-case handling into a reference file (e.g., references/stores.md) and keep a one-line pointer in SKILL.md to slim the body.
Replace the three repeated "suggest review or verification as appropriate before archiving" phrasings with a single defined completion step referenced from each output template.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Most tokens carry CLI-specific semantics Claude cannot know (store stickiness, root: null handling, blocked states), but the context/operationGuidance contract is stated twice (step 3 and Guardrails), "suggest review or verification as appropriate before archiving" appears three times, and the "Pause if" list duplicates the Guardrails section — it could be tightened. | 3 / 5 |
Actionability | Fully executable throughout: copy-paste commands with flags (openspec status --change "<name>" --json), named JSON fields to parse, the exact checkbox edit (- [ ] to - [x]), and concrete output templates for completion and pause. | 5 / 5 |
Workflow Clarity | A clear 7-step sequence with explicit state handling (blocked/all_done), validation feedback loops (rerun instructions after each task, confirm progress changed, refresh sourcePath/line before editing), defined pause conditions, and a guardrail checklist. | 5 / 5 |
Progressive Disclosure | The single file is well-organized with clear sections and headers, and the core workflow belongs inline, but at ~195 lines the dense store-selection and root-null edge-case prose is inline detail that would fit a reference file, leaving minor organization gaps. | 4 / 5 |
Total | 17 / 20 Passed |