agentsclimarketplace

Program health dashboard

Skill janellecipriano/pm-skills/skills/program-health-dashboard

Open-source Claude skills for Program Management in product development — charters, status reports, RAID logs, roadmaps, launch readiness, retros, postmortems, OKRs & more.

Install
npx -y skills add janellecipriano/pm-skills --skill program-health-dashboard

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Assemble a one-page program health snapshot across multiple workstreams — RAG status, milestones, top risks, dependencies, and metrics in a single scannable view. Use when the user says "program dashboard", "program health", "portfolio status", "one-pager across workstreams", "roll up all the projects", or needs an at-a-glance view of a multi-stream program.

SKILL.md

2.1 KB, as published. Nobody here has run it

Program Health Dashboard

Roll multiple workstreams into a single, scannable one-page health view for program leads and steering committees.

When to use

  • A program spans several projects/workstreams and needs one combined view.
  • Prepping a steering/portfolio review.

For a single project's narrative update, use status-report; for a leadership narrative, exec-summary.

Inputs to gather

  • The workstreams and their owners.
  • Per workstream: RAG status, next milestone + date, top risk, key metric.
  • Cross-program risks and dependencies (pull from raid-log / dependency-mapping).

Process

  1. Set an overall program RAG with a one-line rationale (worst-of, weighted by importance — explain the logic).
  2. Build the workstream table: name · owner · RAG · next milestone (date) · trend (↑/→/↓ vs. last period) · top risk.
  3. Surface top cross-program risks/blockers (3–5 max) with owners.
  4. Show key metrics vs. target where the program is measured (tie to okr-tracking).
  5. List upcoming milestones across all streams in date order.
  6. Note decisions needed from leadership.

Output format

# {{Program}} — Health · {{date}}
**Overall:** 🟢/🟡/🔴 — {{rationale}}

## Workstreams
| Workstream | Owner | Status | Next milestone (date) | Trend | Top risk |
| --- | --- | --- | --- | --- | --- |

## Top risks & blockers (program-level)
| Risk | Impact | Owner | Mitigation |

## Key metrics
| Metric | Target | Current | Status |

## Upcoming milestones
| Date | Milestone | Workstream |

## Decisions needed
- {{ask}}

Keep it to one page — this is a glance, not a deep read. Link out for detail.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.