Session-start orientation for this team harness. Load first, before any work. Explains the operating contract, when each skill triggers, and how installed companion plugins supply agent-craft capabilities while this harness supplies the team contract. Trigger at the start of every session and whenever unsure which skill applies.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
This is a team operating harness: one shared contract for humans and AI agents working in the same repository — same rules, same risk tiers, same evidence, same definition of done. It exists to make a mixed human–AI team coherent, not to make one agent faster.
A skill supplies a repeatable procedure. It never supplies permission or accountability.
docs/operating-model/PROJECT-OPERATING-PROFILE.md),
then the manual it binds. Profile facts beat inference.delivery-orchestrator.The shared plugin is provider-neutral. Host adapters implement invocation; the project profile selects authorised reviewers, subscriptions and budgets. Independent Council review is a capability, not a fixed roster. See the review contract.
A user-level installation makes the skills available across that user’s projects; a
project installation shares a selected baseline with collaborators. Neither creates
project authority. Use the host’s selected skill location, including bundled references
and scripts, without assuming a copied .agents/skills/ directory.
For a new adoption, route to operating-model-bootstrap from the consumer project.
Ground its project-owned vision, workflow and profile: ticket system, owners, model
selection, executable checks, review, release and observation. Existing records and
explicit operator authority take precedence. Load detailed skills when needed; an
unadopted project needs orientation and an adoption path, not the full delivery process.
seed is not active. A seed profile supports design and R0/R1 work only.| Work in front of you | Skill |
|---|---|
| New repo, or operating model install/repair | operating-model-bootstrap |
| Multi-track epic, or "which skill applies?" | delivery-orchestrator |
| An agreed goal to drive to a working, merged outcome while the operator is away | get-it-done |
| The machine is slow, tests or browser skills left processes behind | system-performance-guardrail |
| Is everything live, any errors this week, the weekly SRE checkup of a GCP project | cloud-checkup |
| Is the page fast enough, Core Web Vitals, why is this route slow | frontend-performance-audit |
| Vision, requirements, user journeys and product acceptance | product-owner |
| Material strategic, cost/risk or operating ownership decision | cxo-oversight |
| Acceptance coverage and executable user-path checks | test-strategy |
| Significant technical decision or ADR | the-architect |
| New feature, epic, or change — plan before code | spec-first-delivery |
| High-stakes decision, or before claiming done | adversarial-gate |
| Agent output feeding a decision, store, or another agent | domain-validator |
| Any PR or agent-generated code before commit | pr-reviewer |
| Anything about to ship to a real environment | release-readiness |
| CI triggers, Actions billing, issues, labels, branch protection, or release-tag workflow | github-manager |
| Release process governance: SemVer, ADR, changelog, release authority | release-manager |
| Enterprise policy, compliance, governance, or approved-vendor alignment | governance-guardrail |
| Status, standup, or situation report | sitrep |
| Plugin-directory, marketplace, or curated-list submission | plugin-submission |
| LLM/cloud cost estimate or architecture with LLM calls | cost-guardrail |
| Google ADK multi-agent design | adk-expert |
| Any cloud-vendor workload (GCP, AWS, Azure, Alibaba Cloud) | cloud-expert (the-architect routes) |
| Adding or reviewing an MCP server | mcp-server-scaffold |
Agent-craft capabilities may be provided by installed companion plugins instead of these
skills — see INTEGRATIONS.md for the evaluated map (simplicity discipline, TDD
methodology, frontend design review, and similar craft lanes).
Skills name actions, not tools. The per-harness translation lives outside the canonical skill bodies:
references/antigravity-tools.md (in this skill's
directory) before acting; it maps subagent dispatch, task tracking, and file/search
actions to Antigravity's native tools.skillInstructions carry the mapping.| Excuse the agent makes | Counter |
|---|---|
| "The skills are just docs — I can skip them" | The skills are the harness. Skipping them is running without the contract. |
| "This task is too small for a skill" | Gates are proportional to risk — R0/R1 is cheap. Skipped small gates are where big failures rehearse. |
| "The companion plugin handles quality" | Companions own craft. Authority, evidence, and completion semantics stay here. |
| "I'll edit the skill body to fit my tools" | Porting adds a thin adapter or tool mapping. Canonical skill bodies never change per harness. |
| "I remember the contract from earlier" | Sessions compact and clear. Re-ground in the tracked profile; memory is not the contract. |
| "The user seems in a hurry" | Speed is easy. Safe speed is engineered. Hurry raises risk tier, it does not lower it. |
Route through delivery-orchestrator. Record every unresolved fact with an owner and
the trigger that resolves it. Stop before any R2/R3 mutation or external action that
lacks explicit authority and runnable controls.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Google ADK (Agent Development Kit) orchestration patterns — boundaries, agent composition, and tool seams. Trigger when designing or reviewing multi-agent systems built on ADK. Authoritative source: adk.dev.
The English summary is being prepared. Showing the original description.
JP's signature red-team pass — "how would I break this?" Argue against your own approach before proceeding. Trigger on any high-stakes decision, architecture choice, or before marking work complete.
The English summary is being prepared. Showing the original description.
Read-only SRE checkup of any GCP project: deterministic probes of the edge, Cloud Run services, 7-day error logs, Cloud Scheduler, alert policies and uptime checks, Secret Manager and IAM, the data stores and the machine's own scheduled jobs, audited into one fixed status table (LIVE / WARNING / RED / INCONCLUSIVE) with evidence, findings by severity, what could not be checked, and a single OVERALL line delivered as one notification. Parametrised by a per-project manifest, so the same routine runs on every project. Use when the operator says "cloud checkup", "SRE check", "is everything live", "what's healthy / warning / red", "any errors this week", "audit the infra", "weekly checkup", "set up the weekly checkup", before a deploy or demo, or after an incident. Cloud Run first; App Engine and GKE differ only in the serving probes.
The English summary is being prepared. Showing the original description.
Cloud guardrails for any vendor workload — Google Cloud (GCP, Vertex AI, GKE), AWS (IAM, EKS, Bedrock), Azure (Entra ID, Policy, AKS), Alibaba Cloud (RAM, mainland/international residency). Enforces identity least-privilege, mechanical policy, data boundaries, residency, cost caps, network egress and observability, with official-source validation before any claim. Trigger on any cloud infrastructure design, review, Terraform plan, or LLM/agent deployment; the-architect routes here.
The English summary is being prepared. Showing the original description.
LLM and cloud cost awareness — model tiering, token budgets, right-sizing, and when a cheaper model suffices. Trigger before finalising any architecture that calls LLMs, before scaling a workload, or when a cost estimate is needed.
The English summary is being prepared. Showing the original description.
Challenge vision alignment, value, cost, risk and operating ownership at material scope or release decisions.
The English summary is being prepared. Showing the original description.