Eve Plan Implementation

This breaks down software engineering plans into parallelized Eve jobs with proper orchestration and gating. The root epic delegates to phase jobs, which spawn atomic task workers that run independently. It pushes context into child job descriptions since workers can't see parent state, which keeps orchestrators lightweight and avoids redundant analysis. The workflow mirrors bead's epic-phase-task hierarchy but uses Eve's dependency system and review gates. Use it when you have a plan document and want orchestrated execution instead of sequential implementation. The waiting signal pattern after spawning children is smart: orchestrators yield resources while parallel work happens downstream.

skills.sh installs: 306
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add incept5/eve-skillpacks --skill eve-plan-implementation --agent claude-code

Installs into .claude/skills of the current project.

Files

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)

Read the plan doc and extract phases, deliverables, and blockers.
If present, read AGENTS.md for repo-specific rules.
Fetch current job context:
```
eve job current --json
```
Stay lightweight: the orchestrator reads just enough to plan the breakdown. Delegate deep analysis (reading large files, exploring code) to worker jobs.