npx claudepluginhub frank-luongt/faos-skills-marketplace --plugin faos-pmThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Reviews prose for communication issues impeding comprehension, outputs minimal fixes in a three-column table per Microsoft Writing Style Guide. Useful for 'review prose' or 'improve prose' requests.
A Power x Interest grid for identifying, categorizing, and managing stakeholders — with tailored communication strategies for each quadrant.
Product initiatives fail more often from stakeholder misalignment than from bad engineering. This skill maps who cares, who has power, and what each person needs from you — preventing surprises, building support, and managing resistance proactively.
List everyone who is:
Don't forget:
For each stakeholder, rate:
HIGH INTEREST
│
┌────────────────────┼────────────────────┐
│ │ │
│ Keep Satisfied │ Manage Closely │
│ │ │
│ Periodic updates │ Regular 1:1s │
│ Escalate critical │ Involve in │
│ issues only │ decisions │
│ │ │
HIGH├────────────────────┼────────────────────┤
POWER │
│ │ │
│ Monitor │ Keep Informed │
│ │ │
│ Light-touch │ Status updates │
│ Watch for │ Demo invitations │
│ changes │ Feedback channel │
│ │ │
└────────────────────┼────────────────────┘
LOW INTEREST
These are your most important stakeholders. Mismanaging them kills projects.
They can make or break your project but don't want to be in the details.
They care deeply but can't directly block you. Often your best advocates.
Minimal investment needed — but watch for changes.
Flag stakeholders who:
# Stakeholder Map — [Initiative Name]
**Date:** [date]
**PM:** [name]
---
## Stakeholder Grid
### Manage Closely (High Power, High Interest)
| Stakeholder | Role | Interest Area | Communication Plan | Potential Risk |
| --- | --- | --- | --- | --- |
| [name] | [role] | [what they care about] | Weekly 1:1, involve in [decisions] | [risk if mismanaged] |
### Keep Satisfied (High Power, Low Interest)
| Stakeholder | Role | Interest Area | Communication Plan | Escalation Trigger |
| --- | --- | --- | --- | --- |
| [name] | [role] | [what they care about] | Monthly summary | [when to escalate] |
### Keep Informed (Low Power, High Interest)
| Stakeholder | Role | Interest Area | Communication Plan | Leverage |
| --- | --- | --- | --- | --- |
| [name] | [role] | [what they care about] | Sprint updates, demos | [how they can help] |
### Monitor (Low Power, Low Interest)
| Stakeholder | Role | Watch For |
| --- | --- | --- |
| [name] | [role] | [condition that would increase their interest/power] |
---
## Conflicts and Risks
| Conflict | Stakeholders Involved | Mitigation |
| --- | --- | --- |
| [conflict description] | [names] | [how to handle] |
---
## Communication Calendar
| Cadence | Audience | Format | Owner |
| --- | --- | --- | --- |
| Weekly | Manage Closely group | 1:1 meetings | PM |
| Bi-weekly | Keep Informed group | Sprint demo | PM + Eng Lead |
| Monthly | Keep Satisfied group | Email summary | PM |
| Quarterly | All stakeholders | Roadmap review | PM + Leadership |
| Avoid | Why | Instead |
|---|---|---|
| Treating all stakeholders equally | Wastes time on low-impact people, under-invests in critical ones | Use the grid to prioritize |
| Only mapping supporters | Resistors cause the most damage if ignored | Map everyone, especially skeptics |
| Static map | People change roles, priorities shift | Review monthly |
| Communicating the same way to everyone | Execs want summaries, ICs want details | Tailor format and depth |
| Skipping the conflict analysis | Unaddressed conflicts escalate | Name conflicts, plan mitigation |