Senior PM for enterprise software and SaaS — portfolio management, quantitative risk analysis, prioritization, and executive reporting. Use for portfolio health reviews, board-ready status reports, and multi-project risk/capacity analysis.
Strategic project management for enterprise software, SaaS, and digital transformation initiatives. This skill provides sophisticated portfolio management capabilities, quantitative analysis tools, and executive-level reporting frameworks for managing complex, multi-million dollar project portfolios. It pairs deterministic Python analysis (health scoring, risk matrices, capacity planning, stakeholder mapping) with board-ready communication frameworks.
Use when
The user asks to "run a portfolio health review", "build an executive status report", or "do a stakeholder map"
Multiple projects need prioritization across WSJF / RICE / ICE / MoSCoW with strategic alignment
A board-ready or executive-ready RAG report needs to be produced
Risk analysis needs EMV, Monte Carlo, or portfolio risk correlation — beyond a basic probability/impact matrix
Resource capacity planning is needed across multiple concurrent projects
A quarterly portfolio rebalancing or three-horizons review is being planned
The user says "our portfolio is misaligned", "executives don't trust the reports", or "we can't tell which projects are actually healthy"
Before generating the report or analysis, confirm these inputs. If any is unknown or vague, ASK — do not assume:
Which artifact — portfolio health review, executive status report, stakeholder map, or risk/capacity analysis (each maps to a different tool and structure)
Audience — board, exec staff, or delivery team (sets the altitude, RAG framing, and level of detail)
Portfolio scope and data — which projects and what timeline/budget/risk data exists (scores and dashboards are only as good as the inputs)
Prioritization model — WSJF, RICE, ICE, or MoSCoW, when ranking projects (each produces a different order)
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Load the reference that matches the task — keep this file lean and pull detail on demand:
references/methodology-and-operations.md — the full three-tier analysis approach, prioritization models, risk framework, stakeholder-mapping detail, asset/template descriptions, weekly/monthly/quarterly workflows, handoff protocols, KPIs, anti-patterns, troubleshooting, success criteria, and Python tool flag reference. Read this for any hands-on portfolio, risk, capacity, or reporting work.
references/portfolio-prioritization-models.md — deep dive on WSJF/RICE/ICE/MoSCoW/MCDA and the model-selection decision tree. Read when choosing or defending a prioritization model.
references/risk-management-framework.md — full quantitative risk process: identification, three-point estimation, EMV, portfolio correlation, risk appetite. Read for any non-trivial risk analysis.
references/stakeholder-engagement-guide.md — Mendelow quadrant playbooks, blocker engagement, communication cadences. Read when building a stakeholder/communication plan.
references/red-flags.md — common ways this skill's output goes wrong, with fixes. Read before finalizing a portfolio assessment or executive report.
Scope & Limitations
In Scope: Multi-project portfolio health assessment with weighted composite scoring; quantitative risk analysis using EMV, probability/impact matrices, and category weighting; resource capacity planning with utilization optimization and skill-matching; stakeholder mapping with Mendelow's Matrix and targeted communication plans; executive-level reporting with RAG status dashboards and strategic recommendations.
Out of Scope: Sprint-level team management (see scrum-master/); product backlog management and feature prioritization (see execution/prioritization-frameworks/); agile coaching and team maturity (see agile-coach/); financial modeling beyond project-level ROI (see finance/); contract negotiation and procurement.
Important Caveats: Health scores use deterministic formulas, not ML predictions — calibrate thresholds to your portfolio. Risk EMV assumes independent risks; portfolio correlation analysis (Step 4) gives a more accurate combined view but needs cross-project dependency data. Capacity models are weekly snapshots; they do not account for intra-week variability or unplanned spikes.
Integration Points
Integration
Direction
Description
scrum-master/
Receives from
Sprint velocity and health metrics feed portfolio-level health dashboards
sprint-retrospective/
Receives from
Retro insights inform stakeholder reports and process improvement tracking
execution/brainstorm-okrs/
Feeds into
Portfolio priorities and strategic context shape quarterly OKR themes
execution/outcome-roadmap/
Feeds into
Portfolio health data influences roadmap commitment levels (Now/Next/Later)
discovery/pre-mortem/
Receives from
Launch-blocking tigers escalate into portfolio risk register
execution/release-notes/
Complements
Release notes incorporate stakeholder communication plans from mapper
Jira via Atlassian MCP
Bidirectional
Pull project data for health analysis; push status reports to Confluence
Financial Systems
Receives from
Real-time budget and spend data for variance analysis
1---2name: senior-pm3description: Senior PM for enterprise software and SaaS — portfolio management, quantitative risk analysis, prioritization, and executive reporting. Use for portfolio health reviews, board-ready status reports, and multi-project risk/capacity analysis.4license: MIT + Commons Clause5---6# Senior Project Management Expert
78## Overview
910Strategic project management for enterprise software, SaaS, and digital transformation initiatives. This skill provides sophisticated portfolio management capabilities, quantitative analysis tools, and executive-level reporting frameworks for managing complex, multi-million dollar project portfolios. It pairs deterministic Python analysis (health scoring, risk matrices, capacity planning, stakeholder mapping) with board-ready communication frameworks.
1112## Use when
1314- The user asks to "run a portfolio health review", "build an executive status report", or "do a stakeholder map"
15- Multiple projects need prioritization across WSJF / RICE / ICE / MoSCoW with strategic alignment
16- A board-ready or executive-ready RAG report needs to be produced
17- Risk analysis needs EMV, Monte Carlo, or portfolio risk correlation — beyond a basic probability/impact matrix
18- Resource capacity planning is needed across multiple concurrent projects
19- A quarterly portfolio rebalancing or three-horizons review is being planned
20- The user says "our portfolio is misaligned", "executives don't trust the reports", or "we can't tell which projects are actually healthy"
2122## Core Capabilities
2324- **Portfolio health & strategic alignment** — multi-dimensional weighted scoring (timeline, budget, scope, quality, risk), RAG status, three-horizons rebalancing
25- **Quantitative risk management** — EMV analysis, three-point/Monte Carlo estimation, category weighting, portfolio risk correlation, risk-appetite framework
26- **Advanced prioritization** — WSJF, RICE, ICE, MoSCoW, MCDA with a model-selection decision tree
27- **Resource capacity planning** — utilization optimization (70-85% band), skill matching, bottleneck identification, scenario planning
28- **Executive communication & governance** — board-ready RAG reports, RACI matrices, escalation paths, risk-adjusted ROI/NPV
2930## Clarify First
3132Before generating the report or analysis, confirm these inputs. If any is unknown or vague, ASK — do not assume:
3334- [ ] **Which artifact** — portfolio health review, executive status report, stakeholder map, or risk/capacity analysis (each maps to a different tool and structure)
35- [ ] **Audience** — board, exec staff, or delivery team (sets the altitude, RAG framing, and level of detail)
36- [ ] **Portfolio scope and data** — which projects and what timeline/budget/risk data exists (scores and dashboards are only as good as the inputs)
37- [ ] **Prioritization model** — WSJF, RICE, ICE, or MoSCoW, when ranking projects (each produces a different order)
3839Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
4041## Quick Start
4243```bash
44# Tier 1 — portfolio health (multi-dimensional RAG scoring)
45python3 scripts/project_health_dashboard.py assets/sample_project_data.json
4647# Tier 2 — quantitative risk matrix + mitigation strategy
48python3 scripts/risk_matrix_analyzer.py assets/sample_project_data.json
4950# Tier 3 — resource capacity / utilization
51python3 scripts/resource_capacity_planner.py assets/sample_project_data.json
5253# Stakeholder mapping (Mendelow's Matrix + comms plan)
54python3 scripts/stakeholder_mapper.py --demo --format json
55```
5657## References
5859Load the reference that matches the task — keep this file lean and pull detail on demand:
6061- **[references/methodology-and-operations.md](references/methodology-and-operations.md)** — the full three-tier analysis approach, prioritization models, risk framework, stakeholder-mapping detail, asset/template descriptions, weekly/monthly/quarterly workflows, handoff protocols, KPIs, anti-patterns, troubleshooting, success criteria, and Python tool flag reference. Read this for any hands-on portfolio, risk, capacity, or reporting work.
62- **[references/portfolio-prioritization-models.md](references/portfolio-prioritization-models.md)** — deep dive on WSJF/RICE/ICE/MoSCoW/MCDA and the model-selection decision tree. Read when choosing or defending a prioritization model.
63- **[references/risk-management-framework.md](references/risk-management-framework.md)** — full quantitative risk process: identification, three-point estimation, EMV, portfolio correlation, risk appetite. Read for any non-trivial risk analysis.
64- **[references/stakeholder-engagement-guide.md](references/stakeholder-engagement-guide.md)** — Mendelow quadrant playbooks, blocker engagement, communication cadences. Read when building a stakeholder/communication plan.
65- **[references/red-flags.md](references/red-flags.md)** — common ways this skill's output goes wrong, with fixes. Read before finalizing a portfolio assessment or executive report.
6667## Scope & Limitations
6869**In Scope:** Multi-project portfolio health assessment with weighted composite scoring; quantitative risk analysis using EMV, probability/impact matrices, and category weighting; resource capacity planning with utilization optimization and skill-matching; stakeholder mapping with Mendelow's Matrix and targeted communication plans; executive-level reporting with RAG status dashboards and strategic recommendations.
7071**Out of Scope:** Sprint-level team management (see `scrum-master/`); product backlog management and feature prioritization (see `execution/prioritization-frameworks/`); agile coaching and team maturity (see `agile-coach/`); financial modeling beyond project-level ROI (see `finance/`); contract negotiation and procurement.
7273**Important Caveats:** Health scores use deterministic formulas, not ML predictions — calibrate thresholds to your portfolio. Risk EMV assumes independent risks; portfolio correlation analysis (Step 4) gives a more accurate combined view but needs cross-project dependency data. Capacity models are weekly snapshots; they do not account for intra-week variability or unplanned spikes.
7475## Integration Points
7677| Integration | Direction | Description |
78|------------|-----------|-------------|
79| `scrum-master/` | Receives from | Sprint velocity and health metrics feed portfolio-level health dashboards |
80| `sprint-retrospective/` | Receives from | Retro insights inform stakeholder reports and process improvement tracking |
81| `execution/brainstorm-okrs/` | Feeds into | Portfolio priorities and strategic context shape quarterly OKR themes |
82| `execution/outcome-roadmap/` | Feeds into | Portfolio health data influences roadmap commitment levels (Now/Next/Later) |
83| `discovery/pre-mortem/` | Receives from | Launch-blocking tigers escalate into portfolio risk register |
84| `execution/release-notes/` | Complements | Release notes incorporate stakeholder communication plans from mapper |
85| Jira via Atlassian MCP | Bidirectional | Pull project data for health analysis; push status reports to Confluence |
86| Financial Systems | Receives from | Real-time budget and spend data for variance analysis |
Run npx skillmds@latest add borghei/senior-pm in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Senior PM for enterprise software and SaaS — portfolio management, quantitative risk analysis, prioritization, and executive reporting. Use for portfolio health reviews, board-ready status reports, and multi-project risk/capacity analysis. It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free. This skill is licensed under MIT + Commons Clause.
borghei (@borghei) published this skill. Their other Agent Skills are listed on their SkillMD profile.