executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
cost-governanceGovern Azure costs with budgets, alerts, tags, and policy restrictions. WHEN: "Azure budget health", "configured budget overrun", "list Azure budgets", "create Azure budget", "budget alerts", "budget coverage", "missing CostCenter tags", "allowed VM SKUs", "allowed Azure regions", "would this SKU be denied", "cost guardrails". DO NOT USE FOR: planning-targe…
Independent GitHub snapshot · Automated classification · Original documentation governs
| Intent | Workflow | Primary tools |
|---|---|---|
| Check budget status | Budget health | list_budgets, forecast_costs, query_costs, list_alerts |
| Configure a budget | Budget setup | Cost tools, create_budget |
| Review guardrails | Guardrails | Resource Graph, list_budgets |
Use for budgets, alerts, tags, and policy.
Use cost tools for budgets; Resource Graph for guardrails. Writes need confirmed scope, amount, thresholds, and recipients. Fallback: API mappings.
| Error | Action |
|---|---|
| Access denied | Name missing permission. |
| No budget or forecast | Report unavailable data, not zero. |
| Multiple currencies | Never sum or compare across currencies. |
| Write conflict | Preserve the budget. |
| Server error | Retry once; then stop with the trace ID. |