Stats
Actions
Tags
From cps-pmo
Facilitate stage-gate review with scorecard and go/no-go decision.
How this command is triggered — by the user, by Claude, or both
Slash command
/cps-pmo:gate-reviewThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /cps-pmo:gate-review **Stage-Gate Review.** Facilitate stage-gate review with scorecard and go/no-go decision. ## When to use When the engagement scope explicitly calls for stage-gate review 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...
Stage-Gate Review. Facilitate stage-gate review with scorecard and go/no-go decision.
When the engagement scope explicitly calls for stage-gate review work in the pmo & program delivery domain. Look for keywords like: PMO, portfolio, program, project, RAID.
project.json (industry, service line, regulatory frameworks)/cps:graph-query to find them)project.json and confirm scope includes PMO & Program Delivery.pmo skill (plugins/pmo/skills/pmo/SKILL.md) and any matching industry skill.05_Deliverables_Final/ per the CPS file-location standard. Filename pattern: pmo-gate-review-<client>-<YYYYMMDD>.md./cps:verify-quality before marking the workstream complete.A CPS-branded deliverable with:
npx claudepluginhub hossamdaoud83/cps-plugins-official --plugin cps-pmo/gate-reviewRuns dual-agent Gate 3.5 review on git-tracked code changes: builder self-assesses via checklist, spawns reviewer(s) for evaluation; both must approve.