technical-program-management

v0.1.2

Technical-program-management team — agents (technical-program-manager, cross-team-dependency-manager, program-launch-coordinator) for delivering a program of projects across teams: program charter + measurable outcomes, dependency mapping and critical-path/integration risk, a RAID-driven program plan, launch-readiness reviews with written go/no-go criteria, staged rollout, and exec status comms that lead with decisions and asks (not activity). skills, a knowledge bank with Mermaid decision trees (TPM-vs-PM-vs-EM, escalate-or-not, go/no-go), best-practices, templates, commands, and an advisory anti-pattern hook. Distinct from project-management (a single project/plan) and engineering-management (people/teams); execution lands in devops-cicd, observability-sre, and the relevant engineering plugins. Requires ravenclaude-core@>=0.7.0.

Claude Code3 Skills

By Matt CorbettLicense: MIT7 GitHub starsUpdated last week

Directory evidence

Runtimes: Claude Code
Parsed components: 3 skill or MCP entries
Source updated: Sep 15, 2026
Manifest status: Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install technical-program-management for Claude Code

Installs for the current user

claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install technical-program-management@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually

$ git clone https://github.com/mcorbett51090/RavenClaude

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/technical-program-management/.

Plugin files

plugins/technical-program-management/

├── .claude-plugin/plugin.json
├── skills/dependency-mapping/SKILL.md
├── skills/launch-readiness-review/SKILL.md
└── skills/program-charter/SKILL.md

Included Skills3

dependency-mappingskills/dependency-mapping/SKILL.md

Build the cross-team dependency graph and derive the critical path — every handoff gets a producer, consumer, due date, and interface contract; cycles and single points of failure get flagged. Use when a program spans multiple teams and you need to know what actually decides the date.

launch-readiness-reviewskills/launch-readiness-review/SKILL.md

Run a go/no-go launch-readiness review against written, pre-agreed criteria and design a staged rollout with a tested rollback. Use as a launch approaches — define measurable, owner-assigned criteria first, then facilitate the decision and record any waiver with its risk acceptance.

program-charterskills/program-charter/SKILL.md

Turn a fuzzy cross-team mandate into a chartered program — a measurable outcome, a named sponsor, explicit in/out-of-scope boundaries, the teams on the hook, and the starting RAID. Use at the very start, before any planning, whenever a multi-team effort lacks a clear outcome or owner.

Plugin manifests1

plugins/technical-program-management/.claude-plugin/plugin.json

{
  "name": "technical-program-management",
  "version": "0.1.2",
  "description": "Technical-program-management team — agents (technical-program-manager, cross-team-dependency-manager, program-launch-coordinator) for delivering a program of projects across teams: program charter + measurable outcomes, dependency mapping and critical-path/integration risk, a RAID-driven program plan, launch-readiness reviews with written go/no-go criteria, staged rollout, and exec status comms that lead with decisions and asks (not activity). skills, a knowledge bank with Mermaid decision trees (TPM-vs-PM-vs-EM, escalate-or-not, go/no-go), best-practices, templates, commands, and an advisory anti-pattern hook. Distinct from project-management (a single project/plan) and engineering-management (people/teams); execution lands in devops-cicd, observability-sre, and the relevant engineering plugins. Requires ravenclaude-core@>=0.7.0.",
  "author": {
    "name": "Matt Corbett"
  },
  "homepage": "https://github.com/mcorbett51090/RavenClaude",
  "license": "MIT",
  "keywords": [
    "technical-program-management",
    "tpm",
    "program-management",
    "cross-team-delivery",
    "dependency-management",
    "critical-path",
    "raid-log",
    "launch-readiness",
    "go-no-go",
    "rollout",
    "program-status",
    "escalation",
    "stakeholder-comms",
    "program-charter"
  ],
  "requires": {
    "plugins": [
      "ravenclaude-core@>=0.7.0"
    ]
  }
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[technical-program-management on Agent Plugins Marketplace](https://pluginsmp.com/plugins/technical-program-management)