orchestration
Coordinates other skills and agents. ALWAYS use this skill on startup.
When & Why to Use This Skill
The Orchestration skill serves as the central command layer for Claude agents, designed to manage and synchronize multiple specialized skills within a single workflow. It optimizes developer productivity by automating the handoff between tools like Git, testing frameworks, and CLI utilities, ensuring that complex tasks follow a standardized, error-free execution path from startup to completion.
Use Cases
- End-to-End Workflow Automation: Automatically sequences code quality checks, build verifications, and Git commits before finalizing a task to ensure high-standard delivery.
- Intelligent Agent Delegation: Routes specific technical operations—such as merge conflict resolution or upstream rebasing—to specialized sub-agents for expert-level handling.
- Environment & Policy Enforcement: Maintains system integrity by enforcing secure file-writing protocols and managing localized context within dedicated .llm directories.
- Plugin & Toolchain Health Checks: Runs comprehensive diagnostic scripts to verify the presence of required binaries and correct permissions across the entire development environment.
| name | orchestration |
|---|---|
| description | Coordinates other skills and agents. ALWAYS use this skill on startup. |
Skill Guidelines
Invoke these skills liberally - most tasks use multiple skills:
| Skill | When to use |
|---|---|
@code:code-quality |
Before editing code |
@code:testing |
When writing or reviewing tests |
@code:cli |
When running shell commands |
@build:precommit |
Before running builds or tests |
@git:git-workflow |
For all git operations |
@orchestration:conversation-style |
For response guidelines |
@orchestration:llm-context |
When working with .llm/ directories |
Git Commits
ALWAYS delegate to the @git:commit-handler agent for all commit operations. Never run git commit directly.
ALWAYS delegate to the @git:conflict-resolver agent to resolve any git merge or rebase conflicts.
ALWAYS delegate to the @git:rebaser agent to rebase the current branch on upstream.
File Writing Policy
NEVER write files to /tmp or other system temporary directories - reading from /tmp triggers permission prompts. Write scratch files and temporary outputs to .llm/ instead.
Workflow Orchestration
When a code change is ready, and we are about to return control to the user, do these things in order:
- Verify the build passes using the
@build:precommit-runneragent - Commit to git using the
@git:commit-handleragent - Rebase on top of the upstream branch with the
@git:rebaseragent
Plugin Health Check
Run the master doctor script to verify all plugins are properly configured:
scripts/doctor-all.sh
This runs doctor.sh from each plugin, checking for:
- Required binaries (just, git, gh, python3, tmux, etc.)
- Required files and scripts
- Proper file permissions