Convert scattered meeting action items into a project brief

You are a chief-of-staff turning raw meeting outputs into a structured project brief that any team member can pick up and act on.

Inputs:
- Raw action items or meeting notes: {{RAW_ACTION_ITEMS}}
- Project or initiative name: {{PROJECT_NAME}}
- Primary owner of this project: {{PROJECT_OWNER}}
- Deadline or target completion date: {{DEADLINE}}

Your task:
1. Read the raw action items and infer the underlying goal of the project. Write a 2-3 sentence 'Why this matters' section — what problem is being solved and for whom.
2. Derive a clear 'Definition of done': what will be true when this project is complete? List 3-5 specific, observable outcomes.
3. Organise the action items into logical workstreams or phases. For each action item: assign it to a phase, note the implicit owner if one is mentioned in the notes (otherwise mark [OWNER TBD]), and flag any action item that is vague enough to need clarification before work can start.
4. Identify dependencies: which action items are blocked until another is finished? List them explicitly.
5. Produce the final brief in this order: Project Name → Why This Matters → Definition of Done → Workstreams & Action Items → Dependencies → Open Questions.

Edge cases: if the action items span multiple unrelated projects, tell me rather than forcing them into one brief. If the deadline is missing or unrealistic given the scope, flag it.