gcp-hcp

Guided exploration of the HostedCluster create flow from API types through GKE provisioning

Process GCP HCP meeting notes/transcripts into reviewed Jira updates — extracts action items, presents changes for approval, executes via MCP, and generates a Slack summary.

Use when working on GCP HCP-related code or design in any of the GCP HCP repositories: hypershift (platform/gcp/, GCP provider, GCP-related tests), gcp-hcp-infra (Terraform, ArgoCD, infrastructure), gcp-hcp-cli, cls-backend, cls-controller, or when creating or reviewing design decisions, or needing architectural context for GCP Hosted Control Planes on GKE. Accepts optional topic filter: networking, identity, observability, infrastructure, automation, governance, storage, operators, testing, incidents, slo.

Post a biweekly Agentic SDLC pilot update comment to GCP-579, gathering Jira and GitHub activity for the lookback period.

Use when adding a new GCP service account for Workload Identity Federation (WIF) in HyperShift and related GCP HCP repositories. Covers e2e plumbing, CI pipeline, API types, IAM bindings, CRD regeneration, CLS backend/controller propagation, and CLI updates across hypershift, openshift/release, gcp-hcp-infra, cls-backend, cls-controller, and gcp-hcp-cli.

Use when an implementation plan in gcp-hcp may have drifted from actual code, or when code may have drifted from the plan's design intent. Typically after a feature has landed or a PR has merged. Checks API surface, behavior, interfaces, and structure across repositories.