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'.

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'.

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'.

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'.

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'.

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'.

Generates project management checklists for Phase 5 (Launch) and Phase 6 (Closure): launch readiness checklist (launch-checklist.md), technical readiness checklist (tech-readiness-checklist.md), and handover-to-operations checklist (handover-checklist.md). Covers tasks #22, #24, and #32 of the project management agent. Mode B: agent pre-populates base items from PMBoK-aligned templates and enriches with data from project-plan.md if available; PM reviews and finalizes. Checklist type is inferred from context; if ambiguous, agent asks. Triggers EN: 'launch checklist', 'tech readiness checklist', 'handover checklist'.

Generates a project closure report aggregating data from charter, plan-fact report, risk register, and lessons learned. Last artifact of the Closing phase. Summarizes project outcomes, deviations, realized risks, and lessons. Triggers RU: «сформируй отчёт о закрытии», «закрой проект», «подготовь closure report», «отчёт о закрытии проекта». Triggers EN: 'generate closure report', 'close project', 'project closure report', 'prepare closure report'.

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'.

Generates a prototype comparison table (comparison-table.xlsx) for Phase 3 — Prototyping. PM describes 2–4 prototypes in chat; the agent structures evaluation criteria (standard set: technical feasibility, UX quality, cost, timeline, risk), proposes weights (customisable by PM), scores each prototype on a 1–5 scale, calculates weighted totals and provides a recommendation. Output: two-sheet xlsx file with a summary and a detailed scoring matrix. PM reviews the draft and makes the final selection decision. Covers task #14 of the project management agent. Mode B: agent prepares draft, PM decides. Triggers EN: 'compare prototypes', 'prototype comparison table', 'evaluate prototype options'.

Generates a preliminary timeline and budget estimate for an IT project (Phase 1 — Initiation). Reads available project files (client questionnaire, project charter, constraints, team list), applies analogy-based estimation using built-in agent knowledge of typical IT projects, and produces a three-scenario (optimistic / realistic / pessimistic) preliminary-estimate.xlsx artifact. Covers task #4 of the project management agent. Mode B: agent prepares draft, PM reviews and corrects. Triggers RU: «сформируй оценку сроков», «подготовь предварительную оценку бюджета», «оцени сроки проекта», «сделай оценку по аналогам», «предварительная оценка». Triggers EN: 'generate estimate', 'preliminary estimate', 'estimate timeline and budget', 'create project estimate', 'ballpark estimate'.

Generates a meeting protocol from free-form notes. Extracts decisions, action items, and plan changes. If project plan is available — links changes to WP-xxx/Mx IDs. Phase 3 artifact, but usable in any phase. Independent skill with no upstream dependencies. Triggers RU: «оформи протокол», «протокол встречи», «обработай заметки со встречи», «generate-meeting-protocol». Triggers EN: 'generate meeting protocol', 'meeting notes', 'meeting minutes', 'meeting protocol'.

Generates a plan-vs-actual report comparing planned and actual project data across three dimensions: timelines, budget, and scope (deliverables). Part of the Closing phase. Output feeds into generate-closure-report. Format: .md, manual data input via chat. Triggers RU: «сформируй план-факт», «подготовь отчёт план/факт», «сравни план и факт». Triggers EN: 'generate plan-fact report', 'plan vs actual', 'variance report'.

Generates a project plan from the approved charter, scope, and optional duration/resource estimates. The plan is the first artifact of the Planning phase. Once approved, it unlocks: generate-risk-register (mode: detailed) and generate-comm-plan (can run in parallel). Accepts both structured estimates and free-form descriptions. Triggers RU: «сформируй план проекта», «подготовь план», «составь project plan», «нужен план проекта». Triggers EN: 'generate project plan', 'create project plan', 'build plan', 'prepare project plan'.

Generates structured questionnaires for IT project management: a client requirements questionnaire (Phase 1 — Initiation) and a lessons-learned questionnaire for the team (Phase 6 — Closure). Also structures received answers for downstream skills. Triggers RU: «сформируй опросник», «подготовь опросник для заказчика», «создай бриф заказчику», «подготовь анкету по урокам», «структурируй ответы заказчика». Triggers EN: 'generate questionnaire', 'create client brief', 'prepare lessons questionnaire', 'structure stakeholder answers', 'prepare project brief'.

Generates a resource allocation plan (resource-plan.md) for Phase 2 — Planning, based on project-plan.md and team-list.md. Produces a role-by-phase FTE matrix with person-month calculations, rates (when available), external resources section, and a phase-load summary. Covers task #8 of the project management agent. Mode B: agent prepares draft, PM reviews and approves. Required input for generate-budget (#9). Triggers RU: «составь ресурсный план», «распредели ресурсы по проекту», «кто и когда работает», «ресурсный план проекта», «загрузка команды по фазам», «generate-resource-plan». Triggers EN: 'generate resource plan', 'resource allocation plan', 'create resource plan', 'team allocation by phase', 'staffing plan', 'who works when'.

Generates an incident response plan (response-plan-{id}.md) for Phase 5 — Launch. Covers task #27 of the project management agent. Handles mixed incident types: Technical (system failures, critical bugs, infrastructure), Operational (deployment failures, process breakdowns), and Business (KPI collapse, PR crises, legal issues). Classifies severity (Critical / High / Medium / Low) from PM description; enriches the plan with team and stakeholder data from project files. The plan includes: incident description, impact assessment, response team, root cause analysis, action plan with owners, resolution timeline, escalation path, communication plan, and post-incident tasks. Mode B: agent prepares draft, PM reviews and approves. Triggers EN: 'incident response plan', 'incident occurred', 'system down'.

Generates a risk register from project charter (initial mode) or enriches it with project plan data (detailed mode). Two modes: initial — phase 1 after charter approval; detailed — phase 2 after project plan approval. Triggers RU: «сформируй реестр рисков», «подготовь risk register», «обнови реестр рисков», «создай реестр рисков». Triggers EN: 'generate risk register', 'create risk register', 'update risk register'.

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'.

Monitors project progress across 6 operational modes: sprint progress report, deviation check (schedule vs budget), launch stream synchronization, actual data collection for project closure, weekly status report (scheduled), and daily deviation check (scheduled). Reads project-plan, project-budget, and Jira data to produce structured reports. Triggers email notifications via send-email for deviations (level 2 draft) and weekly status (level 1 autonomous). Falls back to file-only output if Jira MCP is unavailable. Covers PM tasks #18, #19, #25, #28 and scheduled tasks weekly-status (Р1) and daily-deviation (Р2). Triggers EN: 'check progress', 'project status', 'weekly report'.

Internal service skill for delivering project emails via Gmail MCP. Activated automatically when any project management skill needs to send an email: deadline reminders (E6), weekly status reports (E7), approval requests (E3), client questionnaires (E1), deviation alerts (E4, E5), or meeting notifications (E8). Handles three autonomy levels: Level 1 sends immediately without confirmation, Level 2 sends with PM copied, Level 3 shows a draft and waits for PM approval. Converts .md attachments to .docx for external recipients using the Cowork docx skill. Falls back to a saved .md draft when Gmail is unavailable. Not triggered directly by users — activated by other agent skills passing email_type, recipients, body, and autonomy_level. RU triggers (from calling skills): 'отправить письмо', 'send-email', 'уведомить стейкхолдеров'. EN triggers: 'send email', 'notify stakeholders', 'deliver report'.