Load project context efficiently for Conductor workflows. Use when starting work on a track, implementing features, or needing project context without consuming excessive tokens.
Loads project context efficiently for Conductor workflows by scanning tracked files and reading priority documents (manifests, specs, plans) while respecting ignore files. Use when starting work on a track, implementing features, or needing project context without consuming excessive tokens.
/plugin marketplace add pilotparpikhodjaev/conductor_cc/plugin install conductor@conductor-ccThis skill inherits all available tools. When active, it can use any tool Claude has access to.
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]
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.