akua-dev

Resolve, inspect, apply, verify, review or improve an AgentOS Agent composition. Use when selecting instructions, Skills, harness-native settings or capability requirements for a persistent Mate or bounded Assignment; loading an external composer or origin; reconciling desired and observed setup; collecting a composition debrief; or routing evidence into a separate improvement.

Select, configure, launch, inspect, resume, or change a verified AgentOS coding harness. Use before a First or Second Mate chooses a Crewmate harness, model or reasoning effort; before launching Pi or Codex through Herdr; or when harness authentication, flags, defaults, quota or recovery affect dispatch.

Inspect, create, and operate AgentOS runtime pods, Kustomize overlays, Herdr sessions, Mise toolchains, agent worktrees, terminals, PVCs, Kubernetes health, attach paths and runtime recovery. Use for normal First- or Second-Mate Kubernetes operations, child-Agent workload creation, tool resolution, stuck-agent debugging, remote terminal access, pod or session recovery, and readiness diagnosis.

Reconcile and supervise an AgentOS Mate's direct reports across PostgreSQL, Kubernetes, Herdr, PVCs, and Git. Use at every First- or Second-Mate session start, after restart or compaction, while delegated work is active, when Inbox or runtime state changes, and for blocked, stale, stuck, failed, interrupted, or recovering agents.

Inspect an environment and interactively establish or reconcile a persistent AgentOS First Mate in Kubernetes. Use only for first installation, a partial bootstrap, local-clone onboarding, cluster selection, or handoff from a temporary local agent to the cluster First Mate.

Charter, provision, route to, recover, change, and retire persistent AgentOS Second Mates. Use only from First Mate before any Second-Mate lifecycle operation, scope decision, charter handoff, runtime recovery, work transfer, configuration change, or retirement.

Inspect, provision, migrate, verify, and recover the AgentOS PostgreSQL database using released SQL assets. Use for database topology, schema versions, Fleet coordination, Tasks, Assignments, Inbox, Captain state, external-event reconciliation, roles, grants, RLS, Functions, Triggers, migration failures, or PostgreSQL bootstrap and recovery.

Route and deliver project-specific work through AgentOS Tasks, Assignments, Second Mates, ship Crewmates, and scout Crewmates. Use before accepting, planning, investigating, coding, auditing, assigning, briefing, spawning, merging, handing off, completing, or retiring delegated project work.

Set up a CI gate that runs akua diff on package upgrades and blocks merges that break schema compatibility or violate policy. Use when configuring CI for a platform repo, preventing breaking Helm-chart upgrades, gating Renovate or Dependabot PRs, or enforcing structural-compatibility checks before deployment.

Publish an akua Package to an OCI registry with cosign signature and SLSA v1 attestation. Use when releasing a package version, cutting a new release in CI, shipping to a production registry, meeting supply-chain requirements like SLSA Level 3, or setting up a signed-by-default publishing pipeline.

Set up tests, linting, formatting, coverage, and tracing for an akua workspace — for Packages (KCL) and Policies (Rego) together. Use when bootstrapping CI for a new platform repo, adding test coverage to an untested package, debugging a policy that denies unexpectedly, configuring a format/lint pre-commit hook, or when asked "add tests" / "set up CI gates" / "why is this policy failing?"

Audit a published akua Package or Helm chart before deploying it — schema, sources, cosign signature, SLSA attestation chain, rendered output with sample inputs. Use when evaluating a third-party package, checking signatures, verifying supply-chain provenance, or inspecting a chart from ArtifactHub, GHCR, or any OCI registry.

Convert an existing helmfile.yaml into a typed akua Package written in KCL. Use when migrating from Helmfile to akua, consolidating multi-release orchestration into a single package, replacing Helmfile's untyped templating with a typed schema, or moving a platform repo from helmfile apply to GitOps render-at-CI.

Scaffold a new akua Package in KCL with a typed input schema and Helm/KCL/kro sources. Use when the user wants to start a new cloud-native package, create a new app definition, set up akua for a project, or compose multiple upstream sources into one reusable package.

Rotate a shared secret across every install that references it. Use when a credential is compromised, during scheduled key rotation (e.g., 30-day policy), when an API token expires, or when adopting a new signing key across a fleet. Handles fan-out to all consumers, policy-gated rollout, and audit trail.

Subscribe to a curated policy tier (dev, startup, production, soc2, hipaa, fedramp-moderate) and apply it across a workspace. Use when preparing for a compliance audit, hardening a production environment, standardizing guardrails across teams, onboarding a new environment, or when a user asks "make this SOC2-ready" / "apply production policy".

Guide agents working with Akua documentation, workspaces, authentication, generated CLI commands, structured output, and approval-safe operations. Use for Akua setup, inspection, troubleshooting, or change requests.