Skip to content

hoavdc/CodexKit / skills/codexkit-pmbok8-stakeholder-register

codexkit-pmbok8-stakeholder-register

Unverified

Build and maintain a Stakeholder Register per PMBOK 8 Stakeholder Performance Domain. Identify stakeholders, analyze using Power/Interest grid, plan engagement strategies, and define communication cadence. Use at project initiation and whenever stakeholder landscape changes.

Stakeholder Register Builder

When to Use

  • At project initiation to map the stakeholder landscape
  • When a major change introduces new stakeholders
  • When engagement issues surface (resistance, disengagement, conflict)
  • Before major milestone reviews to validate stakeholder alignment

Procedure

Step 1 — Identify Stakeholders

  1. Review project charter, business case, and org chart
  2. Brainstorm internal stakeholders (sponsor, team, PMO, functional leads)
  3. Identify external stakeholders (vendors, regulators, customers, partners)
  4. Classify by relationship: Decision-maker / Influencer / Contributor / Observer

Step 2 — Analyze (Power × Interest Grid)

Map each stakeholder on a 2×2 matrix:

High InterestLow Interest
High PowerManage CloselyKeep Satisfied
Low PowerKeep InformedMonitor

For each stakeholder, also assess:

  • Current attitude: Supportive / Neutral / Resistant
  • Desired attitude: Where you need them to be
  • Influence direction: Upward / Downward / Lateral / External

Step 3 — Plan Engagement

For each quadrant, define the engagement strategy:

QuadrantStrategyCommunication Frequency
Manage CloselyProactive, face-to-face, co-createWeekly or bi-weekly
Keep SatisfiedRegular updates, escalation channelBi-weekly or monthly
Keep InformedStatus reports, newslettersMonthly
MonitorPassive, available on requestQuarterly or ad-hoc

Step 4 — Define RACI Alignment

Map key stakeholders to project deliverables using RACI:

  • Responsible — does the work
  • Accountable — owns the outcome
  • Consulted — provides input
  • Informed — receives updates

Inputs

InputRequiredFormat
Project charter or briefYesDocument or summary
Org chartRecommendedHierarchy diagram or list
Sponsor briefRecommendedKey expectations and constraints

Output

## Stakeholder Register — [Project Name]

### Register

| # | Name | Role | Power | Interest | Quadrant | Current | Desired | Strategy |
|---|------|------|-------|----------|----------|---------|---------|----------|
| 1 | Jane Kim | VP Finance | High | High | Manage Closely | Neutral | Supportive | Weekly 1:1, co-design budget review |
| 2 | Mark Lee | IT Director | High | Low | Keep Satisfied | Supportive | Supportive | Monthly status email + escalation path |
| 3 | Sarah Chen | End User Lead | Low | High | Keep Informed | Resistant | Neutral | Include in demos, gather feedback |
| 4 | External Auditor | Regulator | High | Low | Keep Satisfied | Neutral | Neutral | Quarterly compliance report |

### Power/Interest Grid

        High Power │ Keep Satisfied │ Manage Closely │
                   │    Mark Lee     │   Jane Kim      │
        ───────────┼────────────────┼─────────────────│
        Low Power  │    Monitor     │ Keep Informed   │
                   │                │   Sarah Chen     │
                   └──Low Interest──┴──High Interest──┘

### Communication Plan

| Stakeholder | Channel | Frequency | Owner | Content |
|-------------|---------|-----------|-------|---------|
| Jane Kim | 1:1 meeting | Weekly | PM | Decisions, risks, budget |
| Mark Lee | Email report | Monthly | PM | Status, IT dependencies |
| Sarah Chen | Demo + survey | Bi-weekly | BA | Feature feedback |

### RACI — Key Deliverables

| Deliverable | Jane Kim | Mark Lee | Sarah Chen | PM |
|-------------|----------|----------|------------|-----|
| Requirements | C | C | R | A |
| Budget approval | A | I | I | R |
| User testing | I | C | R | A |

Definition of Done

  • All stakeholders identified with role and org position
  • Power/Interest grid completed for each stakeholder
  • Engagement strategy defined per quadrant
  • Communication plan with frequency, channel, and owner
  • Current vs desired attitude gap identified
  • At least one RACI matrix for key deliverables

Examples

Prompt

I am starting a new ERP implementation project.
Sponsor: CFO. Key departments: Finance, IT, Operations, HR.
External: ERP vendor (SAP), external auditor.
Build a complete stakeholder register with engagement strategies and communication plan.

Quality Criteria

  • All dependencies and prerequisites are documented
  • Changes are reversible or include a rollback plan
  • Security implications are assessed for each configuration change
  • Monitoring and alerting are defined for post-deployment validation

Verification (4C)

CheckQuestion
CorrectnessAre all configurations, permissions, and dependencies accurate?
CompletenessDoes the setup cover dev, staging, and prod environments as needed?
Context-fitIs the solution proportional to the problem (not over/under-engineered)?
ConsequenceIf deployed as-is to production, what is the highest-risk failure mode?

Edge Cases

  • Target environment has pre-existing configuration — Scan for conflicts before applying changes. Document what to preserve.
  • Permissions differ between environments — Test in staging first. Document the minimum permissions required.
  • Third-party service is unavailable or deprecated — Document fallback or alternative. Include health-check endpoints.

Changelog

  • v1.0.0 — Initial release
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 464kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 464kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 318kUpdated Claude CodeCodexUnverifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 318kUpdated Claude CodeCodexUnverifiedInstall