
Stakeholder Communication
- 12 installs
- 3 repo stars
- Updated January 5, 2026
- pluginagentmarketplace/custom-plugin-product-manager
Helps with ai & agent building tasks.
About
stakeholder-communication is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.
- stakeholder-communication
- AI & Agent Building
- AI-coding skill
Stakeholder Communication by the numbers
- 12 all-time installs (skills.sh)
- Ranked #11,618 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/pluginagentmarketplace/custom-plugin-product-manager --skill stakeholder-communicationAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 12 |
|---|---|
| repo stars | ★ 3 |
| Last updated | January 5, 2026 |
| Repository | pluginagentmarketplace/custom-plugin-product-manager ↗ |
What it does
Helps with ai & agent building tasks.
Files
Stakeholder Communication Skill
Effectively communicate with stakeholders and manage expectations across the organization. Master executive communication and alignment.
Executive Communication
BLUF Format (Bottom Line Up Front)
BOTTOM LINE: [1 sentence - decision/news]
SITUATION: [2-3 sentences - context]
IMPLICATIONS: [2-3 sentences - why it matters]
NEXT STEPS: [Actions needed]Executive Summary Template
TITLE: [Topic]
DATE: [Date]
OWNER: [Name]
SUMMARY:
[2-3 sentence overview]
KEY METRICS:
- Metric 1: [Current vs Target]
- Metric 2: [Current vs Target]
DECISION NEEDED:
[What you need from reader]
TIMELINE:
[Key dates]Stakeholder Management
Stakeholder Matrix
HIGH INFLUENCE
│
MANAGE │ ENGAGE
CLOSELY │ ACTIVELY
(Weekly) │ (Weekly)
│
LOW ─────────────┼───────────── HIGH
INTEREST │ INTEREST
│
MONITOR │ KEEP
ONLY │ INFORMED
(Quarterly) │ (Bi-weekly)
│
LOW INFLUENCERACI Matrix
| Task | Responsible | Accountable | Consulted | Informed |
|---|---|---|---|---|
| Task 1 | Dev Lead | PM | Design | Eng Team |
| Task 2 | PM | CEO | Sales | All |
Presentation Skills
Presentation Structure (15 min)
1. Hook (1 min) - Why should they care?
2. Context (2 min) - Background
3. Problem (2 min) - What's wrong
4. Solution (5 min) - What you propose
5. Impact (3 min) - Benefits & metrics
6. Ask (2 min) - What you needData Visualization Rules
- One point per chart
- Labels on chart, not legend
- Highlight key data
- Remove chart junk
- Use consistent colors
Written Communication
Status Update Template
PROJECT: [Name]
STATUS: On Track / At Risk / Off Track
PROGRESS THIS WEEK:
- [Completed item]
- [Completed item]
NEXT WEEK:
- [Planned item]
- [Planned item]
BLOCKERS:
- [Blocker + mitigation]
METRICS:
- [KPI]: [Value vs Target]Decision Document
DECISION: [What we decided]
DATE: [Date]
PARTICIPANTS: [Who was involved]
CONTEXT:
[Why this decision was needed]
OPTIONS CONSIDERED:
1. [Option A] - Pros/Cons
2. [Option B] - Pros/Cons
DECISION RATIONALE:
[Why we chose this option]
NEXT STEPS:
- [Action] - Owner - DateTroubleshooting
Yaygın Hatalar & Çözümler
| Hata | Olası Sebep | Çözüm |
|---|---|---|
| Stakeholder surprise | No early warning | Increase frequency |
| Misalignment | Unclear communication | BLUF, document |
| No decision | Too many stakeholders | RACI, single decider |
| Resistance | Not included early | Early involvement |
Debug Checklist
[ ] RACI defined mi?
[ ] Communication cadence set mi?
[ ] Key stakeholders informed mi?
[ ] Decisions documented mi?
[ ] Follow-up scheduled mi?Recovery Procedures
1. Stakeholder Surprise → 1:1 meeting, rebuild trust 2. Misalignment → Alignment meeting, document 3. Decision Deadlock → Escalate with recommendation
Learning Outcomes
- Present effectively to executives
- Manage stakeholder expectations
- Write clear status updates
- Build organizational alignment
- Handle difficult conversations
# stakeholder-communication Configuration
# Category: general
# Generated: 2025-12-30
skill:
name: stakeholder-communication
version: "1.0.0"
category: general
settings:
# Default settings for stakeholder-communication
enabled: true
log_level: info
# Category-specific defaults
validation:
strict_mode: false
auto_fix: false
output:
format: markdown
include_examples: true
# Environment-specific overrides
environments:
development:
log_level: debug
validation:
strict_mode: false
production:
log_level: warn
validation:
strict_mode: true
# Integration settings
integrations:
# Enable/disable integrations
git: true
linter: true
formatter: true
{
"$schema": "http://json-schema.org/draft-07/schema#",
"title": "stakeholder-communication Configuration Schema",
"type": "object",
"properties": {
"skill": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"version": {
"type": "string",
"pattern": "^\\d+\\.\\d+\\.\\d+$"
},
"category": {
"type": "string",
"enum": [
"api",
"testing",
"devops",
"security",
"database",
"frontend",
"algorithms",
"machine-learning",
"cloud",
"containers",
"general"
]
}
},
"required": [
"name",
"version"
]
},
"settings": {
"type": "object",
"properties": {
"enabled": {
"type": "boolean",
"default": true
},
"log_level": {
"type": "string",
"enum": [
"debug",
"info",
"warn",
"error"
]
}
}
}
},
"required": [
"skill"
]
}Stakeholder Communication Guide
Overview
This guide provides comprehensive documentation for the stakeholder-communication skill in the custom-plugin-product-manager plugin.
Category: General
Quick Start
Prerequisites
- Familiarity with general concepts
- Development environment set up
- Plugin installed and configured
Basic Usage
# Invoke the skill
claude "stakeholder-communication - [your task description]"
# Example
claude "stakeholder-communication - analyze the current implementation"Core Concepts
Key Principles
1. Consistency - Follow established patterns 2. Clarity - Write readable, maintainable code 3. Quality - Validate before deployment
Best Practices
- Always validate input data
- Handle edge cases explicitly
- Document your decisions
- Write tests for critical paths
Common Tasks
Task 1: Basic Implementation
# Example implementation pattern
def implement_stakeholder_communication(input_data):
"""
Implement stakeholder-communication functionality.
Args:
input_data: Input to process
Returns:
Processed result
"""
# Validate input
if not input_data:
raise ValueError("Input required")
# Process
result = process(input_data)
# Return
return resultTask 2: Advanced Usage
For advanced scenarios, consider:
- Configuration customization via
assets/config.yaml - Validation using
scripts/validate.py - Integration with other skills
Troubleshooting
Common Issues
| Issue | Cause | Solution |
|---|---|---|
| Skill not found | Not installed | Run plugin sync |
| Validation fails | Invalid config | Check config.yaml |
| Unexpected output | Missing context | Provide more details |
Related Resources
- SKILL.md - Skill specification
- config.yaml - Configuration options
- validate.py - Validation script
---
Last updated: 2025-12-30
Stakeholder Communication Patterns
Design Patterns
Pattern 1: Input Validation
Always validate input before processing:
def validate_input(data):
if data is None:
raise ValueError("Data cannot be None")
if not isinstance(data, dict):
raise TypeError("Data must be a dictionary")
return TruePattern 2: Error Handling
Use consistent error handling:
try:
result = risky_operation()
except SpecificError as e:
logger.error(f"Operation failed: {e}")
handle_error(e)
except Exception as e:
logger.exception("Unexpected error")
raisePattern 3: Configuration Loading
Load and validate configuration:
import yaml
def load_config(config_path):
with open(config_path) as f:
config = yaml.safe_load(f)
validate_config(config)
return configAnti-Patterns to Avoid
❌ Don't: Swallow Exceptions
# BAD
try:
do_something()
except:
pass✅ Do: Handle Explicitly
# GOOD
try:
do_something()
except SpecificError as e:
logger.warning(f"Expected error: {e}")
return default_valueCategory-Specific Patterns: General
Recommended Approach
1. Start with the simplest implementation 2. Add complexity only when needed 3. Test each addition 4. Document decisions
Common Integration Points
- Configuration:
assets/config.yaml - Validation:
scripts/validate.py - Documentation:
references/GUIDE.md
---
Pattern library for stakeholder-communication skill
#!/usr/bin/env python3
"""
Validation script for stakeholder-communication skill.
Category: general
"""
import os
import sys
import yaml
import json
from pathlib import Path
def validate_config(config_path: str) -> dict:
"""
Validate skill configuration file.
Args:
config_path: Path to config.yaml
Returns:
dict: Validation result with 'valid' and 'errors' keys
"""
errors = []
if not os.path.exists(config_path):
return {"valid": False, "errors": ["Config file not found"]}
try:
with open(config_path, 'r') as f:
config = yaml.safe_load(f)
except yaml.YAMLError as e:
return {"valid": False, "errors": [f"YAML parse error: {e}"]}
# Validate required fields
if 'skill' not in config:
errors.append("Missing 'skill' section")
else:
if 'name' not in config['skill']:
errors.append("Missing skill.name")
if 'version' not in config['skill']:
errors.append("Missing skill.version")
# Validate settings
if 'settings' in config:
settings = config['settings']
if 'log_level' in settings:
valid_levels = ['debug', 'info', 'warn', 'error']
if settings['log_level'] not in valid_levels:
errors.append(f"Invalid log_level: {settings['log_level']}")
return {
"valid": len(errors) == 0,
"errors": errors,
"config": config if not errors else None
}
def validate_skill_structure(skill_path: str) -> dict:
"""
Validate skill directory structure.
Args:
skill_path: Path to skill directory
Returns:
dict: Structure validation result
"""
required_dirs = ['assets', 'scripts', 'references']
required_files = ['SKILL.md']
errors = []
# Check required files
for file in required_files:
if not os.path.exists(os.path.join(skill_path, file)):
errors.append(f"Missing required file: {file}")
# Check required directories
for dir in required_dirs:
dir_path = os.path.join(skill_path, dir)
if not os.path.isdir(dir_path):
errors.append(f"Missing required directory: {dir}/")
else:
# Check for real content (not just .gitkeep)
files = [f for f in os.listdir(dir_path) if f != '.gitkeep']
if not files:
errors.append(f"Directory {dir}/ has no real content")
return {
"valid": len(errors) == 0,
"errors": errors,
"skill_name": os.path.basename(skill_path)
}
def main():
"""Main validation entry point."""
skill_path = Path(__file__).parent.parent
print(f"Validating stakeholder-communication skill...")
print(f"Path: {skill_path}")
# Validate structure
structure_result = validate_skill_structure(str(skill_path))
print(f"\nStructure validation: {'PASS' if structure_result['valid'] else 'FAIL'}")
if structure_result['errors']:
for error in structure_result['errors']:
print(f" - {error}")
# Validate config
config_path = skill_path / 'assets' / 'config.yaml'
if config_path.exists():
config_result = validate_config(str(config_path))
print(f"\nConfig validation: {'PASS' if config_result['valid'] else 'FAIL'}")
if config_result['errors']:
for error in config_result['errors']:
print(f" - {error}")
else:
print("\nConfig validation: SKIPPED (no config.yaml)")
# Summary
all_valid = structure_result['valid']
print(f"\n==================================================")
print(f"Overall: {'VALID' if all_valid else 'INVALID'}")
return 0 if all_valid else 1
if __name__ == "__main__":
sys.exit(main())