Content
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is actionable and well-structured with concrete commands and a clear change-handling sequence. The main drag is conciseness — illustrative dialog vignettes restate the stance and could be trimmed.
Suggestions
Trim or compress the multi-block ASCII conversation vignettes; one short example conveys the stance without restating it across four scenarios.
Fold 'What You Don't Have To Do' into 'The Stance' to avoid restating the same anti-patterns twice.
Keep concrete commands and the capture table as-is — they are the highest-value content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient guidance, but long ASCII dialog vignettes ('User brings a vague idea', 'The auth system is a mess') and 'What You Don't Have To Do' restate the stance; could be tightened to leaner tokens. | 2 / 3 |
Actionability | Concrete commands (`openspec list --json`, `/opsx:new`, `/opsx:ff`), specific file paths, and an insight→artifact capture table give copy-ready, executable guidance. | 3 / 3 |
Workflow Clarity | Intentionally a stance not a workflow, but the 'When a change exists' branch is explicitly sequenced (steps 1–4) with an offer/don't-auto-capture checkpoint; no destructive ops need validation loops. | 3 / 3 |
Progressive Disclosure | Single self-contained file with no bundle, organized into well-signaled sections separated by `---` and headers; no nested references to penalize. | 3 / 3 |
Total | 11 / 12 Passed |