stakeholder-comms-planner-scott-margetts
Stakeholder mapping, communication plan design, reporting hierarchy, and mid-matter comms updates. Use when setting up a new matter and needing to identify who needs what information, designing the communication rhythm, building reporting structures for multi-jurisdiction programmes, or updating the comms plan when the stakeholder landscape changes. Trigger on: 'stakeholder map', 'who needs to be kept informed', 'communication plan', 'reporting structure', 'who do we report to', 'how often do we meet', 'client wants more updates', 'new contact on the client side', 'build the comms plan', 'repo
npx skills add lawve-ai/awesome-legal-skills --skill stakeholder-comms-planner-scott-margetts --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Designs and maintains the communication architecture for legal matters, including stakeholder mapping, designing reporting rhythms, building hierarchy structures for large programmes, and updating the comms plan when the stakeholder landscape changes.
How it works
- Mode 1 — Stakeholder mapping: identify all stakeholders, classify by influence and interest, assign communication roles, and produce a stakeholder register.
- Mode 2 — Communication plan: from the stakeholder map, design the full communication rhythm (internal and client-facing streams), producing a schedule for the matter plan builder. If Mode 1 output is unavailable, generate from description with placeholders and flag gaps; output should not be blocked by missing stakeholder data.
- Mode 3 — Reporting hierarchy design: for multi-jurisdiction or large programmes, design information flow from jurisdiction level to programme to client, specifying escalation and filtering.
- Mode 4 — Mid-matter comms update: update the existing plan for changes (new contact, role change, added workstream, etc.). If no prior plan exists, infer a prior plan from change description and apply changes, flagging gaps. Required outputs: updated stakeholder register entry, changes table, timezone analysis, action flags for partners/attorneys, onboarding call recommendation.
When to use it
Use at matter setup to map stakeholders and determine information needs and cadence; for designing or updating internal and client-facing reporting rhythms; for multi-jurisdiction programmes; and when the stakeholder landscape changes mid-matter.
What it can touch
The skill specifies roles and outputs (stakeholder register, communication plan, reporting hierarchy, and mid-matter updates) but does not list executable tools or files beyond its own outputs. It instructs producing outputs and structured tables for stakeholder information and cadence.
Caveats
The skill emphasizes mode-specific outputs and placeholders when data is incomplete, and requires an onboarding call recommendation for new stakeholders in Mode 4. It uses a two-tier reporting approach and risk-aware onboarding language requirements for new stakeholders.
# Stakeholder Comms Planner You are a Legal Project Management skill that designs and maintains the communication architecture for legal matters. You encode the methodology an experienced LPM applies when mapping stakeholders, designing reporting rhythms, building hierarchy structures for large programmes, and updating comms plans when the landscape changes. The problem this skill solves: on complex matters, the wrong people get too much information, the right people get too little, and nobody designed it that way — it evolved. Communication plans that are designed at matter setup and maintained through the matter reduce ad hoc "what's the status of?" communication, prevent relationship surprises, and ensure decisions reach decision-makers without being filtered out or diluted. ## When to use this skill - Setting up a new matter — who are the stakeholders, what do they need, how often - Designing the reporting rhythm — internal and client-facing streams separately - Multi-jurisdiction programmes — building a reporting hierarchy that aggregates without losing signal - Stakeholder landscape changes mid-matter — new contact, restructured client team, added workstream - Partner asks ho
- When to use this skill
- Before Starting Any Mode
- Operating Modes
- Mode 1 — Stakeholder mapping
- Mode 2 — Communication plan
- Mode 3 — Reporting hierarchy design
- Mode 4 — Mid-matter comms update
- Domain Knowledge — Stakeholder Mapping
- The power/interest framework
- Communication roles — RASIC adapted for legal matters
- Stakeholder register — required fields
- The primary contact problem
- Domain Knowledge — Communication Planning
- The two reporting streams
What does the stakeholder-comms-planner-scott-margetts skill do?
Stakeholder mapping, communication plan design, reporting hierarchy, and mid-matter comms updates. Use when setting up a new matter and needing to identify who needs what information, designing the communication rhythm, building reporting structures for multi-jurisdiction programmes, or updating the comms plan when the stakeholder landscape changes. Trigger on: 'stakeholder map', 'who needs to be kept informed', 'communication plan', 'reporting structure', 'who do we report to', 'how often do we meet', 'client wants more updates', 'new contact on the client side', 'build the comms plan', 'repo
How do I install it?
Run `npx skills add lawve-ai/awesome-legal-skills --skill stakeholder-comms-planner-scott-margetts --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From lawve-ai/awesome-legal-skills, a repository with 618 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.