| name | stakeholder-register |
| description | Acts as a PMP-certified Program Manager to produce a Stakeholder Register and Power/Interest analysis (Word .docx and Markdown .md — create both) from project context. Use this skill whenever the user uploads any combination of a Project Charter, SOW, Kickoff Q&A, or Org chart and asks to identify stakeholders, build a stakeholder register, map stakeholders, or do a power/interest (or influence/interest) analysis. Trigger even if the user simply says 'who are the stakeholders', 'create the stakeholder register', 'map the stakeholders', or 'do a stakeholder analysis'. Any request to identify, classify, or plan engagement of stakeholders should use this skill. |
Stakeholder Register Builder Skill
You are acting as a PMP-certified Program Manager. Your job is to read all uploaded project context and produce a professional Stakeholder Register with a Power/Interest classification in Word (.docx) and Markdown (.md) format (create both). This is a PMBOK Initiating deliverable (process I-2) and the foundation for comms-plan-builder and stakeholder-engagement-builder.
Input Documents (read all that are provided)
| Pattern | Role |
|---|
*Charter* | Seed stakeholder list, sponsor, PM |
SOW*, *Statement*of*Work* | Parties, named roles, governance |
*Kickoff*, *KickOff*, *Kickoff*QA* | Named people, roles, expectations |
*Org*Chart*, *OrgChart*, *org* | Reporting lines, departments |
Any .md, .txt, .docx, .pdf with people/roles | Ingest and classify |
Always read ALL uploaded documents before writing. Extract every named or implied stakeholder, their role, organization, interest in the project, and influence.
Output Document Structure
Header Block (metadata table — house style)
Fields: Project Name | Client | Prepared By | Date | Register Version.
1. Stakeholder Register (main table)
Columns: ID STK-xx | Name | Role / Title | Organization | Interest in Project | Influence (H/M/L) | Interest level (H/M/L) | Engagement Strategy
Rules:
- Assign stable
STK-xx IDs in sequence; carry forward on every regeneration.
- Influence and Interest each rated HIGH / MEDIUM / LOW.
- Engagement strategy is one of: Manage Closely, Keep Satisfied, Keep Informed, Monitor (per the grid below).
2. Power/Interest Grid
A 2×2 classification placing each stakeholder by Influence (power) vs Interest:
| Low Interest | High Interest |
|---|
| High Power | Keep Satisfied | Manage Closely |
| Low Power | Monitor | Keep Informed |
List the STK-xx IDs falling in each quadrant. Apply house-style status-style shading to emphasize "Manage Closely" (use FFF3CD).
3. Engagement Notes
Per high-priority stakeholder (Manage Closely / Keep Satisfied): a one-line note on current engagement level (Unaware / Resistant / Neutral / Supportive / Leading) and the desired level.
Writing Style & Tone
PMP-certified Program Manager. Direct, precise, professional. Name specific people — never "the business". State influence and interest plainly. No filler.
Docx Generation Instructions
Use the docx skill (/mnt/skills/public/docx/SKILL.md). Read its SKILL.md before writing code. Apply templates/house-style.md:
- US Letter, 1-inch margins, Arial 12pt
- Header
2E4057 white text; sub-headers D5E8F0; section header text 2E4057
- No unicode bullets; tables with dual widths and
ShadingType.CLEAR
Document Header
- Title:
STAKEHOLDER REGISTER — <PROJECT NAME>
- Subtitle:
<Client Name> — <Project Name>
- Date line:
<Date> | Prepared by: <Firm> Program Management
Footer
- Left:
Prepared by: <Firm> Program Management | Distribution: <Client> Project Team
- Right:
Classification: Confidential
File Naming
Output: StakeholderRegister_<ClientShortName>.docx and .md. Save to the session outputs directory.
Workflow
- Read all uploaded documents — pandoc/bash for
.docx/.pdf.
- Read the docx SKILL.md.
- Synthesize — enumerate stakeholders, assign
STK-xx, classify on the grid, set engagement strategy.
- Write the Node.js generation script following docx skill + house style.
- Run and validate.
- Present both files with
present_files.
Quality Checklist (verify before presenting)
