Source: Google Developers Blog — 2026-07-16
Summary
Conductor, previously a Gemini CLI-only extension, now runs as a portable plugin across other agent surfaces including Antigravity CLI, extending spec-driven development beyond its original home. The tool keeps persistent spec.md and plan.md artifacts as the source of truth for a project while letting developers refine the spec conversationally rather than hand-editing structured documents.
Key Takeaways
- Spec-driven development here means the agent works from a durable, version-controllable spec.md and plan.md pair instead of re-deriving intent from scratch each session — the documents persist and evolve as the actual project memory.
- Making Conductor a portable plugin instead of a Gemini CLI-exclusive extension is the notable architectural shift: the same spec-driven workflow can now travel with a developer across different agent CLIs.
- Developers still edit specs through natural conversation, not by hand-writing structured markdown — the tool translates the conversation into the persistent spec/plan documents.
- This is part of a broader industry pattern of treating "what the agent should build" as a durable artifact that outlives any single session, rather than living only in chat history.
Reel Script
Hook (15s / 34 words) Every time you close your coding agent's chat window, does it forget what you were building? Google's Conductor is built around never letting that happen — and now it works outside Gemini's own CLI.
Core Concept (55s / 120 words) Spec-driven development flips the usual coding-agent workflow. Instead of you describing what you want in a chat message that gets buried and lost, Conductor maintains two persistent files: spec.md, which captures what the project should actually do, and plan.md, which captures how it's being built. You still just talk to it conversationally — describe changes, ask for adjustments — but instead of that conversation evaporating, it gets distilled back into those two documents, which live in your repo like any other file. Think of it as the difference between giving verbal directions that vanish the moment you stop talking, versus updating a shared map that anyone — including a future version of the agent — can pick back up.
Hands-On (45s / 100 words) The concrete change this week is architectural, not a new feature inside Conductor itself: it's no longer locked to the Gemini CLI. It now runs as a portable plugin, which means the same spec.md/plan.md workflow can follow a developer into other agent CLIs, including Antigravity. Picture the flow as a simple loop: conversation goes in, spec.md and plan.md get updated, the agent reads those files back out at the start of the next session instead of starting cold. That loop staying intact across different host tools is the actual news here.
Takeaway (22s / 48 words) If your team's coding agent workflow has no persistent spec artifact — just chat history that gets lost between sessions — that's a real gap worth closing. Go look at whether a spec.md/plan.md pattern would survive tool switches for your own setup.