Requirements (PRD) Stage

Write a concrete first draft from research and sensible defaults BEFORE asking the user anything. Then resolve only the specific open items with AskQuestion.

Workflow

1. Research the product idea (web search when needed). Draft product/README.md: what the product is, who uses it, key behaviors, physical constraints, interfaces, power, target cost.
2. Write product/requirements.json:

{
  "requirements": {
    "battery_life_hours": { "value": 8, "source": "default" },
    "connectivity": { "value": "BLE 5.0", "source": "research" },
    "enclosure_max_size_mm": { "value": [60, 40, 18], "source": "user" }
  },
  "open_questions": []
}

3. Sources are exactly user / default / research. Anything the user said is user and belongs to them: never rewrite a user requirement to make a design pass — ask that single item instead.
4. If concrete product facts remain genuinely open (not resolvable by defaults), put them in open_questions and resolve them with the AskQuestion tool, one batch, specific items only, each with 2-4 concrete options. Write answers back with source: "user" and empty the list. Never ask for whole-PRD approval.
5. Write product/contract.json declaring which deliverables the product needs:

{
  "deliverables": {
    "custom_pcb": true,
    "enclosure_cad": true,
    "firmware": false,
    "print_files": true
  }
}

6. PRD is ready when open_questions is empty. State what was written, then stop and invite the next stage - the user's next message authorizes it.

For the complete original field contracts (contract.json v2 allowed values: artifact_level, deliverable_intent, interface sources, CAD delivery targets; and the prd_change_confirmation flow for revising user-owned requirements), read <repo>/reference/replicator-original/product/requirements-contract/references/product-files.md.