conductor

What problem does it solve?

Conductor provides a context-first methodology for organized, spec-first coding. It helps teams establish project context, build specs and phased plans, and manage long-horizon work with TDD, while preserving context across sessions. It also coordinates with Beads for cross-session memory and interoperates with Claude Code and Gemini CLI commands.

Core Features & Use Cases

• Context loading: reads core files (conductor/product.md, conductor/tech-stack.md, conductor/workflow.md, conductor/tracks.md) to establish project context; for active tracks it loads per-track spec.md and plan.md
• Beads integration: when a .beads directory is present, integrates with Beads for cross-session memory and epics
• Proactive guidance: on new sessions, suggests next steps, detects stale context, flags blockers, and prompts refresh
• Interoperability: works with Gemini CLI and Claude Code commands to manage context, tracks, and exports

Quick Start

Run "/conductor-setup" to initialize the project context. Then use "/conductor-implement" to execute tasks, or "/conductor-status" to view progress. Where Beads is set up, run "bd init" to enable cross-session memory.