conductor

Load project context files and manage structured tracks and specs.

24|4|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/NguyenSiTrung/Conductor-Beads --skill conductor-nguyensitrung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conductor
Source: https://github.com/NguyenSiTrung/Conductor-Beads/tree/main/.claude/skills/conductor
Command: npx skills add https://github.com/NguyenSiTrung/Conductor-Beads --skill conductor-nguyensitrung

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about conductor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize software development work with structured tracks and specs?

Conductor translates project context into organized tracks and specs using a context-first methodology. It reads core files (product.md, tech-stack.md, workflow.md, tracks.md) to establish project context, then generates phased implementation plans aligned with TDD principles for long-horizon work.

Can I preserve project context and memory across development sessions?

Yes. Conductor integrates with Beads for cross-session memory and state tracking. When a .beads directory is present, it maintains context, epics, and progress across sessions, enabling teams to pick up work without reestablishing context.

How do I get started with a context-first workflow for my project?

Run /conductor-setup to initialize project context by loading or creating conductor/product.md, conductor/tech-stack.md, conductor/workflow.md, and conductor/tracks.md. Then use /conductor-implement to execute tasks or /conductor-status to view progress.

Does Conductor work with Claude Code and Gemini CLI commands?

Yes. Conductor interoperates with Claude Code and Gemini CLI to manage context, tracks, and exports. It coordinates workflow metadata so CLI commands can access structured project information and execute tasks against established specs.

What file formats and structure does Conductor require?

Conductor uses conductor/product.md for project overview, conductor/tracks.md for phased work, per-track spec.md and plan.md files for detailed requirements, and conductor/beads.json for Beads integration. It supports both greenfield and brownfield project scenarios.

Can I use Conductor on existing projects or only new ones?

Conductor applies to both greenfield and brownfield projects. It works on mature codebases by loading existing context and incrementally establishing tracks, specs, and implementation plans without requiring project restart.