conductor

Orchestrates context-driven development with spec generation, TDD implementation, and checkpointed reverts.

4|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/Arete-Consortium/ai-skills --skill conductor-arete-consortium
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conductor
Source: https://github.com/Arete-Consortium/ai-skills/tree/main/workflows/conductor
Command: npx skills add https://github.com/Arete-Consortium/ai-skills --skill conductor-arete-consortium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature development without shared foundational context produces inconsistent code, and every session drifts from prior decisions. Conductor establishes and maintains project artifacts (product vision, tech stack, workflow rules, style guide) so every implementation phase works from the same context, with mandatory user checkpoints and revert capability. ## Core Features & Use Cases - Interactive Setup: Detects greenfield vs. brownfield projects and generates foundational artifacts (product.md, tech-stack.md, workflow.md, style-guide.md) through guided Q&A. - Spec & Plan Generation: Creates detailed feature specifications and phased implementation plans per track, requiring user approval before any code is written. - TDD Implementation with Revert: Executes tasks test-first with state tracking in state.json, and supports reverting by task, phase, or entire track via git revert commits. - Use Case: Starting a new feature like user authentication in an existing codebase — run setup once, create a track, approve the spec and plan, then let each TDD task complete with checkpoints between phases. ## Quick Start Ask the AI to run the conductor setup for this project and then create a new track for the feature you want to build.

Frequently Asked Questions about conductor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a structured development workflow for a new feature?▼

Run the conductor setup phase once per project to generate foundational artifacts, then create a track with a feature description. The workflow produces a spec and phased plan for your approval before implementing tasks with TDD.

How does conductor handle test-driven development?▼

Each task follows the TDD cycle: write failing tests first, implement minimum code to pass, then refactor. Tests and linting must pass before a task completes, and failures halt execution until you decide how to proceed.

Can conductor work with an existing brownfield codebase?▼

Yes, conductor detects brownfield projects by scanning for existing files and conventions. It reads existing docs and code patterns, then proposes artifacts that complement rather than contradict what already exists, flagging conflicts explicitly.

How do I revert changes made during a conductor track?▼

Use the revert command with a scope: task, phase, or track. Conductor shows exactly which commits will be reverted, requires confirmation, and creates new revert commits rather than rewriting git history.

When should I not use the conductor workflow?▼

Avoid conductor for single-file bug fixes where setup overhead is unjustified, exploratory research without concrete deliverables, or when you need parallel agent execution. It is sequential and single-threaded by design.