agent-team-gemini-harness

To set up a Gemini harness, initialize the standardized harness model including .gemini/agents, .gemini/skills, and GEMINI.md pointers in your project, then reload agents and skills to start the orchestration workflow.

A Gemini-native harness is a structured blueprint for defining reusable agents, skills, orchestrators, and GEMINI.md pointers consistently across repositories. You need one to enable project-level orchestration of Agent Team runtime interactions with a daemonless state.

Yes, you can audit and validate existing Agent Team runtime workflows. The harness supports validation, auditing, and evolution workflows to adapt components and ensure consistent runtimes across projects as requirements change.

Yes, the Gemini harness supports modularity and discoverability. It enforces these by providing frontmatter-driven metadata, trigger-rich descriptions, and structured references, scripts, and assets for reusable agents and skills.

You maintain GEMINI.md pointers by using the harness's evolution workflows. These workflows allow you to adapt and update harness components, ensuring consistent runtimes and security across repositories as project requirements change.