Terse bullet-style instructions with zero concept-explaining fluff (e.g., 'No Vagueness: "Fast" -> "Load < 200ms"'); every line earns its place and assumes Claude's competence rather than the padded level-2 style.

Instruction-only yet highly actionable: concrete file paths ('docs/prd/prd-[slug].md'), stable ID conventions ('REQ-*', 'AC-*'), Given/When/Then, INVEST, and a worked example ('Target platform? a) Web b) Mobile c) Both'), so guidance is specific rather than the incomplete level-2 form.

Clearly sequenced Discovery → Drafting → Verification phases with an explicit feedback loop ('Repeat: Continue until Actionable State reached'), a mandatory verification checklist, and an Implementation Gate checkpoint, matching the explicit-validation anchor rather than the gaps at level 2.

Body is a lean overview with well-signaled one-level-deep references to verified-real files ([Full PRD Template](references/prd-template.md) and [Validation Checklist](references/checklist.md)); content is appropriately split out, satisfying the top anchor. (The un-linked lean-spec-template.md is a minor orphan but does not undermine the signaled references.)

Names multiple concrete actions ('Standardize PRD discovery and drafting') and concrete deliverables ('product scope, user outcomes, requirement IDs, and acceptance criteria'), matching the multiple-specific-actions anchor rather than the partial level 2.

Explicitly answers both what ('Standardize PRD discovery and drafting...') and when with an explicit 'Use when creating PRD, product requirements...' trigger clause, satisfying the top anchor.

Includes natural terms users actually say — 'PRD', 'product requirements', 'feature specification', 'acceptance criteria' — giving good coverage rather than the partial keyword set at level 2.

Clear PRD/product-requirements niche with distinct triggers; unlikely to fire for adjacent skills (BRD/SRS are explicitly routed away in the body), so it is distinguishable rather than merely 'somewhat specific'.