Content
92%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-engineered orchestration skill: fully executable commands, exact file paths, a complete proposal template, and explicit validation checkpoints with retry/skip/abort feedback loops on the risky batch operations. The only weakness is redundancy — the stack-README read instruction, the git-repo confirmation, and stop-on-error handling are each stated two or three times.
Suggestions
State "Read references/stacks/<stack>/README.md first" once (e.g., at the top of Steps) and remove its repeats in step 3 and the Important Rules section.
Drop the duplicate git-repo-exists handling in step 2 — step 1 already requires confirming this and asking the user before proceeding.
Trim per-step restatements of stop-on-error behavior (steps 4 and 5) by relying on the global Validation Rule block, keeping explicit handling only where a concrete recovery loop exists (steps 7 and 10).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is imperative and free of concept over-explanation, but has trimmable repetition: the "read the stack README" instruction appears in step 1, step 3, and again in Important Rules; the git-repo-exists confirmation is duplicated between step 1 and step 2; and stop-on-error handling is stated both in the Validation Rule section and per-step. Not 3 because there is no padding or explanation of things Claude already knows — every section carries operational content. | 4 / 5 |
Actionability | Guidance is copy-paste executable: exact bash commands (git init, openspec init --tools claude,antigravity, openspec new change "<change-name>", openspec status --change --json, git add -A), exact file paths for every read/write, explicit placeholder-replacement mappings, and a complete proposal.md markdown template. Not 4 because the commands and template cover the common cases fully with no gaps requiring improvisation. | 5 / 5 |
Workflow Clarity | Fourteen clearly sequenced steps with explicit validation checkpoints and feedback loops: input validation in step 1, "Verify success: Confirm the openspec/ directory was created. If openspec init fails, report the error output... and stop", and on openspec new change failure "ask the user whether to retry, skip, or abort" — matching the anchor-5 validate→fix→retry pattern for the batch change-creation operation. | 5 / 5 |
Progressive Disclosure | The body is an overview that keeps stack-specific detail in bundle files, referenced by exact one-level-deep paths (references/stacks/<stack>/README.md, openspec-config.yaml, CLAUDE.md, references/common/roadmap-template.md), all of which exist in the bundle, with a closing References section for navigation. Not 4 because there are no organization gaps — every referenced path resolves and nothing that belongs in a reference is inlined. | 5 / 5 |
Total | 19 / 20 Passed |