pmo

PMO — PMO & Program Delivery

Capability overview

Code: PMO Full name: PMO & Program Delivery Description: PMO setup, portfolio governance, program management, RAID logs, status pack automation, gate reviews.

---

Skills index

#	Skill	Command	Purpose
1	PMO Setup	/cps-pmo:pmo-setup	Stand up a PMO: charter, operating model, governance, tools.
2	Portfolio Prioritization	/cps-pmo:portfolio-prioritize	Score and rank initiatives using strategic-fit, value, and feasibility lenses.
3	Program Charter	/cps-pmo:program-charter	Author program charter: scope, objectives, governance, RAID, success criteria.
4	Status Pack	/cps-pmo:status-pack	Author weekly/monthly status pack from tracker state.
5	Stage-Gate Review	/cps-pmo:gate-review	Facilitate stage-gate review with scorecard and go/no-go decision.
6	RAID Cleanup	/cps-pmo:raid-cleanup	Audit RAID log for stale items; drive resolution and aging-out.

---

Skill 1: PMO Setup

Command: /cps-pmo:pmo-setup

Purpose

Stand up a PMO: charter, operating model, governance, tools.

Inputs required

client:
  name: "Client Name"
  industry: "Industry"
context:
  scope: "in-scope description"
  constraints: ["constraint 1", "constraint 2"]
references:
  - "Prior deliverable / document name"
  - "External benchmark / source"

Methodology

1. Frame. Translate client request into a structured problem statement and hypotheses.
2. Gather. Pull data from engagement brain, client documents, and external sources.
3. Analyze. Apply the PMO Setup method using domain frameworks (see Frameworks section of the agent).
4. Synthesize. Produce primary deliverable with recommendations, evidence, and risks.
5. Validate. Run /cps:verify-quality and pass through Every program has a charter with objectives, governance, scope, and named sponsor.

Output shape

A CPS-branded PMO Setup deliverable in 05_Deliverables_Final/. Pyramid-Principle structured, sourced, and reviewed.

Quality checklist

• Every program has a charter with objectives, governance, scope, and named sponsor
• RAID items have owner + due date + aging; nothing untouched > 14 days
• Status packs have a 3-bullet headline, decisions-needed section, and 2-week look-ahead

---

Skill 2: Portfolio Prioritization

Command: /cps-pmo:portfolio-prioritize

Purpose

Score and rank initiatives using strategic-fit, value, and feasibility lenses.

Inputs required

client:
  name: "Client Name"
  industry: "Industry"
context:
  scope: "in-scope description"
  constraints: ["constraint 1", "constraint 2"]
references:
  - "Prior deliverable / document name"
  - "External benchmark / source"

Methodology

1. Frame. Translate client request into a structured problem statement and hypotheses.
2. Gather. Pull data from engagement brain, client documents, and external sources.
3. Analyze. Apply the Portfolio Prioritization method using domain frameworks (see Frameworks section of the agent).
4. Synthesize. Produce primary deliverable with recommendations, evidence, and risks.
5. Validate. Run /cps:verify-quality and pass through Every program has a charter with objectives, governance, scope, and named sponsor.

Output shape

A CPS-branded Portfolio Prioritization deliverable in 05_Deliverables_Final/. Pyramid-Principle structured, sourced, and reviewed.

Quality checklist

• Every program has a charter with objectives, governance, scope, and named sponsor
• RAID items have owner + due date + aging; nothing untouched > 14 days
• Status packs have a 3-bullet headline, decisions-needed section, and 2-week look-ahead

---

Skill 3: Program Charter

Command: /cps-pmo:program-charter

Purpose

Author program charter: scope, objectives, governance, RAID, success criteria.

Inputs required

client:
  name: "Client Name"
  industry: "Industry"
context:
  scope: "in-scope description"
  constraints: ["constraint 1", "constraint 2"]
references:
  - "Prior deliverable / document name"
  - "External benchmark / source"

Methodology

1. Frame. Translate client request into a structured problem statement and hypotheses.
2. Gather. Pull data from engagement brain, client documents, and external sources.
3. Analyze. Apply the Program Charter method using domain frameworks (see Frameworks section of the agent).
4. Synthesize. Produce primary deliverable with recommendations, evidence, and risks.
5. Validate. Run /cps:verify-quality and pass through Every program has a charter with objectives, governance, scope, and named sponsor.

Output shape

A CPS-branded Program Charter deliverable in 05_Deliverables_Final/. Pyramid-Principle structured, sourced, and reviewed.

Quality checklist

• Every program has a charter with objectives, governance, scope, and named sponsor
• RAID items have owner + due date + aging; nothing untouched > 14 days
• Status packs have a 3-bullet headline, decisions-needed section, and 2-week look-ahead

---

Skill 4: Status Pack

Command: /cps-pmo:status-pack

Purpose

Author weekly/monthly status pack from tracker state.

Inputs required

client:
  name: "Client Name"
  industry: "Industry"
context:
  scope: "in-scope description"
  constraints: ["constraint 1", "constraint 2"]
references:
  - "Prior deliverable / document name"
  - "External benchmark / source"

Methodology

1. Frame. Translate client request into a structured problem statement and hypotheses.
2. Gather. Pull data from engagement brain, client documents, and external sources.
3. Analyze. Apply the Status Pack method using domain frameworks (see Frameworks section of the agent).
4. Synthesize. Produce primary deliverable with recommendations, evidence, and risks.
5. Validate. Run /cps:verify-quality and pass through Every program has a charter with objectives, governance, scope, and named sponsor.

Output shape

A CPS-branded Status Pack deliverable in 05_Deliverables_Final/. Pyramid-Principle structured, sourced, and reviewed.

Quality checklist

• Every program has a charter with objectives, governance, scope, and named sponsor
• RAID items have owner + due date + aging; nothing untouched > 14 days
• Status packs have a 3-bullet headline, decisions-needed section, and 2-week look-ahead

---

Skill 5: Stage-Gate Review

Command: /cps-pmo:gate-review

Purpose

Facilitate stage-gate review with scorecard and go/no-go decision.

Inputs required

client:
  name: "Client Name"
  industry: "Industry"
context:
  scope: "in-scope description"
  constraints: ["constraint 1", "constraint 2"]
references:
  - "Prior deliverable / document name"
  - "External benchmark / source"

Methodology

1. Frame. Translate client request into a structured problem statement and hypotheses.
2. Gather. Pull data from engagement brain, client documents, and external sources.
3. Analyze. Apply the Stage-Gate Review method using domain frameworks (see Frameworks section of the agent).
4. Synthesize. Produce primary deliverable with recommendations, evidence, and risks.
5. Validate. Run /cps:verify-quality and pass through Every program has a charter with objectives, governance, scope, and named sponsor.

Output shape

A CPS-branded Stage-Gate Review deliverable in 05_Deliverables_Final/. Pyramid-Principle structured, sourced, and reviewed.

Quality checklist

• Every program has a charter with objectives, governance, scope, and named sponsor
• RAID items have owner + due date + aging; nothing untouched > 14 days
• Status packs have a 3-bullet headline, decisions-needed section, and 2-week look-ahead

---

Skill 6: RAID Cleanup

Command: /cps-pmo:raid-cleanup

Purpose

Audit RAID log for stale items; drive resolution and aging-out.

Inputs required

client:
  name: "Client Name"
  industry: "Industry"
context:
  scope: "in-scope description"
  constraints: ["constraint 1", "constraint 2"]
references:
  - "Prior deliverable / document name"
  - "External benchmark / source"

Methodology

1. Frame. Translate client request into a structured problem statement and hypotheses.
2. Gather. Pull data from engagement brain, client documents, and external sources.
3. Analyze. Apply the RAID Cleanup method using domain frameworks (see Frameworks section of the agent).
4. Synthesize. Produce primary deliverable with recommendations, evidence, and risks.
5. Validate. Run /cps:verify-quality and pass through Every program has a charter with objectives, governance, scope, and named sponsor.

Output shape

A CPS-branded RAID Cleanup deliverable in 05_Deliverables_Final/. Pyramid-Principle structured, sourced, and reviewed.

Quality checklist

• Every program has a charter with objectives, governance, scope, and named sponsor
• RAID items have owner + due date + aging; nothing untouched > 14 days
• Status packs have a 3-bullet headline, decisions-needed section, and 2-week look-ahead

---

Cross-skill workflows

Discovery → /cps-pmo:pmo-setup → /cps-pmo:portfolio-prioritize → Recommendations

Integration with other CPS plugins

Plugin	Integration point
cps-risk	RAID issue/risk feeds into the enterprise risk register
cps-dig	PMO supporting digital transformation programs
cps-finance	Portfolio investment and benefit tracking

Templates & artifacts

All deliverables use standard CPS branding via:

• /doc-gen for document generation
• assets/cps-branding.json for styling
• scripts/cps-document-generator.js for automation

Skill	Primary artifact	Format
/cps-pmo:pmo-setup	PMO Setup Report	DOCX/PDF
/cps-pmo:portfolio-prioritize	Portfolio Prioritization Report	DOCX/PDF
/cps-pmo:program-charter	Program Charter Report	DOCX/PDF
/cps-pmo:status-pack	Status Pack Report	DOCX/PDF
/cps-pmo:gate-review	Stage-Gate Review Report	DOCX/PDF
/cps-pmo:raid-cleanup	RAID Cleanup Report	DOCX/PDF