Proposal: explore interoperability conventions for AI coding

# Hi Gemini CLI team,

I recently created [opinionated-ts/ai-spec](https://github.com/opinionated-ts/ai-spec), an early community-driven effort to explore an open specification for interoperability between AI coding assistants and development environments.

The repository was created only recently, and the project is intentionally in an **early stage**. The specification is not yet stable or finalized.

The purpose of starting this effort early is to involve existing ecosystems before their conventions become increasingly difficult to reconcile across tools.

The project is exploring common conventions around:

* Agents
* Hooks
* Plugins
* Instructions and configuration
* Discovery and precedence
* Lifecycle behavior
* Project-level AI configuration
* Other conventions that may benefit from interoperability

`ai-spec` is not intended to replace Gemini CLI or dictate its internal architecture.

Instead, it aims to provide a neutral place where existing implementations can be compared and where the community can determine which conventions are genuinely useful to standardize across ecosystems.

The repository currently contains the initial project structure, contribution process, and discussion space. Contributors are encouraged to examine existing implementations and prior art before proposing new conventions.

I would appreciate feedback from the Gemini CLI team on:

1. Which existing Gemini CLI conventions should be considered important prior art.
2. Which interoperability problems you believe are worth addressing.
3. Which behaviors should remain implementation-specific.
4. Whether there are existing efforts that `ai-spec` should build upon.
5. Whether the team or community would be interested in participating while the specification is still being shaped.

### Repository and discussion

Repository: https://github.com/opinionated-ts/ai-spec

Contributing: https://github.com/opinionated-ts/ai-spec/blob/main/CONTRIBUTING.md

Discussions: https://github.com/opinionated-ts/ai-spec/discussions

This is intentionally an early-stage initiative rather than a request for immediate adoption.

The project has just started, and the goal is to collect real-world prior art and involve the ecosystems and communities that implement these conventions before the specification becomes mature.

Review the linked ai-spec repository, especially its CONTRIBUTING.md and discussion space, to understand the proposed interoperability scope and prior art. The issue names no Gemini CLI file, test, or implementation entry point; done would require a concrete decision or actionable project change, which is not defined here.

Written by the indexing model from the issue text.