weekly-status-rollup

Generate weekly executive status roll-ups and update PORTFOLIO.md with project health data.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/cody-hutson/pmo-platform --skill weekly-status-rollup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weekly-status-rollup
Source: https://github.com/cody-hutson/pmo-platform/tree/main/operations/skills/weekly-status-rollup
Command: npx skills add https://github.com/cody-hutson/pmo-platform --skill weekly-status-rollup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pypdf, pdfplumber, pdf2image, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the generation of a weekly executive status roll-up across all active projects, providing a comprehensive overview of project health, risks, decisions, and milestones. It saves time and ensures accuracy in reporting to leadership and stakeholders.

Core Features & Use Cases

  • Automated Status Roll-up: Generates a comprehensive weekly status roll-up across all active projects.
  • Health Indicators: Provides a visual representation of project health, including key risks and decisions.
  • Portfolio Dashboard Update: Updates the PORTFOLIO.md file with synthesized health data, keeping the portfolio dashboard current.
  • Use Case: Imagine you are a PMO practitioner. Use this Skill to produce a weekly executive summary that includes project health, key risks, decisions, and upcoming milestones, and then automatically update the PORTFOLIO.md file with the synthesized data.

Quick Start

Run the weekly-status-rollup skill to generate the executive status roll-up for all active projects.

Frequently Asked Questions about weekly-status-rollup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a weekly executive status roll-up across all active projects?

A weekly executive status roll-up aggregates project health, risks, decisions, and milestones from project documentation and communications logs. This Skill synthesizes that data and writes it back to a portfolio dashboard file.

What is the best way to prepare a SteerCo update from multiple project documentation files?

Preparing a SteerCo update requires analyzing project documentation, metrics, and communications logs to extract health indicators and key risks. This process generates a comprehensive cross-project status overview for leadership reporting.

Can I automatically update a portfolio dashboard with synthesized project health data?

Updating a portfolio dashboard with project health data involves writing synthesized metrics, risks, and decisions to a markdown file. This Skill targets the PORTFOLIO.md file to keep your cross-project status current.

Does this weekly status roll-up process PDF project documentation and metrics?

The weekly status roll-up processes project documentation using PDF parsing libraries like pypdf, pdfplumber, and pdf2image. It extracts health indicators and milestones from these files to build the executive summary.

What limitations exist when tracking project health and decisions from communications logs?

Tracking project health from communications logs depends on the consistency of the source documentation and metrics provided. The roll-up requires comprehensive project documentation to accurately synthesize risks and decisions.

When do I need to generate a cross-project status summary instead of individual project reports?

A cross-project status summary is needed when providing leadership with a portfolio dashboard view of overall project health, risks, and milestones. It is triggered for weekly roll-ups, SteerCo prep, and executive status reporting.