Conductor (fcoury) — Summary

Conductor by Felipe Coury (fcoury) is the most cross-tool of all the CDD conductor variants: it explicitly ships for Claude Code (plugin), Gemini CLI (extension), and Codex CLI (prompt files + optional skill) in the same repository. The core methodology — Context-Driven Development via conductor/ directory with product.md, tech-stack.md, workflow.md, and track-based spec+plan lifecycle — matches the rbarcante/lackeyjb pattern, but fcoury makes it tool-agnostic by maintaining three separate integration points: .claude-plugin/, gemini-extension.json, and prompts/ + skills/conductor-development. The plugin ships 5 commands (setup, new-track, implement, status, revert) with an auto-activating conductor-development skill for ambient context injection. At 25 stars with last commit 2025-12-23, it is a community effort focused on portability. Compared to the seed superbasicstudio/claude-conductor (passive scaffold), fcoury adds commands, skills, and multi-tool distribution; compared to rbarcante (Python CLI + patterns), fcoury adds cross-tool support but removes the advanced features. The CODEX.md and GEMINI.md files are its distinguishing artifacts — no other conductor variant targets 3+ AI tools simultaneously.

Conductor (fcoury) — Overview

Origin

• Author: Felipe Coury (fcoury)
• Repo: https://github.com/fcoury/conductor
• Version: unknown
• License: Apache-2.0
• Stars: 25 | Forks: 1 | Last commit: 2025-12-23

Philosophy

Same CDD philosophy as rbarcante/lackeyjb:

"By treating context as a managed artifact alongside your code, you transform your repository into a single source of truth that drives every agent interaction with deep, persistent project awareness."

Tagline: "Measure twice, code once."

Key differentiation from other variants: multi-tool portability. From the README:

The plugin supports three AI coding tools:

• Claude Code (.claude-plugin/, /conductor:* slash commands)
• Gemini CLI (gemini extensions install, @conductor extension)
• Codex CLI (~/.codex/prompts/, /prompts:conductor-*)

This positions fcoury's conductor as the "universal CDD implementation" — one methodology, three runtimes.

Integration points per tool

Claude Code

• Install: /plugin marketplace add fcoury/conductor + /plugin install conductor@fcoury-conductor
• Commands: /conductor:setup, /conductor:new-track, /conductor:implement, /conductor:status, /conductor:revert
• Auto-skill: conductor-development activates when conductor/ directory exists

Gemini CLI

• Install: gemini extensions install https://github.com/fcoury/conductor --auto-update
• Commands: gemini-native (via gemini-extension.json)
• File: GEMINI.md provides conductor context awareness

Codex CLI

• Install: copy prompts/*.md to ~/.codex/prompts/
• Commands: /prompts:conductor-setup, /prompts:conductor-new-track, etc.
• Optional skill: skills/conductor-development/ copyable to ~/.codex/skills/
• Documented in: CODEX.md

Conductor (fcoury) — Architecture

Distribution

• Type: Claude Code plugin + Gemini CLI extension + Codex prompt files
• Install methods:
  • Claude Code: /plugin marketplace add fcoury/conductor && /plugin install conductor@fcoury-conductor
  • Gemini CLI: gemini extensions install https://github.com/fcoury/conductor --auto-update
  • Codex: copy prompts/*.md to ~/.codex/prompts/
• Required runtime: Claude Code (primary) / Gemini CLI / Codex CLI (alternatives)

Directory structure

fcoury/conductor/
├── .claude-plugin/          # Claude Code plugin manifest
├── commands/                # 5 slash commands (Claude Code)
│   ├── conductor/           # Additional conductor skill files
│   ├── setup.md
│   ├── new-track.md
│   ├── implement.md
│   ├── status.md
│   └── revert.md
├── skills/
│   └── conductor-development/  # Auto-activating CDD skill
├── prompts/                 # Codex CLI prompt files
│   ├── conductor-setup.md
│   ├── conductor-new-track.md
│   ├── conductor-implement.md
│   ├── conductor-status.md
│   └── conductor-revert.md
├── templates/               # Project template files
├── gemini-extension.json    # Gemini CLI extension config
├── GEMINI.md               # Gemini CLI context file
├── CODEX.md                # Codex CLI documentation
├── CONTRIBUTING.md
└── LICENSE

Runtime directory (created at setup per project)

conductor/
├── product.md
├── product-guidelines.md
├── tech-stack.md
├── workflow.md
├── tracks.md
├── setup_state.json
├── code_styleguides/
└── tracks/<track_id>/
    ├── spec.md
    ├── plan.md
    └── metadata.json

Target AI tools

• Primary: Claude Code
• Secondary: Gemini CLI, Codex CLI
• Cross-tool portability: medium-high (all three supported, prompt files differ)

Conductor (fcoury) — Components

Commands (5 — Claude Code)

Skills (1)

Prompt files (5 — Codex CLI)

Gemini CLI extension

• gemini-extension.json — extension manifest for Gemini CLI
• GEMINI.md — context file injected into Gemini sessions:

  "If a user mentions a 'plan' or asks about the plan, and they have used the conductor extension in the current session, they are likely referring to the conductor/tracks.md file or one of the track plans."

Templates

templates/ directory — project template files.

Hooks

None.

Sub-agents

None explicitly. The conductor-development skill provides ambient behavior rather than agent delegation.

Commands directory (commands/conductor/)

Additional skill files for conductor methodology embedded under the commands directory.

Conductor (fcoury) — Uniqueness

differs_from_seeds

Closest seed is superbasicstudio/claude-conductor (Archetype 4, passive scaffold), but fcoury adds 5 commands, 1 auto-activating skill, and multi-tool distribution. The key architectural delta from the seed is the conductor-development auto-skill (ambient methodology enforcement), and the cross-tool portability (GEMINI.md + Codex prompts). Among seeds, the auto-activating skill pattern most resembles superpowers (skills-only behavioral framework with ambient activation), but fcoury's skill is narrow (conductor methodology only) rather than a comprehensive behavioral framework. No other seed or variant in this batch targets 3 AI tools simultaneously in a single repo.

What makes fcoury conductor unique

1. Triple-tool distribution — Claude Code + Gemini CLI + Codex CLI from one repo (no other conductor variant does this)
2. Auto-skill ambient enforcement — conductor-development activates on directory presence or keyword mention
3. GEMINI.md — minimal (6-line) ambient context file for Gemini CLI disambiguation
4. CODEX.md — dedicated documentation for Codex CLI installation and usage
5. Tool-agnostic methodology — the core CDD content is the same; only the integration wrapper changes

Observable failure modes

1. Stale multi-tool maintenance: keeping 3 tool integrations in sync is a maintenance burden; as of 2025-12-23, may lag behind Claude Code API changes
2. 25 stars: very low adoption; uncertain maintenance trajectory
3. No specialist agents: simpler than lackeyjb/rbarcante; less robust for complex brownfield projects
4. No hooks: unlike lackeyjb, passive context management only via auto-skill (less reliable than explicit hooks)

Positioning

fcoury's conductor is uniquely positioned for teams that use multiple AI coding tools simultaneously (e.g., Claude Code for some team members, Codex for others). It enforces a shared project methodology regardless of which tool individual developers use.