Conciseness

The body is a dense, telegraphic index ("never `which gh`, never `gh auth status`") that explains nothing Claude already knows, but "Phase 0 and Phase 2 are mandatory" is stated three times and the Q2/Q4 exegesis under "Two readings this exists to rule out" runs long, leaving minor instances that could be trimmed — anchor 4 rather than 5.

Actionability

Concrete, executable guidance dominates: `bash scripts/sync-symlinks.sh --aw`, `gw add <branch>`, an exact MODE SELECTION output block, and a complete worked Lite brief template. Core phase procedures are deliberately deferred to `rules/*.md`, so in-body guidance is mostly rather than fully copy-paste complete, fitting anchor 4.

Workflow Clarity

The phases 0–7 table gives every phase an explicit gate ("Suite green, then `run-checks.mjs` prints `CHECKS M/M PASS`"), mandatory phases are flagged, termination is sentinel-based and deterministic, stuck-loop caps escalate via `Skill("confidence", "analysis")`, and feedback loops are explicit ("A failed `ui:` criterion … re-enters Phase 3 under the same turn cap"; "Watch CI, `ci-auto-fix` if needed") — a clear match for the anchor-5 validation-and-recovery pattern.

Progressive Disclosure

The body declares itself an index ("procedures live in `rules/*.md` and load on demand") with one-level-deep, condition-signaled references ("read when a prerequisite is missing", "each read when it applies"). Against the actual bundle, however, most referenced paths (rules/, templates/, aw/, CLAUDE.md, README.md) are absent and 8 of the 9 files in references/ are not reachable from the body, so navigation is good but not fully verifiable — anchor 4 rather than 5.

Specificity

Concrete mechanisms are named end-to-end — "task intake through a tested draft PR in an isolated worktree", "gated by the plan.md brief and the run-checks.mjs sentinel" — but the description frames them as architecture ("the phase machinery behind the `aw` dispatcher") rather than enumerating several distinct actions, so it sits between the 3 and 5 anchors at 4.

Completeness

Both what and when are explicit — "invoke /autonomous-workflow only to run the phases directly" is equivalent explicit trigger guidance, so the missing-'Use when' cap does not apply — but the when clause is a routing boundary against the sibling `aw` skill rather than a fuller set of concrete situational trigger phrases, fitting anchor 4 rather than 5.

Trigger Term Quality

Some relevant natural terms appear ("autonomous work", "draft PR", "worktree", "task"), but the description leans on internal jargon ("dispatcher", "sentinel", "companions that never block") and omits common user phrasings like autonomously implementing a feature or running phases directly, matching the "some relevant keywords but missing common variations" anchor.

Distinctiveness Conflict Risk

"Not the entry point — natural-language requests for autonomous work go to the `aw` skill" actively disambiguates this skill from its sibling dispatcher, giving it a clear niche with distinct triggers and minimal conflict risk, which matches the anchor-5 example exactly.