cloud-cost-governance

Identify and contain unexpected cloud cost spikes across AWS, GCP, and Azure.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/s3nex-com/sdlc-skills-library --skill cloud-cost-governance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloud-cost-governance
Source: https://github.com/s3nex-com/sdlc-skills-library/tree/main/skills/phase3/cloud-cost-governance
Command: npx skills add https://github.com/s3nex-com/sdlc-skills-library --skill cloud-cost-governance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Cloud costs are real and often invisible on small teams until the bill arrives. This skill makes cloud spending governance a first-class engineering concern by attribution (who owns what cost), per-feature estimation, governance (budget alerts with defined response), and a playbook for monthly optimization and anomaly handling.

Core Features & Use Cases

  • Cost attribution & tagging enforcement: Tag every cloud resource and enforce in IaC so spend can be allocated to project/feature/environment.
  • Per-feature cost estimates in PRDs: Include cost NFRs at design time and compare actual monthly spend to estimates.
  • Monthly optimization audits: 30-minute cadence audits covering right-sizing, reservations, orphaned resources, and anomaly response to optimize spend.
  • Anomaly detection & governance: Budget alerts at 80% and a defined playbook to identify, contain, and communicate cost spikes.

Quick Start

Run the monthly cloud cost audit and post the Cloud Cost Audit report to the team channel.

Frequently Asked Questions about cloud-cost-governance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I attribute cloud spend to specific features and environments?

You can attribute cloud spend by enforcing resource tagging in your IaC to allocate costs to specific projects, features, and environments. This allows you to compare actual monthly spend against per-feature cost estimates defined in your PRDs.

What is the best way to detect and respond to unexpected cloud cost spikes?

The best way to handle unexpected cloud cost spikes is by setting budget alerts at 80% and applying a defined anomaly response playbook. This approach helps you quickly identify, contain, and communicate cost spikes across AWS, GCP, and Azure.

How do I run a monthly cloud cost optimization audit?

You run a monthly cloud cost optimization audit by reviewing right-sizing, reservations, and orphaned resources within a 30-minute cadence. This process generates an actionable Cloud Cost Audit report to drive ongoing spend governance.

Can I enforce cloud cost governance during the design phase of new services?

Yes, you can enforce cloud cost governance at design time by including cost non-functional requirements in PRDs. This acts as a design-time cost gate to estimate per-feature costs before deploying new services.

Does this approach to cost governance work across AWS, GCP, and Azure?

Yes, this cloud cost governance approach applies workflows across AWS, GCP, and Azure. It guides tagging enforcement, right-sizing, and anomaly response uniformly to help you optimize spend regardless of your specific cloud provider.