Skip to content
Skills Library
Management & product · Planning

conductor

/conductor

Use when the user explicitly asks for Conductor, wants track/spec/plan/review artifacts on disk, or needs long-lived project context management. Prefer start-dev for small or one-off tasks. If Conductor is not configured in the project, start with setup.

Repository
oh-my-codex ↗
Licence
MIT
Last repository change
22.08.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
31
Scripts
1
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 22.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/install.sh

What it does and when to use it

Use when the user explicitly asks for Conductor, wants track/spec/plan/review artifacts on disk, or needs long-lived project context management. Prefer start-dev for small or one-off tasks. If Conductor is not configured in the project, start with setup.

Original author description

Use when the user explicitly asks for Conductor, wants track/spec/plan/review artifacts on disk, or needs long-lived project context management. Prefer start-dev for small or one-off tasks. If Conductor is not configured in the project, start with setup.

How it works

  1. When To Use
  2. Native Subagent Protocol (Codex)
  3. Upstream Alignment (Conductor)
  4. Universal File Resolution Protocol (Codex Adaptation)
  5. Core Concepts
  6. Directory Structure
  7. Available Commands
  8. Protocol References
  9. Task Status Markers
  10. Key Workflow Principles
Original SKILL.md headings · 170 lines, 999 words
SKILL.md preview
---
name: conductor
description: Use when the user explicitly asks for Conductor, wants track/spec/plan/review artifacts on disk, or needs long-lived project context management. Prefer start-dev for small or one-off tasks. If Conductor is not configured in the project, start with setup.
version: 0.1.0
source: fork
checksum: adf8bf4bc4f26b82d39d35ce6699ecd65504ead8143a243de1e0c59cc3b03620
updated_at: 2026-05-29T11:50:00+08:00
intent: execution
layer: orchestration
---


# Conductor

Conductor is a Context-Driven Development (CDD) workflow for managing durable project context on disk. The working loop is:

```text
Refresh -> Spec -> Plan -> Implement -> Review -> Reconcile
```

This skill is the Codex-native adaptation of the upstream Conductor repository. Keep the workflow compatible with upstream concepts, but translate execution into Codex conventions instead of copying upstream-only behavior literally.

## When To Use

Use **Conductor** when the user wants:
- persistent artifacts under `conductor/`
- a track with `spec.md` and `plan.md`
- a governed multi-step implementation flow
- a lightweight preflight summary before important work
- review/cleanup/archive operations tied to the track lifecycle

Use **start-dev** instead when the task is small, one-off, or does not need new artifacts on disk.

## Native Subagent Protocol (Codex)

Codex supports native subagents. Delegate with `spawn_agent`, coordinate with `send_input`, collect via `wait_agent`, and clean up with `close_agent`.

Execution preference:
1. Use native subagents first for independent workstreams (parallel when possible).
2. Merge results in main thread and run final verification.
3. Fallback only when delegation is blocked: use the `[ANALYST]`/`[ARCHITECT]`/`[EXECUTOR]`/`[REVIEWER]` structure in a single response.

Minimal orchestration pattern:
```text
spawn_agent -> send_input (optional) -> wait_agent -> close_agent
```

## Upstream Alignment (Conductor)

When adapting or extending this skill, inspect the upstream repository as a protocol bundle, not just the README. The highest-value upstream files are:
- upstream project instruction files
- upstream extension metadata
- `policies/conductor.toml`
- `commands/conductor/*.toml`
- `templates/workflow.md`

Preserve these upstream ideas when they improve Codex behavior:
- `conductor/` is the default plan directory
- commands are protocol files; read the TOML `prompt` field before executing
- review is a first-class command, not an afterthought
- file resolution should work from semantic names, not only hard-coded paths
- implementation and verification should prefer isolated review contexts when possible

The compatibility boundary for this skill is defined in:
- `docs/CONDUCTOR_V2_COMPATIBILITY_CONTRACT.md`

## Universal File Resolution Protocol (Codex Adaptation)

Before using Conductor files, resolve them in this order:

1. If the project contains upstream metadata such as project instruction files, extension metadata, or `policies/conductor.toml`, read those first and honor their plan-directory declarations.
2. Otherwise, default to the fixed `conductor/` directory.
3. Resolve semantic aliases as follows:
   - Tracks Registry -> `conductor/tracks.md`
   - Product Definition -> `conductor/product.md`
   - Product Guidelines -> `conductor/product-guidelines.md`
   - Tech Stack -> `conductor/tech-stack.md`
   - Workflow -> `conductor/workflow.md`
   - Track Folder -> `conductor/tracks/<track_id>/`
   - Archive -> `conductor/archive/`
   - Temp Workspace -> `conductor/tmp/`
   - Code Styleguides -> `conductor/code_styleguides/`

If the user asks for a custom artifact path, state that Conductor defaults to `conductor/` and either:
- proceed with the default directory, or
- pause for a deliberate protocol refactor

## Core Concepts

- **Track**: A unit of work (feature or bug fix) with its own spec and plan
- **Spec**: Detailed requirements document (`spec.md`)
- **Plan**: Phased task list with checkboxes (`plan.md`)
- **Workflow**: Rules for task lifecycle, TDD, commits, and quality gates

## Directory Structure

When initialized, Conductor creates this structure in the project:

```
conductor/
├── product.md              # Product vision and goals
├── product-guidelines.md   # UX/brand guidelines
├── tech-stack.md           # Technology choices
├── workflow.md             # Development workflow rules
├── tracks.md               # Master list of all tracks
├── code_styleguides/       # Language-specific style guides
├── tracks/                 # Active tracks
│   └── <track_id>/
│       ├── metadata.json
│       ├── spec.md
│       └── plan.md
└── archive/                # Completed tracks
```

## Available Commands

| Command | Purpose |
|---------|---------|
| **Setup** | Initialize Conductor in a project (new or existing) |
| **Refresh** | Refresh the facts layer from code, config, and git state |
| **New Track** | Create a new feature/bug track with spec and plan |
| **Implement** | Execute tasks from a track's plan following TDD workflow |
| **Review** | Review a track or current changes against spec, plan, workflow, and code guidelines |
| **Status** | Show progress overview of all tracks |
| **Revert** | Git-aware rollback of tracks, phases, or tasks |

## Protocol References

The detailed protocols are in TOML format. Read the `prompt` field from each file:

| Action | Protocol File |
|--------|---------------|
| Setup project | `commands/conductor/setup.toml` |
| Refresh facts | `commands/conductor/refresh.toml` |
| Create new track | `commands/conductor/newTrack.toml` |
| Implement tasks | `commands/conductor/implement.toml` |
| Review implementation | `commands/conductor/review.toml` |
| Check status | `commands/conductor/status.toml` |
| Revert changes | `commands/conductor/revert.toml` |

**How to read**: Each `.toml` file has a `prompt` field containing the full protocol instructions.

## Task Status Markers

- `[ ]` - Pending
- `[~]` - In Progress
- `[x]` - Completed

## Key Workflow Principles

1. **The Plan is Source of Truth**: All work tracked in `plan.md`
2. **Test-Driven Development**: Write tests before implementing
3. **High Code Coverage**: Target >80% coverage
4. **Commit After Each Task**: With git notes for traceability
5. **Phase Checkpoints**: Manual verification at phase completion

## When to Use Each Protocol

- **"set up conductor" or "initialize project"** -> Read `commands/conductor/setup.toml`
- **"refresh", "sync current context", "update conductor facts"** -> Read `commands/conductor/refresh.toml`
- **"new feature", "new track", "plan a feature"** -> Read `commands/conductor/newTrack.toml`
- **"implement", "start working", "next task"** -> Read `commands/conductor/implement.toml`
- **"review", "audit", "check this track"** -> Read `commands/conductor/review.toml`
- **"status", "progress", "where are we"** -> Read `commands/conductor/status.toml`
- **"revert", "undo", "rollback"** -> Read `commands/conductor/revert.toml`
- **If the user does not mention Conductor and the task is small** -> Use `start-dev` instead

## Assets

- **Code Styleguides**: `templates/code_styleguides/` (general, go, python, javascript, typescript, html-css)
- **Workflow Template**: `templates/workflow.md`

## Critical Rules

1. **Validate every tool call** - If any fails, halt and report to user
2. **Check setup first** - Resolve and verify the required Conductor files before any operation
3. **Codex-first interaction** - Prefer reasonable assumptions; ask one concise blocking question only when necessary
4. **Plain-language UX** - Do not suggest slash commands. Tell the user what to ask for directly in natural language
5. **Codex-native delegation** - Replace upstream-only flows such as `ask_user` or isolated CLI shells with Codex chat, native subagents, and local commands
Files in this package (31)
  • SKILL.md 8 KB
  • commands/conductor/implement.toml 8 KB
  • commands/conductor/newTrack.toml 9 KB
  • commands/conductor/refresh.toml 4 KB
  • commands/conductor/revert.toml 8 KB
  • commands/conductor/review.toml 5 KB
  • commands/conductor/setup.toml 37 KB
  • commands/conductor/status.toml 6 KB
  • scripts/install.sh 3 KB
  • templates/current.md 1 KB
  • templates/workflow.md 14 KB
  • templates/code_styleguides/csharp.md 6 KB
  • templates/code_styleguides/dart.md 12 KB
  • templates/code_styleguides/general.md 1 KB
  • templates/code_styleguides/go.md 3 KB
  • templates/code_styleguides/html-css.md 3 KB
  • templates/code_styleguides/javascript.md 3 KB
  • templates/code_styleguides/python.md 2 KB
  • templates/code_styleguides/typescript.md 3 KB
  • templates/rules/README.md 1 KB
  • templates/rules/agents.md 1 KB
  • templates/rules/coding-style.md 1 KB
  • templates/rules/dev.md 1 KB
  • templates/rules/git-workflow.md 1 KB
  • templates/rules/hooks.md 1 KB
  • templates/rules/patterns.md 1 KB
  • templates/rules/performance.md 1 KB
  • templates/rules/research.md 1 KB
  • templates/rules/review.md 1 KB
  • templates/rules/security.md 1 KB
  • templates/rules/testing.md 1 KB

Versions

RepositoryScoreLicence
This page · materialofair/oh-my-codex100MIT
crbnos/carbon100AGPL-3.0
microsoft/conductor100MIT
singlak999/Conductor100MIT
seattle78/AgentQuest100Apache-2.0
conductor-oss/conductor-skills100Apache-2.0
RizwanZafaris/product-manager-OS100MIT
garagon/nanostack100Apache-2.0
inkbytefo/claude-conductor98MIT

Database snapshot: 13.11.2026 · package version 1dbefdc1c2a6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95conductor-context
    Auto-load Conductor project context when conductor/ directory exists. Use for any development task in a Conductor-managed project to ensure alignment with product goals, tech stack, and workflow methodology.
  • 100conductor-setup
    Scaffolds the project and sets up the Conductor environment. Use this whenever a project needs to be initialized or if the Conductor configuration is missing.
  • 100track-management
    Use this skill when creating, managing, or working with Conductor" tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
  • 100track-management
    Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
  • 100track-management
    Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
  • 100track-manager
    Manage Conductor tracks, phases, and tasks. Use when working with track status, updating task markers, or navigating between tracks.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.