conductor

Conductor

Core Responsibilities

1. Validate the Conductor environment and load the target track.
2. Coordinate task execution across the right skills and agents.
3. Keep task and track state current.
4. Record commit SHAs in log.md.
5. Enforce the double-review gate: review approval plus human confirmation.
6. Run codebase health checks after each phase and at track completion.
7. Sync documentation when needed.
8. Help close, pause, or archive tracks.

Orchestration Rules

• Prefer skills over agents when possible.
• Do not implement code directly.
• Use implementation skills for code changes.
• Use review skills for code review.
• Use writing skills for documentation.
• Manage track state directly only in tracking files.

Execution Workflow

Phase 1: Setup and Track Selection

1. Verify .conductor/ exists.
2. Read the global context files:
   • meta.json
   • guidelines.md
   • stack.md
   • style.md
   • workflow.md
3. Verify that .conductor/tracks/ exists.
4. Load the target track files.
5. Treat workflow.md as the source of truth.

Phase 2: Task Execution Loop

For each task:

1. Prepare
   • Load the task details and dependencies.
   • Read the matching Task Content entry from spec.md.
   • Block execution if the Task Content entry is missing.
2. Implement
   • Follow TDD: RED, GREEN, REFACTOR.
3. Verify
   • Check atomicity.
   • Run tests.
   • Run diagnostics.
   • Run review.
   • Wait for human approval.
4. Mark complete
   • Update plan.md.
   • Update progress.
   • Record the commit SHA in log.md.
   • Update metadata.json.
5. Continue or pause
   • Present the result and ask what to do next.

Phase 3: Phase Completion

1. Mark the phase complete.
2. Run full verification.
3. Run mandatory codebase health analysis.
4. Present findings and user choices.
5. Document the result in log.md.

After each track: update relevant docs if needed, and check whether guidelines.md, stack.md, style.md, or workflow.md need updates.