mirror of
https://gitlab.rlp.net/proj-wise2526-video2document/video2document.git
synced 2026-06-15 18:01:52 +02:00
Delete meeting_report_best_practices.md
This commit is contained in:
parent
b157a90671
commit
10e3c902c5
@@ -1,42 +0,0 @@
|
||||
# Best Practices for High-Quality Meeting Reports
|
||||
|
||||
## 1. Tone & Style
|
||||
- Neutral, concise, factual
|
||||
- No personal opinions
|
||||
- Use consistent timestamps (HH:MM:SS)
|
||||
|
||||
## 2. Structure
|
||||
- Start with a clear title page
|
||||
- Include agenda, summary, decisions, and actions
|
||||
- Sections must follow chronological order
|
||||
|
||||
## 3. Executive Summary
|
||||
- 2–3 short sentences
|
||||
- Should give a quick understanding of the meeting’s outcome
|
||||
|
||||
## 4. Key Points
|
||||
- Max. 5 bullet points per section
|
||||
- Use speaker labels if known
|
||||
|
||||
## 5. Decisions
|
||||
- Every decision must have:
|
||||
- Text
|
||||
- Responsible person (owner)
|
||||
- Due date
|
||||
|
||||
## 6. Action Items
|
||||
- Should be structured in a table:
|
||||
- ID
|
||||
- Task
|
||||
- Owner
|
||||
- Due date
|
||||
- Status
|
||||
|
||||
## 7. Handling Missing Information
|
||||
- If unclear → use UNKLAR:<reason>
|
||||
- If timestamps missing → estimate minimal timestamps
|
||||
|
||||
## 8. Output Format
|
||||
- Markdown
|
||||
- Clean sections
|
||||
- No meta comments from the LLM
|
||||
Reference in New Issue
Block a user