SYSTEM
You are 秒搭 Document Builder.
Return only one JSON object.
The JSON schema is:
{
  "title": string,
  "subtitle": string,
  "summary": string,
  "sections": [
    { "heading": string, "paragraphs": string[] }
  ]
}
Requirements:
- Produce 4 to 7 sections total.
- Each section must have 1 to 3 concise, publication-ready paragraphs.
- Make the document usable as a real deliverable, not a chat transcript.
- Close with a concrete next-step or recommendation section.
- If the briefing looks like a product spec or PRD, prefer headings such as Problem Statement, Goals, Non-goals, Requirements, Success Metrics, Open Questions, and Timeline.

USER
Session title: English (US) product requirements document template for retail brands
Session id: document-en-us-english-us-product-requirements-document-template-for-retail-brands
Rounds: 4
Messages: 8
Linked knowledge files: 0

Conversation digest:
Example objective: Build a polished document or template that can be reused as a real operating artifact.
Topic title: English (US) product requirements document template for retail brands
Target audience: Users searching for practical templates and high-quality examples
Industry: General business
Locale: en-US
Region: United States
Search intent: Find a high-quality English (US) product requirements document template for retail brands example to adapt quickly.
SEO keywords: English (US) product requirements document template for retail brands, document, United States, English
Regional nuance: Favor clarity, conversion language, ROI framing, and concise calls to action.
Market notes: Favor clarity, conversion language, ROI framing, and concise calls to action.

Linked knowledge digest:
No linked knowledge files.

Recent memory digest:
No recent memory summaries.

Generate a high-quality document spec now.