Conciseness

The body teaches only non-obvious, Archon-specific behavior ('A detached run starts its own session and survives your shell', 'with dozens it contends for the database') with no padding or explanations of concepts Claude already knows. Every section — routing table, operating loop, hard rules, gotchas — carries information Claude could not infer.

Actionability

Fully executable commands cover the common cases: `archon workflow run <workflow> --branch <branch-name> "<the work>" --detach`, `archon workflow attention --watch --json`, `archon workflow respond <run-id> <decision> "<reason>" --detach`, `archon workflow get <run-id> --json`, and `gh pr merge <n> --match-head-commit <sha>`. Nothing is pseudocode or abstract.

Workflow Clarity

The operating loop is a clear six-step sequence (Discover, Check the brief, Launch detached, Watch once, Answer deliberately, Read the result) with explicit validation checkpoints ('get the user's agreement before launching', 'Read the report before telling the user what the run concluded', 'read the open review threads first' before merge). Destructive operations (cancel, hand-merge) carry consequence warnings and safer alternatives (`end-turn`, match-head-commit), and stalled/failed runs route to troubleshooting — so the destructive-operation cap does not apply.

Progressive Disclosure

The intent-routing table ('The user wants to... | Read') maps every intent to a one-level-deep reference file, and inline pointers cite exact sections ('operate/managing-runs.md, "A stalled turn"'). The body is a lean overview that appropriately defers detail to the referenced files; no content that belongs in a separate file is inlined.

Specificity

The description lists multiple concrete actions with comprehensive coverage: 'run AI workflows on a repo, watch and answer the runs that need a decision, drive the SDLC pack's queues (intake, build queue, merge queue, discoveries), set up Archon or change its config, and author and validate workflows'. Not score 4, which requires minor gaps in coverage — operating, queue-driving, setup, and authoring are all explicitly named.

Completeness

Both questions are answered explicitly: a concrete 'what' (the action list) and an explicit 'when' with quoted trigger phrases ('Use when the user says...'), plus a negative boundary ('NOT for: doing the coding work yourself'). This matches the 5 anchor exactly.

Trigger Term Quality

Comprehensive natural trigger phrasing including synonyms and variants: 'use archon', 'run archon', 'archon workflow', 'fix issue #N with archon', 'have archon review this PR', "what's running / check run <id>", 'approve/reject/answer/cancel/resume that run', 'drain discoveries', 'set up archon' / 'configure archon' / 'change my archon config', 'create a workflow' / 'author a workflow'. Matches the 5 anchor (natural terms, synonyms, and variations) rather than the 4 anchor (a few natural terms missing).

Distinctiveness Conflict Risk

Clear niche — delegating work to isolated Archon runs via its CLI — with distinct triggers tied to the product name and an explicit NOT-for clause separating it from doing the coding work directly. Minimal conflict risk with other skills.