From 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'.
npx claudepluginhub kirkruglov/claude-project-managerThis skill uses the workspace's default tool permissions.
Sends personalized deadline reminder emails to task executors.
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.
Sends personalized deadline reminder emails to task executors. Checks Jira for overdue or approaching-deadline tasks, groups by assignee, and sends emails via Gmail at autonomy level 1 (no confirmation needed). Runs daily as a scheduled task or on demand.
Russian: «напомни исполнителям», «проверь дедлайны», «отправь напоминания», «кто просрочил задачи», «какие задачи горят», «проверь просроченные» English: "remind executors", "check deadlines", "send deadline reminders", "overdue tasks", "remind the team", "coordinator reminders"
language field from project-state.md → use that value (RU or EN)email-tpl-reminder-deadline-ru.mdemail-tpl-reminder-deadline-en.md| Data | Required | Source |
|---|---|---|
| Tasks with deadlines and assignees | yes | Jira MCP (primary) or 02-planning/project-plan.md (fallback) |
| Reminder horizon | no | Default ≤ 2 business days; configurable via project-state.md → reminder_horizon_days |
| Executor contacts | no | 01-initiation/stakeholder-map.md or Jira profiles |
| Project name, current phase | no | project-state.md |
| File / Action | Path | Condition |
|---|---|---|
| Deadline reminder email | — (Gmail, external) | Tasks with deadline ≤ 2 days or overdue |
reminders-{YYYY-MM-DD}.md | reports/ | Fallback: Gmail unavailable |
| Log entry | logs/log.md | Always |
| State update | project-state.md | When reminders are sent |
If the request is about team management theory, HR practices, or motivation (not about specific project task deadlines) → respond: "coordinate-executors sends deadline reminders to task assignees. Tell me which tasks or project phase to check." Do not start the workflow.
Determine run mode:
Read project-state.md → project name, current phase, sprint, PM name,
reminder_horizon_days (default: 2 if not set).
Primary path (Jira available): Query tasks with filter:
dueDate ≤ today + reminder_horizon_days (business days) OR dueDate < todayGroup results by assignee.
Fallback (Jira unavailable):
Read 02-planning/project-plan.md. Extract tasks for the current phase with
fields: task name, owner, deadline, status.
Apply the same filter: deadline ≤ today + horizon OR overdue.
Notify PM in chat: "Jira unavailable. Data loaded from project-plan.md."
If no qualifying tasks found:
logs/log.md:
{DATE}: coordinate-executors — check complete, no overdue or approaching tasksFor each executor with qualifying tasks:
Split tasks into two lists:
dueDate < today (include days overdue)dueDate = today or today + 1–{horizon} days (include days remaining)Load the E6 template matching the project language:
templates/email-tpl-reminder-deadline-en.mdtemplates/email-tpl-reminder-deadline-ru.mdPopulate the template:
{EXECUTOR_NAME} — assignee name{PROJECT_NAME} — from project-state.md{OVERDUE_TASKS} — table: task name | due date | days overdue{UPCOMING_TASKS} — table: task name | due date | days remaining{PM_NAME} — from project-state.md (or placeholder)Resolve executor email:
01-initiation/stakeholder-map.md (primary)Primary path (Gmail available): For each executor:
send-email skill with autonomy level 1 (auto-send)Fallback (Gmail unavailable):
Create reports/reminders-{YYYY-MM-DD}.md. For each executor — one section using the E6 template structure:
## {EXECUTOR_NAME} <{EXECUTOR_EMAIL}>Notify PM: "Gmail unavailable. Reminder drafts saved to reports/reminders-{DATE}.md — send manually."
Write to logs/log.md:
{DATE}: coordinate-executors — {N} reminders sent ({EXECUTOR_LIST}){DATE}: coordinate-executors — fallback, saved reports/reminders-{DATE}.mdUpdate project-state.md: set last_reminder_check to today's date.
Output summary to chat:
| File | Purpose |
|---|---|
templates/email-tpl-reminder-deadline-en.md | Email template E6 — deadline reminder (EN) |
templates/email-tpl-reminder-deadline-ru.md | Email template E6 — deadline reminder (RU) |
Reads (optional):
project-state.md — project name, phase, PM, horizon setting01-initiation/stakeholder-map.md — executor contacts02-planning/project-plan.md — task list (Jira fallback)External actions:
send-email — sending reminders (primary)Passes data to:
send-email — email body, recipient, autonomy levelproject-state.md → log error and exit