Conciseness

The body is dense and instruction-only — no explanations of concepts Claude already knows — with exact commands, prompts, and schemas throughout. It is not anchor 5 because of minor trimmable redundancy: the Error Handling section restates exit conditions already specified in Steps 1-2 (e.g., "No merged features — inform the user... Run /arn-code-batch-merge first" appears twice), and the Step 5 example findings block is somewhat long. It is above anchor 3 since nearly all content is operational guidance rather than unnecessary explanation.

Actionability

Guidance is fully executable: exact shell commands ("git checkout -b batch-simplify/<date>", "gh pr create --title '[batch-simplify] Cross-feature quality improvements'..."), exact snapshot.sh invocations, a verbatim applier prompt with a strict JSON return schema, exact user-facing prompts, and exact fallback paths. This matches the copy-paste-ready anchor covering the common cases, exceeding anchor 4 which allows minor gaps.

Workflow Clarity

Steps 0-9 are clearly sequenced with exit conditions at scoping stages, user approval gates (Steps 3, 6, 9a), and explicit validation feedback loops for this batch operation: per-finding test runs, up to 3 self-heal attempts with re-runs, per-finding revert on failure, a final cumulative test pass, and partial-failure handling for reviewers and the applier. This matches the top anchor (explicit validation, feedback loops, error recovery), well above anchor 4.

Progressive Disclosure

The one bundle reference (references/cross-feature-prompts.md) is real, well-signaled, one level deep, and loaded exactly when needed in Step 4; the body sections are clearly organized with headers. It is not anchor 5 because SKILL.md is not an overview pointing to detailed materials — the full 35-line applier prompt template and example findings presentation are inlined where a reference file (like the existing prompts reference) could carry them, and several detailed materials (ensure-config references, snapshot.sh, report template) live as ${CLAUDE_PLUGIN_ROOT} cross-skill references outside this bundle. It exceeds anchor 3 since the structure present is good and references are clearly signaled.

Specificity

The description names the domain ("post-merge quality pass") and 1-2 concrete actions ("finds duplication and consolidation opportunities across independently implemented features"), matching the anchor for domain plus 1-2 actions. It falls short of anchor 4 because it does not list several specific actions (e.g., dispatching reviewers, applying fixes, generating a report), and exceeds anchor 2 since the actions named are concrete rather than generic.

Completeness

It explicitly answers 'what' ("post-merge quality pass that finds duplication and consolidation opportunities across independently implemented features") and 'when' ("This skill should be used when the user says... or wants to run a post-merge quality pass") with concrete trigger phrases, plus a stated precondition ("requires merged features in .arness/plans/ — run arn-code-batch-merge first"). This matches the top anchor for both what and when with concrete triggers.

Trigger Term Quality

It lists 15+ natural trigger phrases with synonyms and variations ("batch simplify", "cross-feature simplify", "simplify all features", "batch code cleanup", "deduplicate across features", "post-merge simplify", "find cross-feature duplication"), comprehensively covering how a user would naturally phrase the request. This matches the comprehensive-synonyms anchor and is clearly above anchor 4, which expects only a few missing natural terms.

Distinctiveness Conflict Risk

Triggers consistently carry the cross-feature/batch/post-merge qualifier ("cross-feature deduplication", "simplify merged features"), establishing a clear niche with minimal conflict risk against unrelated skills. It is not anchor 5 because of minor overlap risk with the closely related single-feature 'simplify' skill — phrases like "batch simplify" or "simplify all features" could plausibly be said when a user wants a plain simplification pass — but it is well above anchor 3 since the cross-feature scope is explicit throughout.