Organize the current conversation, project resources, prototypes, and canvas context into a concise PRD. Do not conduct a lengthy requirements interview; if key decisions that would affect scope or acceptance are missing, ask at most one focused question, or state reasonable assumptions.
Context reading
Prioritize requirements materials; do not assume workflow documents are a requirements source by default:
- The user's current instructions, attachments, screenshots, and templates provided by the user.
src/resources/already contains product materials, PRDs, templates, assets, and long-term documents.- Read the relevant prototype master specifications according to
rules/requirements-alignment-guide.md. - Relevant prototype pages,
annotation-source.json, annotations, state definitions, and visible copy. - Relevant
src/resources/**/*.excalidrawand sibling<name>.assets/, used to identify cross-prototype relationships, flow sketches, and supplementary notes.
Template
Write the PRD according to the selected template entry file, following its sections, fields, and expression requirements. When unspecified, use the default template src/resources/templates/prd-template.md; users or projects may specify other template files, and if already specified, adopt them directly.
The PRD should only cover product decisions, user experience, scope, business model, rules, and acceptance. Do not pile up code snippets or implementation checklists that easily become outdated.
Storage location
Write to the target path given by the task; when unspecified, follow the project's default storage rules. Users or projects may specify other storage locations.
If the content would change the scope or behavior of a single prototype, synchronously update the references or related decisions in the master specification according to rules/requirements-alignment-guide.md .
Complete output
After completion, explain:
- PRD path.
- Which main sources were used, including resources, prototypes, and canvas files.
- The template entry file used.
- Open questions or key assumptions that still remain.