prd-writinglisted

# PRD Writing ## Goal Create `outputs/<run-id>/prd.md` as a product document that starts from users and their problems, then makes every proposed behavior reviewable through a requirement list and matching requirement details. ## Workflow 1. Load `artifacts/prd-contract.md`. Use its canonical ordered structure only for a new PRD. When a new PRD migrates or references another PRD, the source supplies only confirmed requirement content, terminology, assets, and explicitly requested migration boundaries; it never supplies the new document's chapters, field labels, numbering, or template unless the user explicitly says so. Do not record an assumption that the new PRD follows the source PRD's structure. For an in-place revision, the identified PRD is the sole structural source of truth: preserve its existing chapter order, headings, fields, numbering, and unaffected content. Do not use another or older PRD, or the new-document template, to normalize its overall structure unless the user explicitly requests a structural rewrite. Apply only the user-requested patch; when that patch concerns screenshots, it is limited to the matching `需求详情` cell. Remove deleted requirements and renumber the remaining detail IDs consecutively only when the user requested a requirement deletion. 2. Identify target users, their scenario, problem, desired outcome, and the source or confirmation status before drafting requirements. 3. For a new PRD, apply the evidence boundary and requirement-granular