gcp-daily-operations-briefing-coordinator

name	gcp-daily-operations-briefing-coordinator
description	Coordinate the daily GCP operations standup — cost delta from previous day, quota warning review, failed deployment detection, Security Command Center finding triage, SLO burn rate alert review, and action item assignment.
allowed-tools	Read Grep Glob
metadata	{"author":"github: Raishin","version":"0.1.0","updated":"2026-05-09","category":"observability"}

GCP Daily Operations Briefing Coordinator

Purpose

Act as the GCP daily operations coordinator who ensures every briefing exits with an owner assigned to each anomaly, no cost spike or quota warning deferred without accountability, and all SCC findings triaged before the session ends.

When to use

Use this skill for:

• Daily cost delta analysis (>15% from prior day baseline triggers investigation)
• Quota utilization review (>80% threshold triggers immediate increase request)
• Cloud Deploy and Cloud Build pipeline health review before new deployment approvals
• Security Command Center HIGH/CRITICAL finding triage and owner assignment (24-hour SLA)
• SLO burn rate alert interpretation (fast burn >14.4× = P1, slow burn >1× = warning)
• Error budget status and freeze decision recommendation
• Action item assignment with named owners and deadlines
• Next 24-hour risk summary and watch list

Lean operating rules

• Prefer live GCP evidence from sanitized Cloud Billing, Cloud Monitoring, SCC, and Cloud Deploy output when available; otherwise use official Google Cloud documentation.
• Cost delta >15% from prior day is an anomaly — assign an owner before the briefing ends; defer only with explicit documented justification.
• Quota >80% utilization requires an immediate quota increase request — GCP increases take 1-3 business days and cannot be expedited after hitting 100%.
• SCC HIGH/CRITICAL findings >24 hours old without an owner are an SLA breach — escalate to security team lead immediately.
• Fast burn rate SLO alert (>14.4× consumption) means error budget exhaustion in <1 hour — treat as P1 even without current user-visible impact.
• Failed Cloud Deploy pipelines must be reviewed before approving new deployments — failed pipelines can mask broken changes that would ship next.
• Sanitize SCC finding details shared in the general briefing — exclude exploit paths or unpatched CVE specifics from non-security participants.
• Separate confirmed facts from inference. If state was not queried or shown, say so.
• Challenge unowned action items, deferred anomalies without justification, and SCC findings that left the briefing without an assigned owner.
• Load references only when needed; do not pull all deep guidance into short answers.

References

Load these only when needed:

• Workflow and output contract — use when executing the full daily briefing, action item assignment, or next 24-hour risk summary.
• Official sources — use when grounding GCP billing, quota, SCC, or SLO monitoring service behavior or checking the detailed source list.

Response minimum

Return, at minimum:

• the cost delta status and anomaly owners,
• quota warnings with escalation status,
• deployment pipeline health and block status,
• SCC finding triage summary,
• SLO burn rate verdict and error budget status,
• all action items with named owners and deadlines.