From conductor
Loads project context efficiently for Conductor workflows. Use when starting a track, implementing features, or needing context without consuming excessive tokens.
How this skill is triggered — by the user, by Claude, or both
Slash command
/conductor:context-loaderThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Efficiently load and manage project context for Conductor's context-driven development workflow.
Efficiently load and manage project context for Conductor's context-driven development workflow.
Use this skill when:
/conductor:implement workflowBefore scanning files, check for:
.claudeignore - Claude-specific ignores.gitignore - Standard git ignores# Check for ignore files
ls -la .claudeignore .gitignore 2>/dev/null
Use git for tracked files:
git ls-files --exclude-standard -co | head -100
For directory structure:
git ls-files --exclude-standard -co | xargs -n 1 dirname | sort -u
| Priority | File Type | Examples |
|---|---|---|
| 1 | Manifests | package.json, Cargo.toml, pyproject.toml |
| 2 | Conductor | conductor/product.md, conductor/tech-stack.md |
| 3 | Track | conductor/tracks/<id>/spec.md, plan.md |
| 4 | Config | tsconfig.json, .env.example |
For files over 1MB:
1. Load CLAUDE.md (if exists)
2. Load conductor/product.md (project vision)
3. Load conductor/tech-stack.md (technical context)
4. Load current track spec.md (requirements)
5. Load current track plan.md (tasks)
After loading context, summarize:
## Project Context Loaded
**Product**: [one-line summary]
**Tech Stack**: [key technologies]
**Current Track**: [track name/id]
**Active Phase**: [current phase]
**Pending Tasks**: [count]
npx claudepluginhub tenxengineer/conductor_ccLoads optimized project context for Conductor workflows via git-tracked files, ignores, and priority manifests/tracks. Use for new tracks, features, or context needs.
Auto-loads Conductor project context from conductor/ directory (product.md, tech-stack.md, workflow.md, tracks.md) when it exists, for development tasks aligned with goals, stack, and processes.
Guides implementing context-driven development: manage artifacts like product.md alongside code for consistent AI interactions, team alignment, onboarding, and workflow from context to implementation.