AI Development Tools
Google's Conductor Shifts to Plugin Architecture, Enabling Cross-Tool AI-Driven Development
The spec-driven development tool moves beyond Gemini CLI to work conversationally across multiple platforms including Antigravity, while preserving version-controlled architecture files.
Google Developers Blog (AI)
Google has announced a major evolution for Conductor, its spec-driven development tool. Rather than remaining locked within the Gemini CLI as an extension, Conductor now operates as a portable plugin that integrates with multiple AI development environments, including Antigravity CLI and others.
From Extension to Plugin#
The redesign fundamentally changes how developers interact with the tool. Previously, Conductor required users to follow strict command sequences within the Gemini CLI terminal. The plugin approach smooths this friction by shifting to natural conversation—the system dynamically generates and updates specifications and development plans as you discuss your architectural needs, without forcing you to memorize specific commands.
The persistent spec.md and plan.md files that form the core of spec-driven development remain central to the workflow. Now, however, the AI handles those artifacts intelligently in the background, automatically updating context and tracking completed tasks while you focus on design decisions.
Unified Context Across Tools#
A key benefit of the plugin model is portability. Your project's architectural guidelines, configuration, and development context now persist consistently whether you're working in Antigravity CLI, Claude, or other compatible tools. Start a workflow in one environment and continue it seamlessly in another without losing conversational continuity—the repository stays the single source of truth.
The new plugin maintains backward compatibility with existing Conductor commands and legacy plans and specifications.
Key Features#
The Conductor Plugin emphasizes accessibility and adaptability:
- Natural dialogue replaces command memorization
- Tool flexibility — use Conductor wherever it fits your current task
- Preserved architecture — your repository remains central to the development process
- Improved outcomes — early testing on complex TerminalBench tasks shows higher success rates with spec-driven discipline than without it

