Designing a team of agents

Google Antigravity added support for building with an autonomous team of agents. Google's blog post reveals the agents that make up these teams, and I think it is relevant for Openclaw as we design our subagents: https://antigravity.google/blog/google-antigravity-built-an-os Snip: Instead of a single agent wearing many hats, we ended up creating a series of subagent types with specialized goals and constraints: The Sentinel — the “front-desk manager” of the project that does not write code, analyze logs, or makes technical decisions. It focuses entirely on structuring user intent, spawning the Orchestrator, and supervising overall task completion. The Orchestrator — a dispatch-only manager, i.e. never writes code or executes builds itself. Focuses on decomposing requirements into milestones, kicking off other specialized subagents, and synthesizing reports. The Explorer — analyzes requirements and previous logs to write formal strategies for the Orchestrator to act on, but never writes code itself. The Worker — the actual coder that implements the strategies, builds the code, and runs tests. The Reviewer — independently reviews the Worker’s changes for design correctness, edge cases, and interface contract compliance. The Critic — stress-tests the solution, runs adversarial tests to find gaps in coverage. The Auditor — an independent investigator that verifies the authenticity and robustness of the generated solutions.