How do I install the Conductor skill?

Run npx skillmds add majiayu000/conductor-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Conductor safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Conductor?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Conductor free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Conductor?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Conductor by majiayu000 — Agent Skill

Name: Conductor
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

Conductor

Context-driven development methodology. Trigger with ci, /conductor-implement, cn, /conductor-newtrack, or /conductor-* commands. Use when working with conductor/ directories, tracks, specs, plans, or when user mentions context-driven development.

majiayu000 66c9654 2 files · 4.9 KB Updated Sep 9, 2026 567 repo stars

File contents

Conductor: Context-Driven Development

Measure twice, code once.

Entry Points

Trigger	Action	Reference
`/conductor-setup`	Initialize project context	workflows/setup.md
`/conductor-design`	Design feature (Double Diamond)	design skill
`/conductor-newtrack`	Create spec + plan from design	workflows/newtrack.md
`/conductor-implement`	Execute track (auto-routes if parallel)	workflows/implement.md
`/conductor-status`	Display progress overview	structure.md
`/conductor-revise`	Update spec/plan mid-work	revisions.md
`/conductor-finish`	Complete track, extract learnings	finish-workflow.md
`/conductor-handoff`	Unified handoff (auto-detect create/resume)	workflows/handoff.md

Quick Reference

Phase	Purpose	Output
Requirements	Understand problem	design.md
Plan	Create detailed plan	spec.md + plan.md
Implement	Build with TDD	Code + tests
Reflect	Verify before shipping	LEARNINGS.md

Core Principles

Load core first - Load maestro-core for routing table and fallback policies
Design before code - /conductor-design → /conductor-newtrack → implement
TDD by default - RED → GREEN → REFACTOR (use --no-tdd to disable)
Beads integration - Zero manual bd commands in happy path
Parallel routing - ## Track Assignments in plan.md triggers orchestrator
Validation gates - Automatic checks at each phase transition

Directory Structure

conductor/
├── product.md, tech-stack.md, workflow.md  # Project context
├── code_styleguides/                       # Language-specific style rules
├── CODEMAPS/                               # Architecture docs
├── handoffs/                               # Session context
├── spikes/                                 # Research spikes (pl output)
└── tracks/<track_id>/                      # Per-track work
    ├── design.md, spec.md, plan.md         # Planning artifacts
    └── metadata.json                       # State tracking (includes planning state)

See structure.md for full details.

Beads Integration

All execution routes through orchestrator with Agent Mail coordination:

Workers claim beads via bd update --status in_progress
Workers close beads via bd close --reason completed|skipped|blocked
File reservations via file_reservation_paths
Communication via send_message/fetch_inbox

See beads-integration.md for all 13 integration points.

`/conductor-implement` Auto-Routing

Read metadata.json - check orchestrated flag
Read plan.md - check for ## Track Assignments
Check beads.fileScopes - file-scope based grouping (see file-scope-extractor)
If parallel detected (≥2 non-overlapping groups) → Load orchestrator skill
Else → Sequential execution with TDD

File Scope Detection

/conductor-newtrack Phase 4.5 extracts file paths from tasks and groups them:

Tasks touching same files → sequential (same track)
Tasks touching different files → parallel (separate tracks)
See parallel-grouping for algorithm

Anti-Patterns

❌ Skipping design phase for complex features
❌ Creating spec/plan without metadata.json
❌ Manual bd commands when workflow commands exist
❌ Ignoring validation gate failures

design - Double Diamond design sessions
beads - Issue tracking
orchestrator - Parallel execution
maestro-core - Routing policies in AGENTS.md

---name: conductor-2description: Context-driven development methodology. Trigger with ci, /conductor-implement, cn, /conductor-newtrack, or /conductor-* commands. Use when working with conductor/ directories, tracks, specs, plans, or when user mentions context-driven development.--- # Conductor: Context-Driven Development Measure twice, code once. ## Entry Points | Trigger | Action | Reference | |---------|--------|-----------| | `/conductor-setup` | Initialize project context | [workflows/setup.md](references/workflows/setup.md) | | `/conductor-design` | Design feature (Double Diamond) | [design skill](../design/SKILL.md) | | `/conductor-newtrack` | Create spec + plan from design | [workflows/newtrack.md](references/workflows/newtrack.md) | | `/conductor-implement` | Execute track (auto-routes if parallel) | [workflows/implement.md](references/workflows/implement.md) | | `/conductor-status` | Display progress overview | [structure.md](references/structure.md) | | `/conductor-revise` | Update spec/plan mid-work | [revisions.md](references/revisions.md) | | `/conductor-finish` | Complete track, extract learnings | [finish-workflow.md](references/finish-workflow.md) | | `/conductor-handoff` | Unified handoff (auto-detect create/resume) | [workflows/handoff.md](references/workflows/handoff.md) | ## Quick Reference | Phase | Purpose | Output | |-------|---------|--------| | Requirements | Understand problem | design.md | | Plan | Create detailed plan | spec.md + plan.md | | Implement | Build with TDD | Code + tests | | Reflect | Verify before shipping | LEARNINGS.md | ## Core Principles - **Load core first** - Load [maestro-core](../maestro-core/SKILL.md) for routing table and fallback policies - **Design before code** - `/conductor-design` → `/conductor-newtrack` → implement - **TDD by default** - RED → GREEN → REFACTOR (use `--no-tdd` to disable) - **Beads integration** - Zero manual `bd` commands in happy path - **Parallel routing** - `## Track Assignments` in plan.md triggers orchestrator - **Validation gates** - Automatic checks at each phase transition ## Directory Structure ``` conductor/ ├── product.md, tech-stack.md, workflow.md # Project context ├── code_styleguides/ # Language-specific style rules ├── CODEMAPS/ # Architecture docs ├── handoffs/ # Session context ├── spikes/ # Research spikes (pl output) └── tracks/<track_id>/ # Per-track work ├── design.md, spec.md, plan.md # Planning artifacts └── metadata.json # State tracking (includes planning state) ``` See [structure.md](references/structure.md) for full details. ## Beads Integration All execution routes through orchestrator with Agent Mail coordination: - Workers claim beads via `bd update --status in_progress` - Workers close beads via `bd close --reason completed|skipped|blocked` - File reservations via `file_reservation_paths` - Communication via `send_message`/`fetch_inbox` See [beads-integration.md](references/beads-integration.md) for all 13 integration points. ## `/conductor-implement` Auto-Routing 1. Read `metadata.json` - check `orchestrated` flag 2. Read `plan.md` - check for `## Track Assignments` 3. Check `beads.fileScopes` - file-scope based grouping (see [file-scope-extractor](references/file-scope-extractor.md)) 4. If parallel detected (≥2 non-overlapping groups) → Load [orchestrator skill](../orchestrator/SKILL.md) 5. Else → Sequential execution with TDD ### File Scope Detection `/conductor-newtrack` Phase 4.5 extracts file paths from tasks and groups them: - Tasks touching same files → sequential (same track) - Tasks touching different files → parallel (separate tracks) - See [parallel-grouping](references/parallel-grouping.md) for algorithm ## Anti-Patterns - ❌ Skipping design phase for complex features - ❌ Creating spec/plan without metadata.json - ❌ Manual `bd` commands when workflow commands exist - ❌ Ignoring validation gate failures ## Related - [design](../design/SKILL.md) - Double Diamond design sessions - [beads](../beads/SKILL.md) - Issue tracking - [orchestrator](../orchestrator/SKILL.md) - Parallel execution - [maestro-core](../maestro-core/SKILL.md) - Routing policies in AGENTS.md

Frequently asked questions