Slash Command

/portfolio-prioritize

From cps-pmo

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

Invocation

How this command is triggered — by the user, by Claude, or both

Slash command

/cps-pmo:portfolio-prioritize

Model invocable

No pre-commands

Tool Access

This command is limited to the following tools:

ReadWriteEditGlobGrepBash

Context Preview

The summary Claude sees in its command listing — used to decide when to auto-load this command

# /cps-pmo:portfolio-prioritize

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

## When to use

When the engagement scope explicitly calls for portfolio prioritization work in the pmo & program delivery domain. Look for keywords like: PMO, portfolio, program, project, RAID.

## Inputs you should gather first

- The engagement `project.json` (industry, service line, regulatory frameworks)
- Relevant client documents already ingested into the brain (run `/cps:graph-query` to find them)
- Any prior CPS PMO & Program Delivery delive...

Command Content

42 lines · ~466 tokens

Stats

LanguageJavaScript

Parent stars0

MaintenanceGood

Last CommitMay 25, 2026

Actions

View Source View Plugin View on GitHub View README

Stats

Actions

/cps-pmo:portfolio-prioritize

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

When to use

When the engagement scope explicitly calls for portfolio prioritization work in the pmo & program delivery domain. Look for keywords like: PMO, portfolio, program, project, RAID.

Inputs you should gather first

The engagement project.json (industry, service line, regulatory frameworks)
Relevant client documents already ingested into the brain (run /cps:graph-query to find them)
Any prior CPS PMO & Program Delivery deliverables for cross-reference (central brain)

Steps

Read the engagement project.json and confirm scope includes PMO & Program Delivery.
Load the pmo skill (plugins/pmo/skills/pmo/SKILL.md) and any matching industry skill.
Use the relevant subagent(s) — see Integration table below — to do the analysis.
Apply the methodology described in the skill, citing all sources.
Place the deliverable in 05_Deliverables_Final/ per the CPS file-location standard. Filename pattern: pmo-portfolio-prioritize-<client>-<YYYYMMDD>.md.
Run /cps:verify-quality before marking the workstream complete.

Output shape

A CPS-branded deliverable with:

Pyramid-Principle structure (recommendation up front)
Source citations on every data point
Recommendation Format used in any advice section
Quality bar items below all checked

Quality bar

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