prd-skills

Use when asked to create, write, or draft a PRD, product requirements document, design doc, or feature specification for a software project

Use when asked to audit, verify, validate, or check the implementation of a PRD against the shipped code -- confirming every goal is met, no stubs or TODOs remain, tests/playbooks/build/lint pass, no regressions were introduced, and scope matches what the PRD promised

Use when asked to review, audit, critique, or validate an existing PRD, design doc, or feature specification