Content
77%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 content is an exceptionally actionable and well-validated workflow: concrete CLI commands, per-step validation, and robust recovery paths for every failure mode. Its weaknesses are duplicated procedural text (the thrice-repeated adapter-override rule and restated batch-flow instructions) and a monolithic structure where batch-splitting and artifact-generation protocols belong in dedicated reference files.
Suggestions
Consolidate the three near-identical '外部 OpenSpec Skill 适配规则' blocks into a single stated rule (or a short reference note) invoked from Steps 1 and 2, reclaiming roughly 60 lines.
Move the Step 1a batch-PRD-splitting protocol (~50 lines: candidate checklist, decision options, batch file schema, per-item checks, resume rules) into a dedicated reference file such as references/batch-splitting.md, keeping only the decision summary and confirmation gate inline.
Deduplicate the repeated batch pause/select instructions in Step 1a — '拆分完成后，必须暂停，请用户选择从哪一个 change 开始' is stated in at least three paragraphs covering the same scenario.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The "外部 OpenSpec Skill 适配规则" override block is repeated near-verbatim three times (after Steps 1, 2, and the openspec-propose note), and the batch pause/select instruction ("拆分完成后，必须暂停，请用户选择从哪一个 change 开始") is restated across multiple paragraphs in Step 1a. The body is mostly efficient with no concept padding, but could be tightened — the repetition exceeds the 'minor instances' of the 4 anchor. | 3 / 5 |
Actionability | Fully executable, copy-paste-ready commands throughout: "comet classic workspace prepare <name> --isolation <current|branch|worktree> --json", "comet state init <name> full --isolation <selected-isolation>", "comet classic openspec --agent-json -- instructions <artifact-id> --change \"<name>\" --json", "comet guard <change-name> open --apply". Expected output fields (changeRoot, applyRequires, resolvedOutputPath) are named so results can be checked, covering the common cases. | 5 / 5 |
Workflow Clarity | A clearly sequenced multi-step process (0, 0a-0c, 1, 1a, 1b, 2, 3, 4, 5, 退出条件, 自动衔接) with explicit validation checkpoints ("comet state check <name> open", "comet state artifacts <name> --json", "逐项检查批量创建结果（不得跳过）"), error-recovery feedback loops for done/ready/blocked artifacts, and mandated batch validation — matching the top anchor including the batch-operation requirement. | 5 / 5 |
Progressive Disclosure | The body has good section headers and delegates some detail to clearly-signaled external references ("comet-classic/reference/workspace.md", "decision-point.md", "auto-transition.md"), but this bundle ships no references/ of its own and long procedures — Step 1a's ~50-line batch-splitting protocol and the Step 2 artifact-generation loop — are inlined in a ~300-line monolith. This fits 'some structure, content that should be separate is inline' better than the 4 anchor's 'most content is appropriately placed'. | 3 / 5 |
Total | 16 / 20 Passed |