# google-conductor-context-driven-development-gemini-cli-2025-12-17

## Veille

Conductor Google - Gemini CLI extension for context-driven development

## Titre Article

Conductor: Introducing context-driven development for Gemini CLI

## Date

2025-12-17

## URL

https://developers.googleblog.com/conductor-introducing-context-driven-development-for-gemini-cli/

## Keywords

Gemini CLI, context-driven development, specifications, persistent documentation, brownfield, AI workflow, Markdown, planning

## Authors

Keith Ballinger, Jay Kornder, Sherzat Aitbayev

## Ton

Profile: Official Google product announcement, accessible technical register, developer tool launch perspective.
Style: Informative and structured tone, typical of Google Developer communications. Methodical presentation across three phases (setup, newTrack, implement). Emphasis on solving an identified problem (the gap between ephemeral chat and persistent documentation). Vocabulary oriented toward developer productivity. Target audience: developers using Gemini CLI, technical teams looking to structure their AI usage.

## Pense-betes

- Gemini CLI extension for context-driven development
- Philosophy: moving from temporary chat logs to persistent documentation
- Specifications and plans stored as Markdown files in the codebase
- Three main commands: /conductor:setup, /conductor:newTrack, /conductor:implement
- Setup phase: product definition, technology stack, workflow preferences
- newTrack phase: generates detailed specs and task plans for new features
- Implement phase: execution with the ability to pause, resume, and modify
- Explicit support for brownfield projects (existing codebases)
- Enables teams to establish shared technical standards and guidelines
- Available on GitHub

## RésuméDe400mots

Google has announced Conductor, a new extension for Gemini CLI designed to transform AI-assisted development workflows. The tool introduces a "context-driven development" approach that moves away from ephemeral chat logs in favor of persistent, formal documentation.

Conductor's core principle rests on storing project specifications and plans as Markdown files directly within the codebase. This approach ensures that project context remains accessible and consistent for all team members, unlike AI conversations that disappear after each session.

The workflow is structured around three distinct phases. The first phase uses the `/conductor:setup` command to establish the project's foundational context. This step covers product definition, the chosen technology stack, and the team's workflow preferences. This information becomes the baseline for all subsequent interactions with the AI.

The second phase, triggered by `/conductor:newTrack`, initiates work on a new feature. The tool then generates detailed specifications and actionable task plans. This step structures the work before any implementation, favoring upfront reflection over improvised coding.

The third phase uses `/conductor:implement` to execute the established plan. The tool offers significant flexibility: developers can pause work, resume it later, or modify the plan along the way based on discoveries made during implementation.

Conductor addresses a specific need that is often overlooked: support for brownfield projects, meaning existing codebases. For these projects, understanding historical context and existing architecture proves crucial. The tool allows this knowledge to be documented in a structured way, facilitating the onboarding of new developers and relevant AI assistance.

The extension also allows teams to establish shared technical standards and coding guidelines. Once documented, these conventions steer AI suggestions toward practices consistent with the team's choices.

This announcement fits within the broader trend of structuring AI interactions in software development, joining similar approaches such as AGENTS.md files or skill systems. The extension is available for download on GitHub.

## GrapheDeConnaissance

- Google —a_créé→ Conductor (TECHNOLOGIE, 0.97)
- Conductor —fait_partie_de→ Gemini CLI (TECHNOLOGIE, 0.98)
- Conductor —est_basé_sur→ développement piloté par le contexte (METHODOLOGIE, 0.95)
- Conductor —utilise→ fichiers Markdown pour les spécifications (CONCEPT, 0.93)
- Conductor —s_applique_à→ projets brownfield (CONCEPT, 0.9)
- Keith Ballinger —a_créé→ Conductor (TECHNOLOGIE, 0.85)
- Jay Kornder —a_créé→ Conductor (TECHNOLOGIE, 0.85)
- Sherzat Aitbayev —a_créé→ Conductor (TECHNOLOGIE, 0.85)
- développement piloté par le contexte —remplace→ logs de chat éphémères (CONCEPT, 0.88)
- Conductor —converge_avec→ AGENTS.md et systèmes de skills (CONCEPT, 0.82)

---
Canonical: https://www.thekb.eu/en/fiches/google-conductor-context-driven-development-gemini-cli-2025-12-17/