Content
56%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 well-organized stance skill with genuinely concrete OpenSpec integration guidance (commands, artifact paths, capture table). Its weaknesses are verbosity from long illustrative dialogues and a progressive-disclosure structure that inlines example-heavy content rather than splitting it out.
Suggestions
Trim the four extended example dialogues to one or two short exemplars, or move them to a references/examples file, cutting the body's length substantially.
Convert the decorative ASCII box in the "Visualize" section into a one-line instruction; it spends ~15 lines saying "use diagrams".
Condense the stance bullets and "What You Don't Have To Do" into fewer, tighter directives since Claude already understands collaborative exploration behavior.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient and does not explain concepts Claude already knows, but at ~270 lines it carries noticeable padding: four extended sample dialogues (~100 lines), a decorative ASCII box that merely says "use ASCII diagrams liberally", and sections like "What You Don't Have To Do" that could be condensed. | 3 / 5 |
Actionability | Concrete guidance exists ("openspec list --json", artifact paths like "openspec/changes/<name>/proposal.md", and the insight-to-artifact capture table), but the core stance sections ("Curious, not prescriptive", "Patient") are abstract direction rather than executable instruction, leaving guidance incomplete for an instruction-only skill. | 3 / 5 |
Workflow Clarity | The capture workflow is clearly sequenced (read artifacts, reference them naturally, offer to capture, user decides) with an explicit context-check entry step and well-defined ending options; it loses a point only because the deliberately non-workflow framing leaves some transitions implicit. | 4 / 5 |
Progressive Disclosure | The single file is well-sectioned with clear headers, but no bundle files exist and ~100 lines of example dialogues are inlined content that, at this total length, would be better placed in a separate examples reference. | 3 / 5 |
Total | 13 / 20 Passed |