ワンクリックでManusで任意のスキルを実行

generate-stakeholder-map

スター5

フォーク0

更新日2026年4月15日 18:22

Generates a structured stakeholder map for IT project management (Phase 1 — Initiation). Reads available project files (client questionnaire, project charter, team list), extracts stakeholder data, and produces a stakeholder-map.md file with a summary table and narrative blocks per stakeholder. Triggers RU: «создай карту стейкхолдеров», «сформируй карту стейкхолдеров», «идентифицируй стейкхолдеров», «подготовь карту заинтересованных сторон», «кто стейкхолдеры проекта». Triggers EN: 'generate stakeholder map', 'create stakeholder map', 'identify stakeholders', 'stakeholder analysis', 'map project stakeholders', 'who are the stakeholders'.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

KirKruglov

KirKruglov/claude-project-manager

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

関連職種SOC

SOC 職業分類に基づく

プロジェクト管理専門家ビジネス・金融業務職·SOC 13-1082

ファイルエクスプローラー

3 ファイル

SKILL.md

readonly

このリポジトリの他の Skills

同じリポジトリ

coordinate-executors

KirKruglov/claude-project-manager

Sends deadline reminder emails to task executors for overdue or approaching-deadline tasks. Checks Jira (or project-plan.md as fallback) for tasks with deadlines within 2 business days or already overdue, groups them by assignee, and sends personalized reminders via Gmail — autonomy level 1 (no PM confirmation required). Covers project tasks #13 (Phase 3, prototyping) and #23 (Phase 5, launch/marketing). Runs as a scheduled task (Mon–Fri, 10:00) or on demand via /remind-executors. Triggers RU: «напомни исполнителям», «проверь дедлайны», «coordinate-executors», «кто просрочил задачи», «отправь напоминания команде», «какие задачи горят», «напоминания о дедлайнах», «проверь просроченные задачи». Triggers EN: 'remind executors', 'check deadlines', 'send deadline reminders', 'who has overdue tasks', 'executor reminders', 'task reminders', 'overdue tasks', 'remind the team about deadlines', 'coordinate executors', 'deadline check'.

2026-04-155

coordinate-meeting

KirKruglov/claude-project-manager

Coordinates project meetings: generates a structured agenda, creates a Google Calendar event, and prepares a protocol template. Covers 5 meeting types across the full project lifecycle — tasks #6, #15, #17, #20, #26. Meeting types: Go/No-Go (Phase 1, #6), Client Demo (Phase 3, #15), Sprint Planning (Phase 4, #17), Sprint Demo (Phase 4, #20), Launch Status Meeting (Phase 5, #26). Reads project context files (stakeholder-map, project-plan, progress reports) to auto-populate participants and agenda topics. Mode B: agent prepares a draft agenda, PM confirms before the Calendar event is created. Triggers EN: 'coordinate meeting', 'prepare agenda', 'schedule meeting'.

2026-04-155

generate-approval-letter

KirKruglov/claude-project-manager

Generates an approval-letter.md email body and an email-tpl-approval.md template for Phase 2 — Planning. Reads project-plan.md, project-budget.xlsx, and resource-plan.md to compose a formal approval request addressed to all Approver-level stakeholders from stakeholder-map.md. Produces two artifacts: the letter email body (approval-letter.md) and the send-email template (email-tpl-approval.md). Covers task #12 of the project management agent. Mode B: agent prepares draft, PM reviews and confirms before sending. Email level 3 — requires PM confirmation. Triggers RU: «отправь план на согласование», «письмо на согласование плана», «согласуй план с заказчиком», «запроси утверждение плана», «generate-approval-letter», «составь письмо на согласование». Triggers EN: 'send plan for approval', 'approval letter for project plan', 'request plan approval', 'generate approval letter', 'plan sign-off email', 'get plan approved'.

2026-04-155

generate-budget

KirKruglov/claude-project-manager

Generates a detailed project budget (project-budget.xlsx) for Phase 2 — Planning, based on preliminary-estimate.xlsx and resource-plan.md. Produces a single baseline scenario structured by project phases and cost categories (team, infrastructure, GTM), with a contingency reserve as a separate line item. Covers task #9 of the project management agent. Mode B: agent prepares draft, PM reviews and approves. Triggers RU: «сформируй бюджет проекта», «подготовь детальный бюджет», «сделай бюджет по фазам», «бюджет проекта», «детализируй бюджет». Triggers EN: 'generate project budget', 'create budget', 'project budget', 'detailed budget', 'budget by phase', 'budget breakdown'.

2026-04-155

generate-change-impact

KirKruglov/claude-project-manager

Generates a change impact assessment file (change-impact-CR-001.xlsx) for Phase 4 — Development. PM describes a scope change request; the agent classifies the change (scope / budget / timeline / resource), analyzes impact on project-plan.md and project-budget.xlsx, calculates timeline delta, budget delta, and risk level (Low / Medium / High), then produces a two-sheet xlsx artifact with a summary and detailed breakdown. PM reviews the draft and makes the final approval decision. Covers task #21 of the project management agent. Mode B: agent prepares draft, PM decides. If approved — updates project-plan.md via generate-project-plan. Triggers EN: 'scope change request', 'change impact assessment', 'generate change impact'.

2026-04-155

generate-charter

KirKruglov/claude-project-manager

Generates a project charter from brief, stakeholder answers, and constraints. The charter is the first artifact of the Initiation phase. Once approved, it unlocks dependent tasks: generate-risk-register, generate-project-plan, generate-estimate. Accepts both structured briefs and free-form notes. Triggers RU: «сформируй устав», «подготовь устав проекта», «создай устав», «нужен устав проекта», «составь устав проекта», «устав проекта», «generate-charter», «сформируй charter». Triggers EN: 'generate charter', 'create project charter', 'build charter', 'draft project charter'.

2026-04-155

name

generate-stakeholder-map

description

Skill: generate-stakeholder-map

Generates a stakeholder map for IT projects (Phase 1 — Initiation). Reads available project files, extracts stakeholder data, and produces a structured stakeholder-map.md with a summary table and narrative blocks per stakeholder.

Triggers

Russian: «создай карту стейкхолдеров», «сформируй карту стейкхолдеров», «идентифицируй стейкхолдеров», «подготовь карту заинтересованных сторон», «кто стейкхолдеры проекта», «нужна карта стейкхолдеров» English: "generate stakeholder map", "create stakeholder map", "identify stakeholders", "stakeholder analysis", "map project stakeholders", "who are the stakeholders"

Language Detection

Determine the language of the user's request:

If the request is in Russian → use templates with the -ru suffix
Otherwise → use templates with the -en suffix
All output (headings, labels, agent messages) must match the detected language.

Input

Data	Required	Source	Notes
Client answers	no	`01-initiation/questionnaire-client.md`	Primary source: Block 5 + stakeholder mentions throughout
Project charter	no	`01-initiation/project-charter.md`	Secondary source (artifact from generate-charter MVP skill)
Team list	no	`input/team-list.md`	Org structure, roles, contacts
Manual input	no	Chat	If no files found — request data directly

If none of the files is available — ask a clarifying question (see Step 1).

Output

File	Project path	Mode
`stakeholder-map.md`	`01-initiation/`	generate

Instructions

Step 1 — Locate Available Data Sources

Before checking files: if the request includes tasks outside this skill's scope (generating a communications plan, contacting stakeholders, creating a risk register, etc.) — complete the stakeholder map first, then explicitly note at the end of Step 4: "[Task X] is outside this skill's scope. Use [relevant skill] for that." Do not attempt to perform out-of-scope tasks.

Check for files in the following order:

01-initiation/questionnaire-client.md
01-initiation/project-charter.md
input/team-list.md

If the user's message already contains stakeholder data (names, roles, influence/interest levels) — skip the A/B prompt and proceed directly to Step 2.

If none of the files exist AND no inline data is provided — show in chat:

No project input files found. Stakeholder data is needed to create the map.
Choose an option:
A) Provide a path to a file with stakeholder data
B) Enter data directly: name, role, influence level, and interest for each stakeholder

Wait for user response. Do not proceed without data.

Step 2 — Extract Stakeholder Data

Read available files and extract the following per stakeholder:

Field	Sources	Priority
Name	questionnaire-client.md Block 5, project-charter.md	questionnaire > charter
Role / Title	questionnaire-client.md, team-list.md	questionnaire > team-list
Organization	questionnaire-client.md	—
Category	Determine independently (see list below)	—
Influence level	Infer from context	—
Interest level	Infer from context	—
Contact / Email	questionnaire-client.md, team-list.md	—
Interests and expectations	questionnaire-client.md Block 5, Block 2	—
Concerns and risks	questionnaire-client.md Block 4	—
Communication frequency	questionnaire-client.md Q20 equivalent	—

Stakeholder categories:

Sponsor
Client
Project Team
Decision Maker
External User
Pilot Client
Consultant / Regulator

Influence and interest levels: High / Medium / Low.

Power/Interest quadrant — determine automatically:

High Power + High Interest → Manage Closely
High Power + Low Interest → Keep Satisfied
Low Power + High Interest → Keep Informed
Low Power + Low Interest → Monitor
Medium Power + High Interest → Keep Informed
Medium Power + Low Interest → Monitor (Treat Medium as the lower tier for quadrant assignment.)

If data for a field is insufficient:

Mark [clarify] in the corresponding table cell (e.g., the Contact column) AND in the narrative block.
Add a row to Section 5 (Open Questions) with: the missing field description, the stakeholder name, Status = Open.

Step 3 — Generate the Stakeholder Map

Determine language → select template stakeholder-map-{lang}.md.
Fill in metadata:

Placeholder	Source
`{{project_name}}`	Project CLAUDE.md or user request
`{{pm_name}}`	CLAUDE.md (if available)
`{{date}}`	Current date (YYYY-MM-DD)
`{{version}}`	`1.0`

Fill in the summary stakeholder table — one row per stakeholder.
Fill in the narrative block per stakeholder (role, expectations, concerns, strategy, frequency).
If there are more than 15 stakeholders — group minor ones (Monitor quadrant) into a single entry "Other Interested Parties".

Step 4 — Save and Report

Save file: 01-initiation/stakeholder-map.md.
Show in chat:
- What was created: "Stakeholder map saved as [filename] in [path]."
- Number of stakeholders, quadrant distribution
- If Section 5 has rows — list them: "Open questions requiring clarification: [list]."
- Next step: "Stakeholder map ready. Suggested next steps: generate-risk-register (risk register) or generate-comm-plan (communications plan — after project plan is approved)."
- If the original request included out-of-scope tasks — note each one explicitly: "[Task X] is outside this skill's scope. Use [relevant skill] for that."
Log to logs/log.md: date, skill, created file, number of stakeholders.

Templates

File	Purpose
`templates/stakeholder-map-ru.md`	Artifact template (RU)
`templates/stakeholder-map-en.md`	Artifact template (EN)

Dependencies

Reads:

01-initiation/questionnaire-client.md — primary source (from generate-questionnaire)
01-initiation/project-charter.md — secondary source (from generate-charter, MVP)
input/team-list.md — org structure

Passes data to:

generate-comm-plan — communications plan is built on the stakeholder map
coordinate-meeting — attendee lists for meetings
generate-approval-letter — approval addressees

Constraints

Mode B: agent prepares a draft, human reviews and approves
Does not send communications to stakeholders — that is the task of generate-comm-plan and send-email
Does not generate a communications plan — only the stakeholder map
No Miro integration (MCP does not exist as of April 2026)
Handles one project per invocation
If stakeholder data is insufficient — marks [clarify], does not fabricate
Maximum 15 stakeholders in detailed blocks; additional ones grouped as "Other Interested Parties"

Changelog

Date	Version	Change
2026-04-06	1.0	Skill created. Three data sources: questionnaire-client, project-charter, team-list. Template: table + narrative blocks. No Miro.
2026-04-06	1.1	Post-eval fixes (3/6 → 6/6 expected): added inline-data detection in Step 1 (skip A/B when data provided); added Medium Power quadrant rules; added [clarify] to Contact column + Section 5 auto-fill; added out-of-scope guard rail in Steps 1 and 4; added Section 5 open questions reporting.