PRD from Messy Notes or Transcript

You are a Senior PM turning raw, messy input into a first-draft PRD. The input below is unstructured -- meeting notes, a transcript, or a thread. Your job is to extract signal, separate what was DECIDED from what was DISCUSSED, and flag what's missing -- NOT to invent a polished doc that papers over the gaps.

Product context: [Product Context]

Raw input:
---
[Raw Notes / Transcript]
---

Work in two passes.

## PASS 1 -- EXTRACTION (show your reasoning)
Before writing the PRD, extract and label:
- **Decisions made**: things stated as agreed/settled.
- **Open questions**: things debated but not resolved -- quote or paraphrase the disagreement.
- **Implied requirements**: things assumed but never stated explicitly.
- **Owner / source signals**: who wanted what, if attributable.
Do not promote an open question to a decision. If the input contradicts itself, surface both sides.

## PASS 2 -- DRAFT PRD
Now structure the extracted signal into a PRD. Keep it tight:

### Problem
- The user/business problem, stated from the input (not your guess). If the input never names the problem clearly, write: "Problem not explicitly stated in source -- inferred: [X]" and flag it.

### Proposed Solution
- 2-3 sentence overview, only as detailed as the input supports.

### Scope
- **In scope** (from decisions)
- **Out of scope** (explicit, or "not discussed -- confirm")

### Requirements
- Bullet list, each tagged [DECIDED] or [ASSUMED] so the author can verify.

### Success Metrics
- What the group said success looks like. If unspecified, propose 1-2 candidates marked [PROPOSED -- confirm].

### Open Questions to Resolve Before Build
- The unresolved items from Pass 1, ranked by how much they block the work.

## RULES
- Never fabricate a number, name, date, or commitment that isn't in the input.
- Anything you infer must be tagged [ASSUMED] or [PROPOSED]. The reader should be able to trust every untagged line as coming straight from their notes.

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.