Spokes.wiki Search About
Software Source Code source ↗ source url updated Thu Jul 09 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

Conductor (Gemini CLI extension)

A (preview) Gemini CLI extension implementing context-driven-development — turning the CLI into a project manager that walks agents through Context → Spec & Plan → Implement. A spec-driven-development tool whose distinctive move is treating context as a managed artifact alongside code, so the repo is “a single source of truth that drives every agent interaction with deep, persistent project awareness.” Open-source; installed with gemini extensions install https://github.com/gemini-cli-extensions/conductor.

Features

  • Plan before implementation/conductor:newTrack generates two artifacts per track (unit of work): a spec (detailed requirements) and a plan.md (an actionable to-do list structured as Phases → Tasks → Sub-tasks); plan review required before execution (a course-correction gate).
  • Persistent, file-based state — the agent checks tasks off plan.md as it goes and state lives in files, so work pauses and resumes across sessions; supports mid-flight plan edits and version reversion.
  • Persistent context — project guidelines, tech-stack prefs, workflow standards (e.g. TDD), shared at team level; /conductor:setup establishes product/tech-stack/workflow up front.
  • Brownfield support — explicitly designed for established codebases, not just greenfield.
  • Git-aware smart reversion — reverts by logical work units (tracks / phases / tasks), not raw commits.
  • Commands: /conductor:setup, /conductor:newTrack, /conductor:implement.

Why it routed here

It extends spec-driven-development from “spec before code” to “context + spec before code” (context-driven-development), and is an orchestration/governance layer — an agentic-coding-harness focused on the planning/context side rather than execution fan-out. Notably it is the parallel-sprint engine inside gstack (10-15 simultaneous sessions). On Gemini CLI, it also shows the google/Gemini side building the same harness patterns as the Claude side.

Sources

The repo (this page’s url:) and Google’s launch post articulating the methodology (context-driven-development, Developers Blog, Keith Ballinger / Jay Kornder / Sherzat Aitbayev).

context-driven-development · spec-driven-development · agentic-coding-harness · gstack · agent-orchestration · google