pm-stakeholder-trackerlisted

# PM stakeholder tracker Stakeholder relationships are the load-bearing structure of PM work, and they fail silently. A senior stakeholder you haven't spoken to in three weeks is not yet a problem; in seven weeks they're a problem you can't easily fix. This skill maintains the cross-cutting view of every stakeholder, surfacing who's at risk of going cold, who has open commitments hanging, and who needs proactive attention. ## When to use - Weekly, as part of or following `pm-weekly-review` - Before any high-stakes period (board prep, fundraise, exec review, customer escalation) - When the user notices a relationship feels off and wants the full picture - Implicitly chained from `pm-meeting-debrief` when a meeting changes commitments across multiple stakeholders Don't use when: - The user is asking about a single project (project's `stakeholders.md` is the right unit) - The user wants to draft for a specific stakeholder (use `pm-inbox-triage` instead) - No stakeholders.md files exist yet — surface that and ask the user to populate ## How to apply ### 1. Chain to `pm-context-loader` Load `you.md`, all project state, and cross-project stakeholders. ### 2. Build the full stakeholder list Aggregate: - `pm-state/stakeholders.md` (cross-project) - `pm-state/projects/<project>/stakeholders.md` for each active project - De-duplicate (people who appear across projects). For each unique stakeholder, capture: - Name, role, org - All projects they touch - Cross-project priori