conductor-context
Use this skill when the user mentions "plan", "track", "spec", "conductor", asks about project progress, or references conductor files like plan.md, spec.md, tracks.md, product.md, tech-stack.md, or workflow.md. Also use when the user wants to understand the Conductor methodology or Context-Driven Development workflow.
When & Why to Use This Skill
The Conductor skill implements a sophisticated Context-Driven Development (CDD) methodology, effectively transforming Claude into an autonomous project manager. It optimizes the software development lifecycle by enforcing a strict 'Context -> Spec & Plan -> Implement' protocol. By maintaining persistent project awareness through structured documentation (plans, specs, and tracks), it ensures that AI-driven coding remains aligned with project goals, technical standards, and rigorous testing requirements.
Use Cases
- Project Initialization: Setting up a comprehensive project foundation by defining product vision, tech stacks, and development workflows in a centralized 'conductor/' directory.
- Structured Feature Development: Managing the end-to-end lifecycle of new features or bug fixes using 'tracks' that include detailed requirements (spec.md) and actionable task lists (plan.md).
- Progress Tracking & Reporting: Monitoring the real-time status of multiple workstreams and providing clear overviews of project milestones and pending tasks.
- Test-Driven Development (TDD) Enforcement: Guiding the development process through mandatory Red-Green-Refactor phases to ensure high code quality and test coverage.
- Context-Aware Collaboration: Serving as a single source of truth for the repository, allowing AI agents to maintain deep, persistent awareness of project history and architectural decisions.
| name | conductor-context |
|---|---|
| description | Use this skill when the user mentions "plan", "track", "spec", "conductor", asks about project progress, or references conductor files like plan.md, spec.md, tracks.md, product.md, tech-stack.md, or workflow.md. Also use when the user wants to understand the Conductor methodology or Context-Driven Development workflow. |
| version | 0.1.0 |
Conductor: Context-Driven Development
Conductor is a workflow methodology that transforms Claude Code into a project manager following a strict protocol: Context -> Spec & Plan -> Implement.
Core Philosophy
Measure twice, code once. By treating context as a managed artifact alongside code, you transform your repository into a single source of truth that drives every agent interaction with deep, persistent project awareness.
Key Concepts
Tracks
A track is a high-level unit of work (feature or bug fix). Each track has:
spec.md- Detailed requirements and acceptance criteriaplan.md- Actionable to-do list with phases, tasks, and sub-tasksmetadata.json- Track metadata (ID, type, status, timestamps)
Tracks are stored in conductor/tracks/<track_id>/.
Project Context Files
Located in the conductor/ directory:
product.md- Product vision, goals, users, featuresproduct-guidelines.md- Prose style, brand messaging, visual identitytech-stack.md- Languages, frameworks, databases, toolsworkflow.md- Development methodology (TDD, commit strategy)tracks.md- Master list of all tracks and their statuscode_styleguides/- Language-specific coding standards
Task Status Markers
[ ]- Pending (not started)[~]- In progress (currently being worked on)[x]- Completed (finished and committed)
Workflow Phases
- Setup - Initialize project context (run once)
- New Track - Create spec and plan for feature/bug
- Implement - Execute tasks following TDD workflow
- Status - Check progress across tracks
- Revert - Git-aware rollback of tracks/phases/tasks
File Locations
When a user mentions "the plan" or "the spec", they likely refer to:
- Current track's plan:
conductor/tracks/<track_id>/plan.md - Current track's spec:
conductor/tracks/<track_id>/spec.md - Master tracks list:
conductor/tracks.md
TDD Workflow
Conductor follows Test-Driven Development by default:
- Red Phase - Write failing tests first
- Green Phase - Implement minimum code to pass tests
- Refactor - Clean up with safety of passing tests
Phase Completion Protocol
At the end of each phase:
- Ensure test coverage (>80% target)
- Manual verification with user
- Create checkpoint commit
- Attach git notes with verification report
- Update plan.md with checkpoint SHA
Commands Reference
| Command | Purpose |
|---|---|
/conductor:setup |
Initialize project context |
/conductor:new-track |
Create new feature/bug track |
/conductor:implement |
Execute tasks from plan |
/conductor:status |
Display progress overview |
/conductor:revert |
Rollback tracks/phases/tasks |
Template Location
Templates are bundled with the plugin at ${CLAUDE_PLUGIN_ROOT}/templates/:
workflow.md- Default workflow configurationcode_styleguides/- Language-specific style guides