Conductor emerging

Core approach

Treats project context as a version-controlled artifact alongside the code. A one-time setup records the product, guidelines, tech stack, code style, and team workflow under conductor/. Each feature or bug becomes a track under conductor/tracks/<id>/ with its own spec.md, plan.md, and metadata.json; after plan approval, the agent implements tasks, updates shared context, reviews the result against the plan and guidelines, and can revert a logical track, phase, or task through Git history.

Workflow

1. /conductor:conductor-setup — establish product context, guidelines, tech stack, code style, workflow preferences, and the track registry
2. /conductor:conductor-new-track — interview for a feature or bug, then write conductor/tracks/<id>/spec.md, plan.md, and metadata.json for approval
3. /conductor:conductor-implement — execute the approved plan task by task, checking off work and synchronizing project context on completion
4. /conductor:conductor-status — report progress across active and completed tracks
5. /conductor:conductor-review — audit completed work against the plan and project guidelines, run tests, and append a review-fixes phase when needed
6. /conductor:conductor-revert — roll back a whole track, phase, or task and reset its plan state for another attempt

Supported tools

• Antigravity
• Claude Code

Notes

Conductor began as a Gemini CLI extension, but Google announced its move to a portable agent plugin in July 2026. The official migration announcement preserves its original idea — persistent, version-controlled context — while making conversation, rather than a rigid command sequence, the front door. The current repository lifecycle still exposes explicit setup, track, implementation, status, review, and revert operations. That recent transition and pre-1.0 release line keep the maturity rating at emerging, even though the methodology is complete enough to use today. This assessment observes the post-migration repository at 99ba10e.

Added Aug 1, 2026 · Assessment last reviewed Aug 1, 2026 · How we track