Conciseness

The body is dense with non-obvious, tool-specific facts only (PTY/TUI blocking, "`gh stack help <command>` does not work", exit-code semantics, stale `base` SHA meaning) and explains nothing Claude already knows. No trimmable over-explanation was found, so it fits the lean/every-token-earns-its-place anchor rather than the minor-trimming anchor.

Actionability

Copy-paste-ready commands throughout: the core loop, the edit flow (`gh stack down` ... `rebase --upstack` ... `push`), `sync --prune`, and `merge 42 --yes --squash`, plus an always-run/never-run flag table, a JSON output schema, and a recovery column for every exit code. Fully executable and covering the common cases.

Workflow Clarity

Multi-step flows are explicitly sequenced with validation checkpoints ("`gh stack view --json` # confirm", "Check the exit status before changing directories", "branch on exit codes") and genuine feedback loops for error recovery (Exit 3 resolve → `git add` → `rebase --continue`/`--abort`, sync-divergence abort, lock retry). Destructive and batch operations all carry validation or recovery, so the workflow-clarity cap does not apply.

Progressive Disclosure

The body stays an overview and delegates detail to three real, one-level-deep reference files (verified on disk: stack-design.md, commands.md, troubleshooting.md), each given an explicit trigger ("read before creating a stack", "read when a command fails unexpectedly", "read on a rebase conflict") plus "no need to preload all three". Reference cross-links are sibling-level only, matching the clear-overview anchor.

Specificity

"Manages stacked PRs and splits multi-part work into reviewable branches" plus "stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout" names nine concrete operations covering the full stack lifecycle, matching the comprehensive-coverage anchor rather than the minor-gaps anchor.

Completeness

It explicitly answers "what" ("Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack") and "when" ("Use for ... whenever a user mentions a stack, branch layers, dependent PRs, or gh stack; or when a stack is checked out") with concrete trigger phrases, matching the anchor-5 example.

Trigger Term Quality

Natural trigger terms include "a stack, branch layers, dependent PRs, or gh stack" and "split or isolate work for review", covering colloquial synonyms plus the exact CLI string a user would type. It is not a 4 because both the natural phrasings and the literal tool invocation are present.

Distinctiveness Conflict Risk

The niche is clear ("stacked PRs", "dependent PRs", "gh stack"), but the bare verb list "push, submit, sync, rebase, merge, or checkout" in the Use-for clause could fire on ordinary git/PR requests, giving minor overlap risk with generic git-workflow guidance. It is not 5 because of that unscoped verb list, and not 3 because the domain triggers are strongly specific.