ring%3ausing-pmo-team（环%3 使用 PMO 团队）

Using Ring PMO Team

The ring-pmo-team plugin provides 6 specialized PMO agents for portfolio-level management. Use them via Task tool with subagent_type: "ring:agent-name".

See CLAUDE.md and ring:using-ring for canonical workflow requirements and ORCHESTRATOR principle. This skill introduces pmo-team-specific agents.

Remember: Follow the ORCHESTRATOR principle from ring:using-ring. Dispatch agents to handle complexity; don't operate tools directly.

Domain Distinction: PMO vs PM

Use PMO when:

• Managing multiple projects simultaneously
• Planning resources across projects
• Reporting to executives on portfolio status
• Assessing portfolio-level risks
• Conducting governance reviews

Use PM when:

• Planning a single feature
• Creating PRD/TRD for one initiative
• Breaking down one feature into tasks

Blocker Criteria - STOP and Report

ALWAYS pause and report blocker for:

You CANNOT make strategic or resource decisions autonomously. STOP and ask.

Common Misconceptions - REJECTED

Self-sufficiency bias check: If you're tempted to perform PMO tasks directly, ask:

1. Is there a specialist for this? (Check the 6 specialists below)
2. Would a specialist apply portfolio-level frameworks I might miss?
3. Am I avoiding dispatch because it feels like "overhead"?

If ANY answer is yes → You MUST DISPATCH the specialist. This is NON-NEGOTIABLE.

Anti-Rationalization Table

If you catch yourself thinking ANY of these, STOP:

See shared-patterns/anti-rationalization.md for universal anti-rationalizations.

Cannot Be Overridden

These requirements are NON-NEGOTIABLE:

User cannot override these. Executive pressure cannot override these. "Urgent" cannot override these.

Pressure Resistance

When facing pressure to bypass PMO process:

See shared-patterns/pressure-resistance.md for universal pressure scenarios.

Critical Reminder:

• Urgency ≠ Permission to bypass - Urgent projects need MORE PMO oversight
• Authority ≠ Permission to bypass - Executives expect PMO rigor
• Agile ≠ No governance - Agile has governance, just different cadence

Emergency Response Protocol

Critical situations DO NOT bypass PMO process. Here's why:

Emergency Dispatch Template:

Task tool:
  subagent_type: "ring:portfolio-manager"
  prompt: "URGENT: [context]. [specific request]"

IMPORTANT:

• Specialist dispatch takes 10-20 minutes, NOT hours
• Rushed PMO decisions often create NEW problems
• Specialists ensure crisis decisions don't violate governance
• This is NON-NEGOTIABLE even under board pressure

6 PMO Specialists

Dispatch template:

Task tool:
  subagent_type: "ring:{agent-name}"
  prompt: "{Your specific request with context}"

When to Use PMO Specialists vs Other Teams

Use PMO Specialists for:

• Portfolio-level analysis and decisions
• Resource planning across multiple projects
• Governance and gate reviews
• Executive and board reporting
• Portfolio risk management

Use PM Team (ring-pm-team) for:

• Single feature planning
• PRD/TRD creation
• Task breakdown for one feature
• Feature-level research

Use Dev Team (ring-dev-team) for:

• Code implementation
• Technical architecture
• DevOps and infrastructure
• Quality assurance

Teams work together: PMO provides portfolio context → PM plans features → Dev implements code.

Dispatching Multiple Specialists

If you need multiple specialists (e.g., portfolio-manager + risk-analyst), dispatch in parallel (single message, multiple Task calls):

CORRECT:
Task #1: ring:portfolio-manager
Task #2: ring:risk-analyst
(Both run in parallel)

WRONG:
Task #1: ring:portfolio-manager
(Wait for response)
Task #2: ring:risk-analyst
(Sequential = 2x slower)

ORCHESTRATOR Principle

Remember:

• You're the orchestrator - Dispatch specialists, don't analyze directly
• Don't read PMO frameworks yourself - Dispatch to specialist, they know their domain
• Combine with other plugins - PMO + PM + Dev = complete delivery lifecycle

Good Example (ORCHESTRATOR):

"I need portfolio status. Let me dispatch ring:portfolio-manager to analyze."

Bad Example (OPERATOR):

"I'll manually review each project and create a summary myself."

Available in This Plugin

Agents (6):

• ring:portfolio-manager (Multi-project coordination, strategic alignment, portfolio health)
• ring:resource-planner (Capacity planning, skills matrix, allocation optimization)
• ring:governance-specialist (Gate reviews, compliance, process adherence, audit readiness)
• ring:risk-analyst (RAID logs, risk aggregation, mitigation planning, portfolio risk)
• ring:executive-reporter (Portfolio status dashboards, project summaries, board packages)
• ring:delivery-reporter (Git analysis, squad delivery showcases, visual HTML presentations)

Skills (9):

• ring:using-pmo-team (this skill - plugin introduction and dispatch guide)
• ring:portfolio-planning (Strategic portfolio planning, capacity assessment, optimization)
• ring:portfolio-review (Comprehensive portfolio review - dispatches 4 specialists in parallel)
• ring:resource-allocation (Resource capacity planning and allocation across projects)
• ring:risk-management (Portfolio-level risk identification, assessment, and mitigation)
• ring:project-health-check (Individual project health assessment across multiple dimensions)
• ring:dependency-analysis (Cross-project dependency mapping and management)
• ring:executive-summary (Executive dashboards, status summaries, and board packages)
• ring:pmo-retrospective (Portfolio retrospectives and lessons learned)

Note: Missing agents? Check .claude-plugin/marketplace.json for ring-pmo-team plugin.

PMO Workflows

Report Type Selection Guide

Use ring:executive-summary for:

• Portfolio health dashboards
• Project status updates (RAG, SPI, CPI)
• Board packages with governance focus
• Resource and budget tracking

For squad delivery reports, use the ring:delivery-reporter agent directly.

Integration with Other Plugins

• ring-default - ORCHESTRATOR principle for ALL agents
• ring-pm-team - Single feature planning (PMO → PM handoff)
• ring-dev-team - Development execution (PM → Dev handoff)
• ring-finops-team - Financial/regulatory compliance

Dispatch based on your need:

• Portfolio oversight → ring-pmo-team
• Feature planning → ring-pm-team
• Code development → ring-dev-team
• Financial compliance → ring-finops-team