agent-control-plane

Install and verify Ambient Code Platform on an OpenShift cluster using quay.io images. Use when deploying Ambient to any OpenShift namespace — production, ephemeral PR test instances, or developer clusters. Covers secrets, kustomize deploy, rollout verification, and troubleshooting.

Deploy a PR's images (api-server, control-plane, runner) to any OpenShift namespace for integration testing. Supports full SSO deployments (install-openshift.sh) and lightweight dev-mode deployments (install-standard.sh).

Log one or more Jira issues to the ENGPROD project with the acp component pre-filled. Gathers context to make issues agent-actionable from cold start. Use this whenever work needs tracking in Jira -- creating stories, filing bugs, logging tasks, opening spikes, creating epics, or any time the user says "create a jira", "log this", "file a bug", "new ticket", "open a story", "track this", "create tickets", "batch create", or provides a bullet list of work items. Supports single tickets and batch creation from bullet lists. Triggers on: "log jira", "create jira", "file a bug", "new ticket", "open a story", "jira issue", "track this work", "open a jira", "create a ticket", "create tickets", "batch tickets", "log these items".

Deploy a Kind cluster with OpenShell gateway mode, apply tenant fleet definitions via acpctl apply -k, set up Vertex/Google credentials, spin up sandbox sessions, and configure local openshell CLI connectivity. Use this skill whenever the user wants to test gateway-provisioned sandboxes, create credentials in tenants, debug sandbox provisioning, connect the openshell CLI to a gateway, or run dual-tenant tests. You SHOULD reach for this skill on: "kind-up", "kind cluster", "openshell gateway", "gateway mode", "OPENSHELL_USE_GATEWAY", "sandbox provisioning", "dual-tenant", "tenant-a", "tenant-b", "vertex credential", "spin up a sandbox", "credential in tenant", "openshell sandbox list", "gateway connectivity", "connect to the gateway", "mtls", "port-forward gateway", "acpctl apply -k", "local development".

Upgrade the rh-trex-ai upstream framework dependency in ambient-api-server. Handles version bump, compilation verification, breaking change detection, test execution, and go.sum cleanup. Use when: "upgrade rh-trex-ai", "bump upstream", "update trex", "new upstream version", "upgrade framework", "pull in upstream changes", "update rh-trex-ai to latest".

Top-level autonomous orchestrator that reconciles all specs against the codebase. Reads skills/RECONCILE.md for checkpoint state, runs field-level gap analysis, plans waves, and executes the full-stack-pipeline per wave. Idempotent: safe to run repeatedly -- produces the same result for the same spec+code state. Use when: "reconcile everything", "run full reconciliation", "what's the gap across all specs", "autonomous build", "just do it", "build everything", "reconcile specs to code", "spec coverage", "what's left to implement", "implementation status".

Manages Ambient Code Platform development clusters (kind) for testing changes locally. Use when deploying PRs to kind, bringing up local clusters, rebuilding images, troubleshooting pod issues, or running benchmarks. Triggers on: "test in kind", "deploy locally", "kind cluster", "rebuild images", "pod crashing", "bring up cluster", "kind-up", "dev environment", "local dev".

Comprehensive workflow to audit the `ambient-ui` component's ui & ux. Use after any changes are made to the `ambient-ui` user interface.

Autonomous workflow for implementing spec-driven changes across the Ambient platform. Orchestrates gap analysis, wave-based execution, and cross-component integration. Use when: "implement this spec", "build this feature end-to-end", "run the pipeline", "gap analysis", "what waves do we need", "full-stack change".

Create or modify a spec following the project's spec format and conventions. Use when the user wants to write a new spec, add requirements or scenarios to an existing spec, or restructure spec content. Triggers on: "write a spec", "create a spec", "add a requirement", "spec this out", "define the behavior", "what should the spec look like", "new spec for", "update the spec".

ACP-specific review standards to apply alongside the upstream pr-review skill. Use when reviewing PRs in this repository. Loads project conventions, security requirements, and component-specific checklists that supplement the fleet pr-review workflow.