Conductor-Beads

Git-backed issue tracker for multi-session work with dependencies and persistent memory across conversation compaction. Use when work spans sessions, has blockers, or needs context recovery after compaction.

Context-driven development methodology for organized, spec-first coding. Use when: - Project has a `conductor/` directory - User mentions specs, plans, tracks, or context-driven development - Files like `conductor/tracks.md`, `conductor/product.md`, `conductor/workflow.md` exist - User asks about project status, implementation progress, or track management - User wants to organize development work with TDD practices - User invokes `/conductor-*` commands (setup, newtrack, implement, status, revert, validate, block, skip, revise, archive, export, handoff, refresh, formula, wisp, distill) - User mentions documentation is outdated or wants to sync context with codebase changes Interoperable with Gemini CLI extension and Claude Code commands. Integrates with Beads for persistent task memory across sessions.