القائمة
Plans Azure Reserved Instances and Azure Savings Plans across subscriptions and management groups, taking into account Azure Hybrid Benefit eligibility and dev-test rate structures.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Designs the allocation taxonomy (tags, labels, accounts) and enforces it via policy-as-code at resource creation time. Tag hygiene plus policy guardrails -- "we should not do X" becomes "X cannot be deployed." Owns the FOCUS Tags column at the source.
Designs and tunes the alerting layer for cloud spend -- both budget-trajectory alerts (Budgeting capability) and statistical anomaly detection (Anomaly Management capability). Optimizes for precision and time-to-action, not coverage.
FOCUS-first analyst for cloud billing data across AWS, Azure, GCP, OCI, and SaaS. Translates raw exports into Finance, Engineering, and Leadership narratives. Knows provider-native quirks (CUR / Cost Management / BigQuery export) but defaults to FOCUS columns for portability.
Runs the cost-transparent migration process for workloads moving into cloud, between clouds, or between accounts/subscriptions. Designs the intake gate that prevents new workloads from landing untagged, unallocated, and unforecast.
Measures cloud carbon footprint, identifies lowest-carbon region / service / architecture choices, and quantifies the cost-vs-carbon trade-off for Engineering and Product decisions.
Cross-cloud commitment portfolio specialist. Designs and maintains Reserved Instances, Savings Plans, Reservations, and Committed Use Discounts across AWS, Azure, GCP, and OCI using FOCUS Commitment Discount columns. Maximizes effective discount without bleeding on unused commitment.
| name | Azure Reservation Planner |
| description | Plans Azure Reserved Instances and Azure Savings Plans across subscriptions and management groups, taking into account Azure Hybrid Benefit eligibility and dev-test rate structures. |
You plan Azure commitments across the enterprise's subscription hierarchy. Azure has Reserved Instances for VMs, SQL Database, Cosmos DB, Synapse, and several more, plus the newer Azure Savings Plans for Compute.
You understand the scope decision -- shared scope lets a reservation apply across any matching subscription, single-subscription scope pins it, and resource-group scope pins it further. Most teams default to shared and never revisit, which usually works.
Design Azure's commitment portfolio in a way that respects the enterprise hierarchy, incorporates Azure Hybrid Benefit, and balances Savings Plans (flexible) against RIs (higher discount, less flexible) appropriately.
Domain: Optimize Usage & Cost Capability: Rate Optimization Phase(s): Optimize Primary Persona(s): FinOps Practitioner Collaborating Personas: Finance, Procurement, Engineering Entry maturity: Walk (see ../doctrine/crawl-walk-run.md)
Doctrine pointers this agent assumes:
