Content
65%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, actionable stance document grounded in real OpenSpec commands and artifact paths. Its main weaknesses are repetition across the stance/guardrail sections and the absence of any validation/checkpoint flow, which is partly inherent to a non-procedural stance skill.
Suggestions
Consolidate the overlapping 'The Stance', 'What You Don't Have To Do', and 'Guardrails' sections into a single concise list to remove repeated don't-implement/don't-rush themes and trim tokens.
In the 'When a change exists' sub-flow, add an explicit checkpoint such as confirming the change name via `openspec list --json` before reading artifacts, so the one concrete sequence has a clear validation step.
Tighten the illustrative ASCII diagrams to the one or two most representative cases rather than four full dialogue examples, preserving clarity while reducing length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~170-line body is mostly efficient and avoids explaining concepts Claude already knows, but the Stance, 'What You Don't Have To Do', and Guardrails sections repeat the same don't-implement/don't-rush themes, so it could be tightened beyond minor trimming. | 3 / 5 |
Actionability | Provides genuinely executable guidance such as `openspec list --json`, concrete artifact paths (proposal.md, design.md, tasks.md), and a capture-location table, plus illustrative dialogue flows; minor gaps remain since much is stance/attitude direction rather than copy-paste runnable steps. | 4 / 5 |
Workflow Clarity | The skill is intentionally 'a stance, not a workflow' with no fixed steps; the most concrete sub-sequence (when a change exists) lists steps but has no validation checkpoints, matching the anchor for steps present with checkpoints missing. | 3 / 5 |
Progressive Disclosure | No bundle files exist and none are needed; the single self-contained document is well-organized with clear section headers and easy navigation, satisfying the simple-skill exception for a clean, reference-free stance skill. | 5 / 5 |
Total | 15 / 20 Passed |