eve-plan-implementation
Eve Plan Implementation (Jobs)
Translate a plan document into Eve jobs, parallelize work, and drive review/verification through job phases and dependencies.
Orchestration model: The root epic is the orchestrator — it plans, delegates, and coordinates but does not execute heavy work itself. Phase jobs are sub-orchestrators that break a phase into tasks. Task jobs are workers — each one receives a self-contained description and executes independently with no access to the parent's context.
When to Use
- A plan/spec exists and the work should be orchestrated as Eve jobs.
- The initial job says "use eve-plan-implementation to implement the plan."
Workflow
1) Load context (orchestrator)
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-orchestration
Orchestrate jobs via depth propagation, parallel decomposition, relations, and control signals
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).
261