Agent skill
stakeholder-brief
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/stakeholder-brief
SKILL.md
Document Intelligence
This skill supports three modes: Create, Update, and Find.
Mode Detection
| Signal | Mode | Confidence |
|---|---|---|
| "update", "revise", "modify" in input | UPDATE | 100% |
File path provided (@path/to/brief.md) |
UPDATE | 100% |
| "create", "new", "draft" in input | CREATE | 100% |
| "find", "search", "list briefs" | FIND | 100% |
| "the brief", "the stakeholder update" | UPDATE | 85% |
| Just topic | CREATE | 60% |
Threshold: ≥85% auto-proceed | 70-84% state assumption | <70% ask user
Mode Behaviors
CREATE: Generate complete new stakeholder brief using template below.
UPDATE:
- Read existing brief (search if path not provided)
- Preserve context and key messages
- Update details, timeline, or FAQ
- Add new stakeholder-specific messages if needed
- Show diff summary: "Updated: [sections]. Unchanged: [sections]."
FIND:
- Search paths below for stakeholder briefs
- Present results: topic, date, audience, path
- Ask: "Update one of these, or create new?"
Search Locations for Stakeholder Briefs
communications/briefs/stakeholder/updates/
Create a Stakeholder Communication Brief for an important update.
V2V Phase
Phase 4: Coordinated Execution - Stakeholder briefs keep everyone informed during execution.
Prerequisites: Strategy or update defined, stakeholders identified Outputs used by: Stakeholder alignment, decision support
Output Structure
# Stakeholder Brief: [Topic]
**Date**: [Date]
**Author**: [Name]
**Audience**: [Target stakeholders]
**Type**: Update / Decision Request / FYI
## TL;DR
[2-3 sentence summary of the key message]
## Context
**Background**: [What stakeholders need to know to understand this]
**Why Now**: [Why this communication is happening now]
## Key Message
[The main point you want stakeholders to take away]
## Details
### What's Happening
[Description of the situation, change, or update]
### Impact
**Who's Affected**: [Teams, customers, etc.]
**How**: [Nature of the impact]
**When**: [Timeline]
### What We're Doing About It
[Actions being taken]
## Stakeholder-Specific Messages
| Stakeholder | Their Concern | Key Message | Action Needed |
|-------------|---------------|-------------|---------------|
| [Stakeholder 1] | [Concern] | [Message] | [Action] |
| [Stakeholder 2] | [Concern] | [Message] | [Action] |
## FAQ
**Q: [Anticipated question 1]**
A: [Answer]
**Q: [Anticipated question 2]**
A: [Answer]
**Q: [Anticipated question 3]**
A: [Answer]
## What We Need From Stakeholders
| Stakeholder | Ask | By When |
|-------------|-----|---------|
| [Stakeholder] | [Specific ask] | [Date] |
## Timeline
| Date | Milestone |
|------|-----------|
| [Date] | [What happens] |
## Communication Plan
| Audience | Channel | Timing | Owner |
|----------|---------|--------|-------|
| [Audience] | [Channel] | [When] | [Owner] |
## Follow-up
**Questions**: Direct to [Name/contact]
**Next Update**: [Date/cadence]
Instructions
- Ask about target stakeholders if not specified
- Reference any relevant documents via @file syntax
- Tailor messages to stakeholder concerns
- Anticipate questions and prepare answers
- Save in communications/ folder
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?