eve-orchestration
Eve Orchestration
This skill explains how to orchestrate complex work in Eve Horizon by spawning child jobs, managing dependencies, and maximizing parallel execution while respecting depth limits.
Core Principles
- Parent sets a target depth and passes it to children.
- Each job decides its own decomposition based on scope and depth.
- Parallelize by default when tasks can proceed independently.
- Use relations to encode true dependencies, not preference.
- Leaf jobs execute; parent jobs orchestrate and wait.
- Orchestrators stay lightweight — dispatch work, don't accumulate it.
When to Orchestrate vs Execute Directly
Not every job needs decomposition. Use this heuristic:
More from incept5/eve-skillpacks
eve-web-ui-testing-agent-browser
Web UI testing and browser automation. Use Vercel agent-browser for general apps, or the repo-pinned Playwright wrapper inside Eve Horizon. Use when tasks require opening pages, interacting with forms, validating UI flows, taking screenshots, extracting page data, or running repeatable browser-based checks locally or in CI.
345eve-auth-and-secrets
Authenticate with Eve, manage project secrets, and add SSO login to Eve-deployed apps.
266eve-skill-distillation
Distill repeated work into Eve skillpacks by creating or updating skills with concise instructions and references. Use when a workflow repeats or knowledge should be shared across agents.
265eve-job-lifecycle
Create, manage, and review Eve jobs, phases, and dependencies. Use when running knowledge work in Eve or structuring job hierarchies.
261eve-new-project-setup
Configure a new Eve Horizon project after running eve init (profile, auth, manifest, and repo linkage).
261eve-plan-implementation
Execute software engineering plan documents using Eve jobs, dependencies, and review gating.
259