Conciseness

Mostly operational with no padded conceptual explanations, but noticeable duplication: the '[ -x "${CLAUDE_PLUGIN_ROOT:-}/scripts/jira-site-guard.sh" ] ...' guard line appears verbatim 8+ times, and the JQL parent/label verification commands are repeated in both 'Known limitations' and 'Capturing created issue keys'. Matches the 3 anchor ('mostly efficient but ... could be tightened'); not 4 because the repetition is more than minor, and not 2 because there is no over-explanation of concepts Claude already knows.

Actionability

Every section provides copy-paste-ready executable commands with exact flags, jq pipelines, the bulk JSON schema, and literal error messages (e.g. '✗ Error: Please select valid parent issue.'). Fully executable with the common cases covered — matches the 5 anchor.

Workflow Clarity

'Workflow pattern for story creation' gives a 7-step ordered sequence with step 4 'Capture returned issue keys' plus a jq key-extraction snippet, post-write verification via JQL ('confirm the story is parented'), and a dedicated error-handling section with recovery paths per failure mode (DNS block, auth, project/parent not found, rate limit). Clear sequence with explicit validation steps and error-recovery feedback loops — matches the 5 anchor; the batch-operation validation cap does not apply because verification is present.

Progressive Disclosure

Good structure with clear section headers, and the ADF detail is properly split out behind a bold, clearly signaled one-level reference ('Before writing any description or comment to Jira, read .claude/refs/jira-adf.md'). Minor gaps: the ~320-line body inlines content (auth-guard internals, link-direction semantics, known limitations) that could live in reference files — matches the 4 anchor; not 5 because the split is only partial.

Specificity

Names the tool and domain ('acli (Atlassian CLI) to interact with Jira Cloud') and lists five concrete actions ('create, search, view, link, and edit work items'), but omits body-covered operations such as commenting and bulk creation. Matches the 4 anchor ('several specific actions; minor gaps in coverage'); not 3 because coverage far exceeds 1-2 actions, and not 5 because comment/bulk-create are core operations left unstated.

Completeness

The 'what' is explicit ('interact with Jira Cloud — create, search, view, link, and edit work items via shell commands') and a 'when' is present via the routing directive 'Prefer acli over Atlassian MCP to minimize token usage', but there is no explicit 'Use when...' trigger clause. Fits the 4 anchor ('when' could be more explicit or specific); not 3 because the when-guidance is stated rather than merely implied, and not 5 because no concrete trigger phrases are given.

Trigger Term Quality

Includes strong natural terms — 'Jira Cloud', 'Atlassian', 'work items', 'shell commands', 'MCP tools' — but misses common variations users actually say such as 'tickets', 'issues', 'stories', or 'epics'. Good coverage with a few natural terms missing matches the 4 anchor; not 5 because synonym coverage is incomplete.

Distinctiveness Conflict Risk

Clear niche (Jira work-item management via a specific named CLI) with explicit disambiguation from the main competing transport ('instead of MCP tools', 'Prefer acli over Atlassian MCP'). Minimal conflict risk — matches the 5 anchor.