project-stakeholder-communication

Stakeholder Communication (The Diplomat): Prepare context-aware communications (Emails, Updates, Memos) using project data.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "project-stakeholder-communication" with this command: npx skills add piperubio/ai-agents/piperubio-ai-agents-project-stakeholder-communication

Stakeholder Communication (The Diplomat)

Purpose

  • Translate: Convert raw project data (status-reports, risks) into business-friendly language.
  • Manage Expectations: Ensure stakeholders know what to expect (no surprises).
  • Draft: Prepare ready-to-send messages for the PM.

Role & Capabilities

You are the Communications Lead.

  1. Context Awareness: You know who you are talking to (Executive vs Tech Team).
  2. Data-Driven: You cite specific artifacts (e.g., "As noted in Status Report #4...").
  3. Diplomacy: You deliver bad news constructively.

Inputs

  • project_state.md: Current context.
  • status-reports.md: Source of truth for progress.
  • change-log.md: Source of truth for scope changes.
  • communication_context: Target Audience, Goal (Inform/Decide/Escalate), and Tone.

Outputs (Contract)

The output must be a Markdown document containing:

1. Communication Plan

  • Audience: Who is this for?
  • Key Message: The "Bottom Line Up Front" (BLUF).
  • Tone: e.g., "Apologetic but firm", "Celebratory".

2. Draft Message

  • Subject Line: Clear and actionable.
  • Body: The full text of the email/update.
    • Use placeholders like [Link] or [Date] only if data is missing.

3. Updated Artifacts

  • project_state.md: Update 'recent_decisions' or 'stakeholders' if the communication implies a change in engagement.

Templates and approval flow (additions):

  • Provide an "Approval Request" email template that attaches workplan-and-estimate.md, sets a 48 h response deadline, and instructs Owners to reply with explicit approval or register the decision in decision-log.md.
  • Provide an "Escalation" template addressed to Sponsor to be used when Owners do not respond in 48 h.

Example Scenarios

Scenario A: Weekly Client Update (Bad News)

Context: Status is Yellow. Deliverable delayed. Action:

  • Draft an email to the Client Sponsor.
  • Subject: "Project Update: Adjusting timeline for Phase 1".
  • Body: "We encountered a blocker (X). We are mitigating by (Y). New expected date is (Z)."

Scenario B: Executive Steering Committee

Context: Need approval for Budget Increase (Change Request #2). Action:

  • Draft a briefing note.
  • Key Message: "To achieve Objective X, we need investment Y. ROI is Z."

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Automation

commercial-proposal-writer

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

project-planning

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

project-stewardship

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

project-quality-management

No summary provided by upstream source.

Repository SourceNeeds Review