Names the domain (PRDs, requirements) and mentions 'gathering requirements' and 'drafting PRDs' as actions, but doesn't list multiple concrete sub-actions like defining user stories, acceptance criteria, scope, etc.

Clearly answers both what ('gathering requirements and drafting PRDs') and when ('Use when creating a PRD, speccing a new feature, or clarifying requirements') with explicit trigger guidance.

Includes strong natural trigger terms: 'PRD', 'speccing a new feature', 'clarifying requirements', 'creating a PRD'. These are phrases users would naturally say when they need this skill.

PRD creation and iterative requirements discovery is a clear niche. The triggers (PRD, speccing a feature, clarifying requirements) are distinct and unlikely to conflict with general coding or documentation skills.

Every line earns its place. No unnecessary explanations of what a PRD is or how product management works. Telegraphic style with clear labels and minimal filler.

Provides concrete, specific guidance: exact directory paths (docs/specs/), template file to load (references/prd-template.md), output naming convention (prd-[feature-name].md), example question format with options, and specific anti-pattern corrections ('Fast' -> 'Load < 200ms').

Clear three-phase sequence (Discovery → Drafting → Verification) with an explicit iterative loop in Discovery ('Repeat until Actionable State'), a mandatory verification checklist, and anti-patterns serving as guardrails. The feedback loop of asking questions until sufficient info is gathered is well-defined.

Concise overview with well-signaled one-level-deep references to the full PRD template and validation checklist. Content is appropriately split—the skill file stays lean while pointing to detailed materials.