generate-closure-report

# generate-closure-report ## Triggers **Russian:** «сформируй отчёт о закрытии», «закрой проект», «подготовь closure report», «отчёт о закрытии проекта» **English:** "generate closure report", "close project", "project closure report", "prepare closure report" ## 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 | |------|:--------:|--------|-------| | Project charter | yes | knowledge (`project-charter.md`) | Goal, deliverables, team, sponsor, budget, timeline | | Plan-fact report | yes | knowledge (`plan-fact-report.md`) | Deviation summary, actual dates/budget/scope. If multiple files — use the latest by date | | Lessons learned | yes | chat | User provides in any format: retrospective results, questionnaire answers, free text. Agent structures and assigns categories | | Risk register | no | knowledge (`risk-register.md`) | For section 4. If unavailable — agent asks the user about realized risks | | Open items | no | chat | Tasks/questions remaining after closure. If not provided — replace section with "All items closed" | | Lessons source | no | chat | `team retrospective` / `questionnaire` / `PM input in chat`. Default: `PM input in chat` | If required data is missing — request it (system-prompt-d...