dsivov/stakeholder-communication
.claude/skills/stakeholder-communication/SKILL.md
Use when the Manager is writing status updates, daily reports, queue messages to team members, escalation notices, or cross-role coordination messages. Activates when composing any team communication, reports, or documentation updates.
documentation
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add dsivov/ai_development_team stakeholder-communicationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 2:51 PM4.4s1 file scanned
SKILL.md
- name:
- stakeholder-communication
- description:
- Use when the Manager is writing status updates, daily reports, queue messages to team members, escalation notices, or cross-role coordination messages. Activates when composing any team communication, reports, or documentation updates.
- version:
- 1.0.0
Stakeholder Communication Expertise
When This Applies
Apply this guidance when:
- Writing queue messages to team members
- Composing daily reports
- Drafting status updates or escalation notices
- Coordinating work across multiple roles
Communication Principles
- Be specific — Include task IDs, file paths, branch names. Never say "the thing we discussed."
- State the action needed — Every message should make clear what the recipient should DO.
- Include context — The recipient may not share your context. Include enough background.
- Match urgency to priority — Use appropriate queue priority levels. Don't cry wolf.
- One topic per message — Separate concerns into separate queue items.
Message Templates
Task Assignment
Assigning TASK-NNN to you: <subject>
Priority: <priority>
Related CR: CR-NNN
Context: <why this task exists and what it achieves>
Dependencies: <any tasks that must complete first or alongside>
Please update status when you begin work.
Status Request
Requesting status update on TASK-NNN: <subject>
Last known status: <status> as of <date>
Reason for check: <why you need an update>
Please respond with current progress and any blockers.
Blocker Escalation
BLOCKER: TASK-NNN is blocked.
Blocked by: <description of what's blocking>
Impact: <what other tasks/CRs are affected>
Needed from you: <specific action to unblock>
Priority: <escalated priority level>
Approval Notification
TASK-NNN has been approved.
Next step: Integrator to test and commit changes.
Branch: <feature branch name>
Notes: <any conditions or observations from review>
Daily Report Structure
Reports should answer these questions in order:
- What was accomplished? (completed tasks)
- What is in progress? (active work)
- What is blocked? (impediments)
- What's next? (priorities for upcoming sessions)
Keep reports scannable — use tables and bullet points, not paragraphs.
Escalation Guidelines
| Situation | Action |
|-----------|--------|
| Task blocked > 1 session | Send high priority blocker to relevant role |
| Critical bug discovered | Send critical to all affected roles |
| Priority conflict between CRs | Decide and communicate priority change to affected roles |
| Role not responding to queue | Re-send with elevated priority, note the repeat |
Related Skills
dsivov/test-engineering
development
VerifiedTrustedCommunity
Use when the Integrator is writing unit tests, e2e tests, designing test strategies, improving test coverage, creating test fixtures, or mocking dependencies. Activates for any testing-related work including TDD, test refactoring, or test debugging.
SKILL.mdUpdated Apr 16, 2026
dsivov/task-decomposition
development
VerifiedTrustedCommunity
Use when the Architect is breaking down change requests into implementable tasks, defining acceptance criteria, estimating task size, mapping dependencies, or creating technical sub-tasks for Developer and Integrator.
SKILL.mdUpdated Apr 16, 2026
dsivov/system-design
development
VerifiedTrustedCommunity
Use when the Architect is designing system architecture, choosing technology stacks, defining data models, designing APIs, making scalability decisions, or updating ARCHITECTURE.md. Activates for any architecture design, technology evaluation, or system structure discussion.
SKILL.mdUpdated Apr 16, 2026
dsivov/rollback-procedures
devops
VerifiedTrustedCommunity
Use when the Production Engineer is planning rollback strategies, reverting a bad release, handling data migration reversals, managing feature flags, implementing hotfix workflows, or preparing disaster recovery procedures. Activates when discussing rollbacks, reverts, or recovery from failed deployments.
SKILL.mdUpdated Apr 16, 2026