Conciseness

Every phase is prescriptive and dense ("Naming a file isn't grounding", "The synthesized sketch is the contract", "Complexity in the data is not complexity in the design") with zero padding, and detail is delegated to sibling skills and reference files rather than re-explained. Lean and efficient — every token earns its place, matching anchor 5.

Actionability

Guidance is consistently concrete for an instruction-only skill: run named skills (**how**, **why**, **arena**, **interrogate**), "Pass `references/runner-prompt.md` as each runner's prompt", explicit fallback runners ("claude-opus-5-5-xhigh" and "grok-4.7-xhigh-fast"), explicit skip conditions, and concrete scrap tells. Not anchor 5 because execution depends on external skills and a `pstack-models.mdc` rule outside the bundle, so it is not fully self-contained even with the fallback.

Workflow Clarity

Five named phases (Ground, Sketch, Agree, Implement, Scrap) sequenced with a prescribed todolist, an explicit Phase A skip rule, a clear default-vs-opt-in checkpoint, and strong feedback loops: deviations are "signal to surface", human pushback re-enters Phase A, and scrap tells trigger re-ground → redesign → return to Phase B. Clear sequence with explicit validation signals and error-recovery loops — anchor 5.

Progressive Disclosure

The body is a genuine overview that splits detail into three real, one-level-deep reference files (design-red-flags.md linked; runner-prompt.md and rationale-template.md cited by path in actionable context), verified to exist with no nested reference chains. Content is appropriately split and navigation is easy — anchor 5.

Specificity

"Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in" names several concrete third-person actions with only minor coverage gaps (e.g., synthesis and scrap phases are unmentioned). It lists more than the 1-2 actions of anchor 3 but is not the comprehensive coverage of anchor 5.

Completeness

It clearly answers "what" (sketch types, signatures, and module structure, then stay in the loop during implementation) and "when" via an explicit "Use for" clause with concrete trigger phrases. This matches the anchor-5 example structure of explicit what AND when with concrete triggers.

Trigger Term Quality

Triggers "/architect", "'architect this'", "'design this'", and "non-trivial work where jumping to code would lock in the wrong shape" are natural phrases a user would say, but common synonyms like "plan the architecture" or "sketch the design" are missing. Good coverage with a few natural terms absent — anchor 4, not the comprehensive synonym coverage of anchor 5.

Distinctiveness Conflict Risk

The design-first niche (types and module shape before code) is mostly distinct with clear triggers, but "design this" and the broad "non-trivial work" condition could overlap with general planning or UI-design skills. Minor overlap risk with closely related skills — anchor 4, not the minimal-conflict clarity of anchor 5.