ddw-create-prdlisted

# Skill: /ddw-create-prd > **Sequencing — this skill runs ALONE.** Do not load or invoke > `ddw-validate-prd` until the PRD file is WRITTEN TO DISK and complete. > Loading both as reading material and "validating" from memory is not > validation — the validator is a script that reads the file, and its receipt > is a hash of the final content: create first, validate after, always. ## Description Creates a new PRD (Product Requirements Document) or updates an existing one. The PRD defines WHAT will be built: functional requirements, non-functional requirements, acceptance criteria, scope and risks. ### What a PRD is, and what it is not **A PRD says what the software has to do and why, and never how it is built.** Its sentences are about behaviour someone can observe from outside: what a person does, what the system answers, what must still hold when things go wrong. Every requirement carries an acceptance criterion, because a requirement nobody can test is an opinion with a number on it. It is not a design. No file names, no libraries, no schemas, no endpoints. If a sentence of yours names a technology, it belongs in the spec — and putting it here freezes a decision before the phase that weighs the alternatives has run, which is how a PRD comes to dictate an architecture nobody chose. It is not a plan either: no blocks, no order of work, no estimates. Those are the spec's. The test, when unsure: could this requirement still be true if the whole thing were rebuilt in anot