From project-manager
Generates a communication plan from project charter, project plan, and stakeholder data. Includes stakeholder matrix (influence/interest), communication matrix, and escalation rules. Phase 2 artifact. In MVP stakeholders are extracted from charter; in P1 — from stakeholder-map.md. Triggers RU: «сформируй план коммуникаций», «подготовь comm-plan», «кому и как коммуницировать», «план коммуникаций», «создай план коммуникаций», «матрица стейкхолдеров», «generate-comm-plan», «коммуникационный план». Triggers EN: 'generate comm plan', 'create communication plan', 'build comm plan', 'stakeholder communication plan', 'comm plan'.
npx claudepluginhub kirkruglov/claude-project-managerThis skill uses the workspace's default tool permissions.
**Russian:** «сформируй план коммуникаций», «подготовь comm-plan», «кому и как коммуницировать»
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
Russian: «сформируй план коммуникаций», «подготовь comm-plan», «кому и как коммуницировать» English: "generate comm plan", "create communication plan", "build comm plan"
Determine the language of the user's request:
-ru suffix-en suffixAll output (headings, labels, comments, instructions) must match the detected language.
| 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 the project plan. Recommend running generate-project-plan first."
Preliminary stakeholder list (extracted from charter):
| ID | Role | Name | Influence | Interest | Strategy |
[table]
Assumption: influence/interest ratings assigned by agent based on role and context.
Supplement or correct the list — after confirmation I will generate the full plan.
comm-plan.md from project knowledge.S01, S02, ... — sequential numbering.Influence/Interest matrix → strategy:
| Influence \ Interest | High | Medium | Low |
|---|---|---|---|
| High | Manage actively | Manage actively | Keep satisfied |
| Medium | Keep informed | Keep informed | Monitor |
| Low | Keep informed | Monitor | Monitor |
Rating scale:
| Level | Influence (description) | Interest (description) |
|---|---|---|
| H (High) | Makes key decisions, controls budget, can block the project | Actively participates, invested in outcomes, regularly requests status |
| M (Medium) | Influences specific areas (technical decisions, resources), does not block | Interested in certain aspects, periodically involved |
| L (Low) | Does not influence project decisions, executes tasks | Minimal interest, engaged on request |
C01, C02, ... — sequential numbering.Mandatory minimum communications:
| Type | Audience | Default Frequency |
|---|---|---|
| Sponsor status report | Sponsor (+ Client) | Weekly |
| Sprint/iteration planning | Team | On event (sprint start) |
| Sprint demo/review | Sponsor, Client, Tech Lead | On event (sprint end) |
| Escalation (critical issues) | Sponsor | On event |
Additional communications — per context: client sync, external stakeholder alignment, financial report, customer updates.
Reference values:
| Column | Allowed values |
|---|---|
| Format | Meeting, Report, Notification, Presentation, Letter |
| Channel | Email, Meeting (online), Meeting (offline), Chat, Meeting (online/offline) |
| Frequency | Daily, Weekly, Bi-weekly, Monthly, On event, On demand, One-time |
| Artifact | Filename from the system: weekly-status.md, meeting-protocol-{date}.md, progress-report-{date}.md, deviation-report-{date}.md or — if no artifact is produced |
Version: 1.0Date: current generation date.File: comm-plan.mdDocument status: draft (at generation). After approval — approved.Source: list the files used as input.Placeholders
{{}}in the template are fill-in guides, not auto-substitution variables. Replace each with the corresponding value from the input data.
| Placeholder | Required | Source | Allowed values |
|---|---|---|---|
{{project_name}} | yes | charter | text |
{{version}} | yes | agent | 1.0 on creation |
{{date}} | yes | system | YYYY-MM-DD |
{{source_docs}} | yes | agent | list of source files |
{{role}} | yes (≥3) | charter / user data | functional role |
{{name}} | yes (≥3) | charter / user data | name / position |
{{strategy}} | yes (≥3) | agent (per matrix §3) | Manage actively, Keep informed, Keep satisfied, Monitor |
{{comm_name}} | yes (≥4) | agent | communication name |
{{format}} | yes | agent | see reference §3 section 2 |
{{channel}} | yes | agent / user data | see reference §3 section 2 |
{{frequency}} | yes | agent | see reference §3 section 2 |
{{owner}} | yes | charter / user data | name of responsible person |
{{artifact}} | no | agent | system filename or — |
{{threshold}} | yes (≥3) | project data / assumption | numeric threshold + unit |
{{stakeholder_id}} | yes (≥3) | section 1 | S01, S02, ... |
{{deadline}} | yes (≥3) | agent | response time (hours/days) |
Before showing result to user — verify:
{{}} placeholders remaining in textdraftConsumes (input):
project-charter.md — project charter (skill generate-charter)project-plan.md — project plan (skill generate-project-plan)stakeholder-map.md — stakeholder map (skill generate-stakeholder-map)Produces (output): communication plan → consumed by (system-prompt-draft.md §7):
send-email (module) — defines recipients and mailing frequency (P1)After plan approval, the user must upload comm-plan.md to project knowledge.
User command:
Сформируй план коммуникаций. Устав и план проекта — в knowledge.
Agent response (step 4 — preliminary list):
Stakeholders extracted from charter:
ID Role Name Influence Interest Strategy S01 Sponsor Алексей Воронов, CEO H H Manage actively S02 Client Елена Морозова, Head of CS H H Manage actively S03 PM Кирилл Ругалёв M H Keep informed Assumption: influence/interest ratings assigned based on roles. Supplement the list or correct the ratings.
After approval (step 11):
Communication plan "ClientBoard" generated based on: project-charter.md, project-plan.md.
Assumptions:
- Stakeholder influence/interest ratings assigned by agent based on roles.
- Budget escalation threshold: >10% of total (not specified in charter).
- Communication channels: Email + online meetings (preferences not specified).
Required: approve, provide feedback, or reject.
[plan text]
| Date | Version | Change |
|---|---|---|
| 2026-03-26 | 1.0 | Skill created. Hybrid stakeholder model (extraction + clarification). Mandatory minimum of 4 communications. Reference values dictionary. Table of 16 placeholders |