Meeting Minutes Assistant

Problem

Meeting Minutes Assistant works on meeting text that has already been transcribed and roughly organized upstream. It fixes unstable template rendering: inconsistent issue splitting, arbitrary conclusions, mixed problem types, and uncertainty around owners and product terms.

How It Works

It generates paste-ready Markdown according to templates/sample.md:
- Issue recognition: split by explicit headings; if absent, create a 10–20 character short title.
- Review type: use online review when the text says “online review / async review / comment-section review / online review”; otherwise default to meeting review.
- Conclusion: default to “Approved, no re-review needed”; switch to “Not approved, re-review required” only when explicit re-review semantics appear.
- Issue classification: emit 【Clarification】, 【Suggestion】, 【Question】, or 【Defect】; use Defect only when repair, error, or risk can be clearly inferred.
- Two-stage confirmation: draft first, then ask one item at a time to verify proposer, owner, details, or terminology before final output.

Boundaries

It does not perform speech recognition, raw note cleanup, or Jira status backfill; the Processing Result column remains blank. If terms are missing from the glossary, suspected transcription errors, or ownership is unclear, it asks the minimum necessary questions. Corrections are written as wrong term -> correct term and only persisted when the user explicitly confirms.