Conciseness

Every clause carries domain protocol and no concepts Claude already knows are explained, but the reuse/don't-requery rule is restated repeatedly ("do not retrieve repeatedly", "Do not reload the protocol", "Reuse them when already available", "Reuse the latest valid response", "Reuse current valid state"), matching anchor 4 (minor instances that could be trimmed). It is not 5 because a tightened single statement of the reuse policy would remove noticeable redundancy; not 3 because there is no unnecessary explanation or padding beyond that repetition.

Actionability

Fully executable, copy-paste-ready commands with flags and placeholders cover the common cases: "comet state propose-archive <change-name> --summary \"<delivery-summary>\"", "comet state decide-archive <change-name> --proposal-hash <proposalHash> --choice <local|push|pr|reverify|later>", "comet guard <change-name> archive --apply", and "comet state complete-delivery <change-name> --commit <sha>". This matches anchor 5; it is not 4 because the command set is complete for all delivery branches rather than having gaps.

Workflow Clarity

A clearly numbered 1-5 sequence includes explicit validation steps ("Guard checks authorization, branch, and Verify receipts"; complete-delivery "validates the archive commit and approved remote/PR delivery") and feedback loops for error recovery ("After interruption inspect state next --json and --recover"; "On an unknown result, read the remote or PR before retrying"; "On failure preserve the Run and decision and address the reported gap"). This matches anchor 5; the destructive-operation cap does not apply since validation and recovery checkpoints are present throughout.

Progressive Disclosure

The body stays lean by deferring detail to one-level-deep, well-signaled references with explicit read-conditions ("[Task Context and Artifact Language](../comet-classic/reference/scripts.md...)", "[phase entry and recovery](../comet-classic/reference/sdk-methods.md...)"), matching anchor 4 (references mostly clear, minor organization gaps). It is not 5 because "reference/compat.md" and "decision-point.md" are referenced but do not resolve within this bundle (no references/ directory exists), leaving navigation slightly ambiguous.

Specificity

"Archive and deliver a Classic change" names the domain with exactly two actions ("Archive", "deliver"), matching the anchor for 1-2 concrete actions that are not comprehensive. It is not 4 because "deliver" is generic and no several specific actions (e.g., commit, push, open PR) are enumerated, and not 2 because "archive" is a concrete domain-specific action rather than purely generic.

Completeness

Explicitly answers "what" ("Archive and deliver a Classic change") and "when" with three concrete trigger phrases ("invokes /comet-archive or Classic Runtime enters Archive or resumes delivery"), matching the anchor for clearly answering both with concrete triggers. It is not 4 because the "when" clause is already explicit and specific, leaving no gap that anchor 4 describes.

Trigger Term Quality

Triggers are "/comet-archive", "Classic Runtime enters Archive", and "resumes delivery" — relevant and precise but all system jargon with no natural-language variations or synonyms a user would casually say. This matches anchor 3 ("Some relevant keywords but missing common variations or synonyms") rather than 4, which requires good natural keyword coverage.

Distinctiveness Conflict Risk

The unique slash command "/comet-archive" plus phase-scoped terms ("Classic Runtime", "Archive", "resumes delivery") establish a clear niche with distinct triggers and minimal conflict risk, matching anchor 5. It is not 4 because no overlap with closely related skills is apparent — the triggers are unambiguous within the comet skill family.