One-click install
npx skills add https://github.com/konglong87/superPM --skill pm-cross
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-cross
Source: https://github.com/konglong87/superPM/tree/main/skills/04-risk-management/pm-cross
Command: npx skills add https://github.com/konglong87/superPM --skill pm-cross

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you define how multiple departments should collaborate so cross-team work doesn’t stall after a technical plan is decided.

Core Features & Use Cases

  • Cross-department participation discovery: Identify which departments must be involved for the current project.
  • Collaboration workflow design: Choose collaboration strictness and define dependencies (sequential, parallel, mixed).
  • Communication & responsibility clarity (RACI): Design meeting cadence and information-sharing channels, then produce a RACI matrix and a complete collaboration方案 document.

Use Case: After finishing a technical方案, product can’t get consistent alignment from R&D, design, testing, and other teams; use this Skill to produce a cross-department协作方案 and RACI职责分工 so everyone knows what to do, when, and how to communicate.

Quick Start

Tell the assistant: “Use pm-cross to create a cross-department collaboration plan with RACI for my project after the technical方案 is finalized.”

Frequently Asked Questions about pm-cross

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

FAQPage Schema
How do I create a cross-department collaboration plan with a RACI matrix for product management?

Create a cross-department collaboration plan by collecting involved departments, dependency types, and communication channels to generate a workflow and RACI matrix. This defines clear responsibilities so cross-team product execution doesn't stall after technical decisions.

What is a RACI responsibility matrix and when do I need it for cross-team collaboration?

A RACI responsibility matrix clarifies who is Responsible, Accountable, Consulted, and Informed across departments. You need it when multi-team project roles are unclear, causing alignment issues between R&D, design, and testing teams during reviews or launches.

How to design a cross-team workflow for technical reviews and product launch readiness?

Design a cross-team workflow by defining collaboration strictness and mapping sequential or parallel dependencies. Establish meeting cadence and information synchronization channels to ensure all departments align during technical reviews, design checks, and launch readiness.

How do I align stakeholders and define decision ownership across multiple project teams?

Align stakeholders by establishing clear decision ownership and setting a regular meeting cadence for information synchronization. Defining communication channels and role responsibilities ensures consistent alignment across R&D, design, and testing teams.

What information do I need to generate a cross-department collaboration workflow?

To generate a cross-department collaboration workflow, you need to collect involved departments, collaboration scenarios, workflow strictness, dependency types, meeting cadence, and decision ownership to produce a complete RACI collaboration document.

Does this collaboration planning approach work for ongoing issue resolution and testing reviews?

Yes, this approach works for ongoing issue resolution and testing reviews. It maps department roles and communication channels to handle multi-team execution complexity, ensuring continuous alignment throughout the product lifecycle.