help
Get help with Conductor - commands, usage examples, and best practices
What this skill does
plugin: conductor
updated: 2026-01-20
# Conductor Help
Conductor implements Context-Driven Development for Claude Code.
## Philosophy
**Context as a Managed Artifact:**
Your project context (goals, tech stack, workflow) is documented and maintained alongside your code. This context guides all development work.
**Pre-Implementation Planning:**
Before coding, create a spec (WHAT) and plan (HOW). This ensures clear direction and traceable progress.
**Safe Iteration:**
Human approval gates at key points. Git-linked commits for traceability. Easy rollback when needed.
## Available Skills
### conductor:setup
Initialize Conductor for your project.
- Creates conductor/ directory structure
- Generates product.md, tech-stack.md, workflow.md
- Interactive Q&A with resume capability
### conductor:new-track
Create a new development track.
- Generates spec.md with requirements
- Creates hierarchical plan.md (phases -> tasks)
- Updates tracks.md index
### conductor:implement
Execute tasks from your plan.
- Status progression: [ ] -> [~] -> [x]
- Git commits linked to track/task
- Follows workflow.md procedures
### conductor:status
View project progress.
- Overall completion percentage
- Current task and blockers
- Multi-track overview
### conductor:revert
Git-aware logical undo.
- Revert at Track, Phase, or Task level
- Preview before executing
- State validation after revert
## Quick Start
1. **Initialize:** Run `conductor:setup` to create context files
2. **Plan:** Run `conductor:new-track` to create your first track
3. **Implement:** Run `conductor:implement` to start working
4. **Check:** Run `conductor:status` to see progress
5. **Undo:** Run `conductor:revert` if you need to roll back
## Directory Structure
```
conductor/
├── product.md # Project vision and goals
├── tech-stack.md # Technical preferences
├── workflow.md # Development procedures
├── tracks.md # Index of all tracks
└── tracks/
└── {track_id}/
├── spec.md # Requirements specification
├── plan.md # Hierarchical task plan
└── metadata.json
```
## Best Practices
1. **Keep Context Updated:** Review product.md and tech-stack.md periodically
2. **One Task at a Time:** Focus on completing tasks fully before moving on
3. **Commit Often:** Each task should result in at least one commit
4. **Use Blockers:** Mark tasks as [!] blocked rather than skipping silently
5. **Review Before Proceeding:** Use phase gates to verify quality
## Troubleshooting
**"Conductor not initialized"**
Run `conductor:setup` to initialize the conductor/ directory.
**"Track not found"**
Check tracks.md for available tracks. Track IDs are case-sensitive.
**"Revert failed"**
Check for uncommitted changes. Commit or stash before reverting.
## Getting Help
Use `conductor:help` anytime for this reference.
For issues, check the project documentation or file an issue.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.