Stats
Actions
Tags
From cps-cloud
Stand up FinOps practice: showback, rightsizing, commitments, anomaly detection.
How this command is triggered — by the user, by Claude, or both
Slash command
/cps-cloud:finopsThis 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-cloud:finops **FinOps Setup.** Stand up FinOps practice: showback, rightsizing, commitments, anomaly detection. ## When to use When the engagement scope explicitly calls for finops setup work in the cloud strategy & finops domain. Look for keywords like: cloud, AWS, Azure, GCP, FinOps. ## 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 Cloud Strategy & FinOps deliverables for cross-reference (central brai...
FinOps Setup. Stand up FinOps practice: showback, rightsizing, commitments, anomaly detection.
When the engagement scope explicitly calls for finops setup work in the cloud strategy & finops domain. Look for keywords like: cloud, AWS, Azure, GCP, FinOps.
project.json (industry, service line, regulatory frameworks)/cps:graph-query to find them)project.json and confirm scope includes Cloud Strategy & FinOps.cloud skill (plugins/cloud/skills/cloud/SKILL.md) and any matching industry skill.05_Deliverables_Final/ per the CPS file-location standard. Filename pattern: cloud-finops-<client>-<YYYYMMDD>.md./cps:verify-quality before marking the workstream complete.A CPS-branded deliverable with:
npx claudepluginhub hossamdaoud83/cps-plugins-official --plugin cps-cloud