SkillsAdd

smithery.ai

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.

First seen Mar 23, 2026

Installation

$ npx skills add https://smithery.ai
View on skills.sh ↗ Website ↗

Summary

  • 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.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

find-skills Same topic
vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…

3.3M installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-prepare Same topic
microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…

568.3K installs

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai
smithery-ai-cli 7.8K frontend-design 6.2K skill-creator 2.5K ck:ui-ux-pro-max 1.3K pdf 1.2K xlsx 966 pptx 894 docx 884 webapp-testing 1 web-design-reviewer 657

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version0.1.0
Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,357 B
  • docs SUMMARY.md 345 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

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 criteria
  • plan.md - Actionable to-do list with phases, tasks, and sub-tasks
  • metadata.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, features
  • product-guidelines.md - Prose style, brand messaging, visual identity
  • tech-stack.md - Languages, frameworks, databases, tools
  • workflow.md - Development methodology (TDD, commit strategy)
  • tracks.md - Master list of all tracks and their status
  • code_styleguides/ - Language-specific coding standards

Task Status Markers

  • [ ] - Pending (not started)
  • [~] - In progress (currently being worked on)
  • [x] - Completed (finished and committed)

Workflow Phases

  1. Setup - Initialize project context (run once)
  2. New Track - Create spec and plan for feature/bug
  3. Implement - Execute tasks following TDD workflow
  4. Status - Check progress across tracks
  5. 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:

  1. Red Phase - Write failing tests first
  2. Green Phase - Implement minimum code to pass tests
  3. Refactor - Clean up with safety of passing tests

Phase Completion Protocol

At the end of each phase:

  1. Ensure test coverage (>80% target)
  2. Manual verification with user
  3. Create checkpoint commit
  4. Attach git notes with verification report
  5. 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 ${CLAUDEPLUGINROOT}/templates/:

  • workflow.md - Default workflow configuration
  • code_styleguides/ - Language-specific style guides