Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a strongly actionable, well-sequenced workflow with concrete commands, JSON field handling, and explicit validation checkpoints throughout. Its main weaknesses are repetitive blocking-point language that bloats token use and the absence of actual bundle reference files, with a large inline split-precheck section that could be externalized.
Suggestions
Consolidate the repeated blocking-point protocol into a single shared callout (e.g., a '## Blocking decision points' section) referenced from 1a/1b/1c/5 instead of restating it verbatim each time.
Move the detailed PRD split-precheck rules (1a) into a reference file under references/ and link to it from the body, reducing inline length and improving progressive disclosure.
Add the actual referenced files (decision-point.md, scripts.md, auto-transition.md) to a references/ bundle so the signaled links resolve to real content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is procedural and avoids explaining concepts Claude already knows, but the blocking-point protocol language ('必须按 comet/reference/decision-point.md 的协议暂停并等待用户...') is restated near-verbatim across 1a/1b/1c/5 and the PRD split-precheck is elaborated at length, so it could be tightened. | 2 / 3 |
Actionability | It gives fully executable commands with exact flags (openspec status/instructions, node "$COMET_STATE" init/check/next, node "$COMET_GUARD" ... --apply), an exact artifact file tree, and field-level JSON handling (dependencies/template/instruction/context/rules/resolvedOutputPath), making it copy-paste ready. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (0→1→1a→1b→1c→2→3→4→5→exit→auto-transition) with explicit validation checkpoints at every blocking point, status refreshes after each artifact, entry-state verification, file-existence checks, idempotency rules, and a guard-based exit gate with feedback loops on failure. | 3 / 3 |
Progressive Disclosure | External paths (comet/reference/decision-point.md, scripts.md, auto-transition.md) are clearly signaled and one level deep, but no bundle files actually exist under references/scripts/assets, and the lengthy inline PRD split-precheck (1a) is content that could be externalized into a reference. | 2 / 3 |
Total | 10 / 12 Passed |