generate-meeting-protocollisted

# generate-meeting-protocol ## Triggers **Russian:** «оформи протокол», «протокол встречи», «обработай заметки со встречи» **English:** "generate meeting protocol", "meeting notes", "meeting minutes" --- ## Language Detection Determine the language of the user's request: - If the request is in Russian → use templates with `-ru` suffix - Otherwise → use templates with `-en` suffix All output (headings, labels, comments, instructions) must match the detected language. --- ## 1. Input Data | Data | Required | Source | Notes | |------|:--------:|--------|-------| | Meeting notes | yes | chat or knowledge | Any format: bullet points, free text, chat copy, voice dictation. Agent structures the content independently | | Project plan | no | knowledge | If available — agent links changes to plan element IDs (WP-xxx, Mx). If not — describes changes as text | | Meeting context | no | chat | Meeting type, participants, date — if not included in the notes | If required data is missing — request it (system-prompt-draft.md §3 p.2): ``` To generate a protocol, meeting notes are required — in any format: bullet points, free text, chat copy, voice dictation (as text). Minimum to start: what was discussed and what decisions/tasks were recorded. Available data: [list what is available]. Missing: [specify]. ``` --- ## 2. Execution Algorithm 1. **Validate input data.** Check if notes are present. If not → request using the template from §1. Do NOT generate a placeholder protocol — re