PRD creation and revision

Turn a product idea or an existing requirements document into a clear, testable PRD. A PRD is a product decision record: keep business intent and evidence visible, while leaving implementation choices open unless the user or a source has decided them.

Route before writing

Read prd-revision-rules.md before revising an existing PRD, strategy table, or requirements section. Classify material as:

• confirmed requirement or verified fact;
• proposed decision, which must stay labelled as a proposal until accepted;
• unresolved question or dependency, with the missing evidence and impact recorded.

“Fix all issues” authorizes repairs within the stated scope. It does not approve new thresholds, durations, priorities, triggers, actions, retention rules, or policy. Correct clear errors and broken references directly; ask or record a decision when behavior would change. If the user asks only for review, do not write files.

For an existing document, use the latest source as the baseline, patch the requested sections, update directly affected references, and preserve unrelated content and formatting. For a local or remote document, write only through the requested destination and report what was changed and read back. Follow the current Lark skill and CLI help for remote edits; do not assume a command or tool exists.

Output and language

Honor the user's language, output format, filename, and location. If they have not specified a language, use the language of the request and ask only when the audience makes that choice material. Do not silently create a Markdown file or a cloud document during inspection or review.