senior-pm

Imported from borghei/claude-skills (project-management/senior-pm/SKILL.md). Install upstream with npx skills add borghei/claude-skills --skill senior-pm. Copyright stays with the author (MIT + Commons Clause).

Senior Project Management Expert

Overview

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"

Core Capabilities

• Portfolio health & strategic alignment — multi-dimensional weighted scoring (timeline, budget, scope, quality, risk), RAG status, three-horizons rebalancing
• Quantitative risk management — EMV analysis, three-point/Monte Carlo estimation, category weighting, portfolio risk correlation, risk-appetite framework
• Advanced prioritization — WSJF, RICE, ICE, MoSCoW, MCDA with a model-selection decision tree
• Resource capacity planning — utilization optimization (70-85% band), skill matching, bottleneck identification, scenario planning
• Executive communication & governance — board-ready RAG reports, RACI matrices, escalation paths, risk-adjusted ROI/NPV

Clarify First

Before generating the report or analysis, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.

• 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).

Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.

Quick Start

# Tier 1 — portfolio health (multi-dimensional RAG scoring)
python3 scripts/project_health_dashboard.py assets/sample_project_data.json

# Tier 2 — quantitative risk matrix + mitigation strategy
python3 scripts/risk_matrix_analyzer.py assets/sample_project_data.json

# Tier 3 — resource capacity / utilization
python3 scripts/resource_capacity_planner.py assets/sample_project_data.json

# Stakeholder mapping (Mendelow's Matrix + comms plan)
python3 scripts/stakeholder_mapper.py --demo --format json

Anti-Patterns

Burying the ask in the executive report

Mistake: The 20-slide deck puts the decision the exec must make on slide 14. Why it happens: Decks follow the order the work happened, so the ask lands at the end. Instead: Put the decision or ask on slide 1 or in the first 100 words. Any ask past slide 5 means the report needs restructuring. Executives skim, and a missed ask leads to a decision made on incomplete data.

Averaging the portfolio into one color

Mistake: The dashboard shows portfolio health as a single R/Y/G. Two projects are red, but the aggregate reads yellow. Why it happens: One summary color is what executives asked for, and averaging is the easy way to produce it. Instead: Name each red project next to any aggregate from project_health_dashboard.py. Eight greens and two reds is not a yellow portfolio. It has two projects that need attention now.

A risk matrix with no mitigations

Mistake: The risk matrix plots 22 risks by probability and impact, with no mitigation column. Why it happens: Plotting and scoring feel like the analysis, so the plan for each risk gets left for later. Instead: Give every risk a mitigation before the matrix goes to anyone. risk_matrix_analyzer.py outputs a mitigation strategy, so carry it into the report instead of showing the plot alone.

Seven more, each with a bad and a good example: references/red-flags.md.

References

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