generate-comm-planlisted

# generate-comm-plan ## Triggers **Russian:** «сформируй план коммуникаций», «подготовь comm-plan», «кому и как коммуницировать» **English:** "generate comm plan", "create communication plan", "build comm plan" ## 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. Inputs | Data | Required | Source | Notes | |------|:--------:|--------|-------| | Project charter | yes | knowledge or chat | Source of stakeholders (section 5 "Team and Roles"), goals, scope, constraints | | Project plan | yes | knowledge or chat | Source of milestones, phases, work blocks — for binding communications to events | | Stakeholder data | no | chat or knowledge | Additional stakeholders not listed in the charter. In P1 — `stakeholder-map.md` | | Channel preferences | no | chat | Communication channels used by the team (Slack, Teams, Email, Meets, etc.) | If required data is missing — request it (system-prompt-draft.md §3.2): ``` To generate the communication plan, the following are needed: — Project charter (project-charter.md) — source of team, goals, constraints — Project plan (project-plan.md) — source of milestones and phases Available: [list what is present]. Missing: [be specific]. ``` If the project plan does not yet exist — respond: "The communication plan depends on th