Conciseness

The body is dense, skill-specific policy with no padding about concepts Claude already knows ("Re-platform by default: pick the AWS service that matches the Azure workload type (App Service → Elastic Beanstalk, AKS → EKS, ...)"). It fits the 4 anchor (efficient, minor instances of over-explanation that could be trimmed): the `run_mode` semantics appear in three sections (Execution, State Management, Sidebar Placement), and passages like "The eligibility rule exists precisely so that the two cases named above ... never reach the short path" over-justify already-stated rules. It is not 3 because nearly every token carries non-inferable skill policy, and not 5 because some multi-clause sentences (e.g., the Clarify fast-path and live-first Philosophy paragraphs) must be re-read to parse.

Actionability

Directives are specific and executable: an exact entry point ("begin at `references/phases/discover/discover.md`"), copy-paste-ready outputs ("Unrecognized phase: [value]. Valid phases: discover, clarify, design, estimate, workshop, generate, feedback."), a verbatim feedback prompt with [A]/[B] options, exact defaults ("Region: `us-east-1`", "CPU architecture: `x86_64`"), and named MCP tools (`aws___search_documentation`, etc.). For an instruction-only orchestrator this matches the 5 anchor — concrete, specific guidance covering the common cases; not 4, because there are no high-level hints without a corresponding executable directive.

Workflow Clarity

Sequencing is unambiguous (cold start entry phase, `_advances_to` chain, warm-start rules, mandatory Clarify with no exceptions) and validation is explicit: seven numbered state-validation checks with STOP conditions, plus a full error-recovery feedback loop for corrupt `.phase-status.json` (enumerate artifacts → infer completed phases → confirm with the user → rewrite the file). This matches the 5 anchor (explicit validation steps, feedback loops for error recovery, checklists); it is not 4 because checkpoints are explicit rather than implicit, and the noted caveat that `generate.md`'s `_assert` "has no mechanical teeth" is disclosed rather than hidden.

Progressive Disclosure

The body is a genuine overview that pushes detail into a well-organized bundle (phases/, design-refs/, shared/, vendored/), enforces load discipline ("~800 lines of instructions", "Do not speculatively load files", "a pattern may never change a deterministic mapping's target" lives once in Philosophy), and the vendored contracts (`INTERPRETER.md`, `phase-status.schema.json`, `PROTOCOL.md`) are loaded once and referenced by name. It fits the 4 anchor (good structure, references mostly clear, minor organization gaps) rather than 5 because references chain more than one level (SKILL.md → phase file → fragment → shared ref such as `extract-terraform.md`) and several mentions are bare filenames without paths ("`clarify.md` § Step 0.5", "`estimate-assemble.md` § Step 3b"). It is not 3 because nothing that belongs in a separate file is inlined and navigation is easy via the directory layout.

Specificity

Lists many concrete actions and inputs — "discover Azure resources from Terraform, the live `az` CLI, a customer-supplied Resource Discovery for Azure (RDfA) report, and app code, then clarify, design, estimate, optionally reprice, generate artifacts, and collect feedback" — plus concrete service mappings ("migrate AKS to EKS", "migrate Cosmos DB to DynamoDB", "migrate Azure OpenAI to Bedrock"). This matches the 5 anchor (multiple specific concrete actions, comprehensive coverage); it is not 4 because there is no coverage gap — discovery sources, phases, gates, and exclusions are all enumerated.

Completeness

Both questions are answered explicitly: the "what" ("Migrate workloads from Microsoft Azure to AWS. Runs a 6-phase process: ...") and the "when" (an explicit "Triggers on:" clause with concrete phrases, plus a "Do not use for: GCP ... Heroku ... AWS-to-Azure reverse migration" exclusion list). This is exactly the 5 anchor — explicit what AND when with concrete trigger phrases — not 4, since the "when" needs no additional specificity.

Trigger Term Quality

"Triggers on: migrate from Azure, Azure to AWS, migrate AKS to EKS, migrate App Service or Azure VMs to AWS compute, ... estimate AWS costs for Azure, what-if workshop" covers the natural phrasings and service-pair synonyms a user would actually type. It fits the 5 anchor (comprehensive natural terms including synonyms) rather than 4 ("a few natural terms missing") because every common way of asking for an Azure-to-AWS migration or cost estimate is present.

Distinctiveness Conflict Risk

The direction is unambiguous (Azure-to-AWS, not reverse) and sibling conflicts are explicitly redirected: "Do not use for: GCP (see gcp-to-aws) or Heroku (see heroku-to-aws) migrations, general AWS architecture advice (see architect-for-startups), AWS-to-Azure reverse migration, or Azure-to-Azure refactoring." Clear niche with distinct triggers and minimal conflict risk — the 5 anchor; not 4 because it does not merely reduce overlap, it enumerates and routes the overlapping cases.