Context-Driven Development skill for projects using Conductor. Use this skill when you detect a `conductor/` directory in the project, when working on tasks defined in a `plan.md` file, or when the user asks about tracks, specs, or plans. Automatically applies TDD workflow, tracks task completion, and follows the spec-driven methodology.
/plugin marketplace add fcoury/conductor/plugin install conductor@conductorThis skill inherits all available tools. When active, it can use any tool Claude has access to.
This skill enables Claude to work effectively on projects managed by the Conductor framework - a spec-driven, structured development methodology.
Claude should automatically apply this skill when:
conductor/ directory exists in the project rootconductor/tracks.md, conductor/workflow.md, or conductor/product.md are present/conductor:* commandplan.md[ ] → [~] → [x])When working on a Conductor project, familiarize yourself with:
conductor/
├── product.md # Product vision and goals
├── product-guidelines.md # Brand voice and communication style
├── tech-stack.md # Technology choices and constraints
├── workflow.md # Development methodology and procedures
├── tracks.md # Master list of all tracks
├── code_styleguides/ # Language-specific style guides
│ ├── general.md
│ ├── python.md
│ └── [others]
└── tracks/ # Individual track folders
└── <track_id>/
├── spec.md # Feature specification
├── plan.md # Implementation plan with tasks
└── metadata.json # Track metadata
When implementing a task from a Conductor plan:
[ ]) in the track's plan.md[~]conductor/code_styleguides/feat(auth): Add login form)[x] and append commit SHAconductor(plan): Mark task 'X' as completeWhen completing a phase:
plan.md with checkpoint SHA[ ] - Pending (not started)[~] - In Progress (currently working)[x] - Completed (done with commit SHA)Remind users of available Conductor commands:
/conductor:setup - Initialize Conductor in a project/conductor:new-track - Create a new feature/bug track/conductor:implement - Execute tasks from the current track/conductor:status - Show project progress/conductor:revert - Git-aware revert of tracks/phases/tasksBefore starting any implementation work, always load:
conductor/workflow.md - For task lifecycle proceduresconductor/tech-stack.md - For technology constraintsspec.md - For requirementsplan.md - For current task statusConductor tracks work through Git:
plan.md for traceabilityIf something goes wrong:
/conductor:revert)Before marking any task complete, verify:
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.