Package Exports
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (conductor-init) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Conductor Init
Conductor Init is a Conductor Scaffolding CLI that generates spec-driven, portable Gemini Conductor workflows for any AI coding agent via npx. It enables the context-first evolution of spec-driven development for Claude Code, OpenCode, Cursor, Kilo Code, and other leading AI Coding Assistants.
Originally developed for the Gemini CLI, the Conductor is now decoupled by this project, empowering developers to maintain context, manage tasks, and orchestrate complex features. It serves as a bridge between human intent and AI execution, ensuring "Context is King" in the era of Agentic AI.
🎯 Goals
- Universal Compatibility: Enable the Conductor methodology outside of the Gemini CLI ecosystem.
- Agent-Agnostic Setup: Provide a mechanism to "install" Conductor commands and templates into a project, effectively "enabling" it for consumption by multiple different coding agents.
- Standardization: Create a unified interface for project orchestration that bridges the gap between human intent and AI execution.
✨ Key Features
- Universal AI Compatibility: Works out-of-the-box with Opencode, Claude Code, Antigravity, Cursor, VS Code Copilot, Codex, Windsurf, Cline, Kilo Code, Roo Code, Qwen Code, Factory Droid, and Gemini CLI.
- Context Management: Structured artifacts (
spec.md,plan.md) keep your AI agent focused and context-aware. - Spec-Driven Development: Define what you want before asking the AI how to build it.
- Agent-Agnostic Workflows: Switch between agents without losing project context or progress.
- Easy Initialization: Single command setup with
npx conductor-init. - Git Ignore Configuration: Automatically configure
.gitignoreor.git/info/excludeto exclude agent configuration files from version control.
🚀 Usage
1. Setup Conductor in Your Project
conductor-init [path] [options]
Positionals:
path Directory to install Conductor [string] [default: "."]
Options:
-a, --agent Specify the coding agent
[string] [choices: "opencode", "claude-code", "antigravity", "cursor",
"vscode-copilot", "codex", "windsurf", "cline", "kilo-code", "roo-code",
"qwen-code", "factory-droid", "gemini"]
-r, --repo Git repository URL for conductor. If used without value,
defaults to official repository. [string]
-b, --branch Branch name for conductor repository
[string] [default: "main"]
-s, --scope Installation scope (project or global)
[string] [choices: "project", "global"]
-g, --git-ignore Configure git ignore for Conductor files (gitignore: add to
.gitignore, exclude: add to .git/info/exclude, none: remove
entries) [string] [choices: "gitignore", "exclude", "none"]
-f, --force Force overwrite existing installation
[boolean] [default: false]
-h, --help Show help [boolean]
-v, --version Show version number [boolean]
Examples:
conductor-init Install with interactive prompts
conductor-init --agent claude-code Install for Claude Code agent
conductor-init --git-ignore gitignore Add Conductor files to .gitignore
conductor-init --git-ignore exclude Add Conductor files to
.git/info/exclude
conductor-init --git-ignore none Remove Conductor entries from git
ignoreTo initialize Conductor in your project, simply run the following command in your project root:
npx conductor-initYou can also specify a custom template repository and branch:
npx conductor-init --repo https://github.com/your-org/custom-conductor --branch v2Or specify the agent directly:
npx conductor-init --agent claude-code2. Alternative: Build from Source
If you prefer to build from source:
pnpm install
pnpm build
node dist/index.jsYou will be prompted to select your AI Coding Agent:
- Opencode
- Claude Code
- Antigravity
- Cursor
- VS Code Copilot
- Codex
- Windsurf
- Cline
- Kilo Code
- Roo Code
- Qwen Code
- Factory Droid
- Gemini CLI
This will verify the environment and install the necessary Conductor files:
- Commands: Agent-specific prompt or command files (e.g.,
.opencode/commands/conductor-setup.mdor.gemini/commands/setup.toml) that your agent can execute. - Templates: Workflow guides and style guides (e.g.,
.opencode/conductor/templates/).
3. Shell Completion
Enable tab completion for specific shells (Bash, Zsh) to make using conductor-init easier.
Zsh (Recommended)
Option 1: Source from file (Best for performance)
Generate the script to a file and source it in your .zshrc:
mkdir -p ~/.config/conductor
conductor-init completion > ~/.config/conductor/completion.zsh
echo 'source ~/.config/conductor/completion.zsh' >> ~/.zshrc
source ~/.zshrcOption 2: One-liner
Add this directly to your .zshrc (easiest setup):
echo 'source <(conductor-init completion)' >> ~/.zshrc
source ~/.zshrcBash
Add the completion script to your .bashrc:
conductor-init completion >> ~/.bashrc
source ~/.bashrc4. Using Conductor with Your Agent
Once installed, you can instruct your AI Agent to perform Conductor tasks using the installed commands. For example:
/conductor-setup- Initialize the project structure./conductor-newTrack- Start a new feature or bug fix track./conductor-implement- Implement the selected track./conductor-review- Review the completed track work against guidelines and the plan./conductor-revert- Revert previous work./conductor-status- Check the status of current tracks.
Note: The exact invocation syntax depends on your specific agent's slash command or file context capabilities.
🙏 Acknowledgements
This project is inspired by and based on the Conductor and Conductor-for-all.