Coordinate the work that spans projects, teams, vendors, and organizational boundaries so a collection of locally successful efforts produces the outcome it was meant to produce.

Why Install This Skill

A program can be full of green project dashboards and still be failing. The integration path is late, the shared specialist is committed three ways, the benefits belong to nobody, and each team has optimized its own deliverable while the larger change quietly comes apart. This skill gives an agent a way to see and manage those seams.

It helps establish a real program mandate, connect component projects to a shared outcome, manage cross-project dependencies and capacity, surface trade-offs to the people who can decide them, and keep benefits and adoption from becoming somebody else's problem. It complements technical-project-management, which owns the control of one bounded project.

What You Get

Contents	What they provide
`SKILL.md`	Program-level operating loop, method selection, troubleshooting, communication, and routing
`references/`	Research ledger, program controls, benefits dependency networks, tranches, transformation, assurance, and failure recovery
`templates/`	Program brief, integrated control record, benefits dependency map, independent assurance review, and stakeholder update
`evals/`	Portable output-quality cases for realistic program decisions

Quick Start

Ask: "We have four projects modernizing one platform. Each is reporting green, but integration and adoption are slipping. Help me build an integrated program view and prepare the sponsor decisions."

Triggers

Coordinating multiple related technical projects, products, teams, or suppliers toward one outcome.
Managing cross-project dependencies, shared capacity, funding, architecture, or release sequencing.
Tracking program benefits, adoption, transformation, and disbenefits.
Preparing executive, component-team, vendor, or operations communication about program health.
Recovering a troubled program whose component projects look healthy in isolation.

Requirements

No service, API key, or runtime is required. The skill is platform-agnostic and uses Markdown artifacts. Route project-level control, detailed implementation planning, product portfolio decisions, enterprise architecture, release approval, and incident command to their owning skills.