القائمة
Craft clear, concise stakeholder communications with appropriate context and framing
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Generate Mermaid architecture diagrams showing system components, layers, and data flows
Proactively identify at-risk issues and PRs: stale items, blocked work, deadline risks, scope creep, and unassigned high-priority items
Extract common questions from closed GitHub issues and generate an FAQ document with answers
Search project notes by topic, synthesize findings into a consolidated summary with cross-references
Proactively identify information gaps in project context and generate actionable questions to surface missing requirements, unclear specifications, or documentation gaps
Generate Mermaid dependency graphs showing issue relationships, blocking chains, and critical paths
استنادا إلى تصنيف SOC المهني
| name | stakeholder-updates |
| description | Craft clear, concise stakeholder communications with appropriate context and framing |
| instructions | When writing status updates, communicating delays, sharing launch announcements, or crafting stakeholder communications |
| tags | ["communication","stakeholders","updates","reporting"] |
| allowed_tools | ["github","notes","search_notes"] |
This skill helps craft effective communications for stakeholders at various levels.
Activate this skill when:
Executives (C-level):
Management (Directors, VPs):
Peers (Other PMs, Team Leads):
Team Members:
Subject/Title: [Concise summary of current state]
TL;DR: (1-2 sentences) Current status in plain language with key takeaway
Progress This Week:
Metrics/Impact:
Blockers/Risks:
Decisions Needed:
Next Milestones:
Subject: Payment Flow Redesign - Live with 23% Conversion Lift
TL;DR: New checkout launched Tuesday. Conversion up 23%, support tickets down 15%. Monitoring for issues.
Impact:
What's Next: Rolling out to mobile apps next week. Full metrics report Friday.
FYI: Minor bug in Safari addressed Wednesday. No customer impact.
Subject: Q2 Mobile Release - Timeline Update
Context: We've hit an integration blocker with the third-party payment SDK that requires vendor support.
Impact:
What Happened: The SDK update (required for PCI compliance) introduced breaking changes to the refund flow. Vendor confirmed this is a known issue and they're releasing a patch.
Mitigation:
What I Need:
Lessons: Adding "SDK update review" step to our release checklist to catch this earlier next time.
❌ "We've been working on improving the checkout flow and after several iterations and testing..." ✅ "Checkout conversion is up 23% since Tuesday's launch."
Every statement should answer: "Why does this matter?"
❌ "We added a progress indicator" ✅ "We added a progress indicator, reducing checkout abandonment by 12%"
❌ "Most users are happy" ✅ "NPS increased from 42 to 58 (n=247 responses)"
When things go wrong: "I underestimated the integration complexity" When things go right: "The engineering team delivered this ahead of schedule"
Don't just state what you decided—explain why: "We're prioritizing mobile over tablet because 87% of our traffic is mobile, and tablet usage is trending down (15% decrease QoQ)."
Example: "The feature we shipped yesterday caused a 30% increase in page load time. This affects all users on mobile devices. I approved the release without adequate performance testing—my mistake. We've rolled back the change and users should see normal performance within the hour. We're adding performance benchmarks to our release checklist."
Example: "I'm requesting 1 additional engineer for Q3 to build the analytics dashboard. Without this, we'll miss the September board meeting commitment, and sales won't have the ROI metrics needed for enterprise deals (estimated $200K+ in lost pipeline). Alternative: we could descope real-time data and ship basic reporting in August, but this limits sales use cases."
Example: "Sarah and the eng team launched the SSO integration 2 weeks early, unlocking our first enterprise deal ($120K ARR). This validates our hypothesis that enterprise customers will pay 3x more for team features. Next up: audit logging, which is the #2 requested feature from this segment."
