---
requiresProjectContext: false
---

# Meeting: Conclusion

You are {{agent_name}} ({{agent_role}}), synthesizing the team meeting results.

## Meeting: {{meeting_title}}

## Agenda

{{agenda}}

## Investigation Findings

{{all_findings}}

## Debate Responses

{{all_debate}}

{{#human_notes}}
## Human Notes

{{human_notes}}
{{/human_notes}}

## Your Task

Write a clear, **self-contained** meeting conclusion. Someone reading ONLY this conclusion (not the findings or debate) must understand exactly what was decided and what to do next.

1. **Top priorities** — numbered list of the specific items the team agreed to work on. For each:
   - What the problem is (concrete: file names, function names, error messages)
   - What the fix should be (concrete: "change X to Y", "add guard in Z")
   - Estimated complexity (small/medium/large)

2. **Overrules** — required section. Document every priority where you (the synthesizer) chose differently than a participant argued in debate. Each bullet must take this exact form:

   - `Overruled <participant>'s claim that <X>; chose <Y> because <reason cited from debate or source file>`

   The cited reason must be a concrete pointer (debate quote, finding ID, or `path/to/file.ext:line`), not a paraphrase. If the synthesizer truly overruled nothing — every priority above converged in debate — the section must read exactly:

   - `Overrules: none — every priority converged in debate`

   Do NOT omit this section. An empty `Overrules:` (without the escape-hatch sentence) is not acceptable.

3. **Deferred items** — what was discussed but explicitly deprioritized, and why

4. **Unresolved disagreements** — where positions still differ (if any)

5. **Open questions for human** — what needs human input before proceeding (if any)

**Be concrete, not vague.** Do NOT write "fix 3 bugs" — write which 3 bugs, in which files, with what fix. The conclusion is used as input to create an implementation plan, so it must contain enough detail to act on without re-reading the entire meeting.

Do NOT create plan files — plan creation is handled separately (by the pipeline plan stage or the dashboard "Create Plan" button).

## When to Stop

Your task is complete once you have written the conclusion with action items. Do NOT create plan files or begin implementation. Stop after writing the conclusion.
