npx skills add https://github.com/incept5/eve-skillpacks --skill eve-orchestration此技能解释了如何在 Eve Horizon 中编排复杂工作,通过生成子作业、管理依赖关系以及最大化并行执行,同时遵守深度限制。
并非每个作业都需要分解。使用以下启发式方法:
在决定任何事情之前,先获取当前作业的上下文:
eve job current --json
# 或显式指定
eve job current $EVE_JOB_ID --json
使用上下文来确认:
job.depth(当前深度)children(现有的子作业)relations(依赖关系)blocked / / 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.
Not every job needs decomposition. Use this heuristic:
Fetch the current job context before deciding anything:
eve job current --json
# or explicit
eve job current $EVE_JOB_ID --json
Use the context to confirm:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
waitingeffective_phase使用环境变量来避免猜测标识符:
EVE_JOB_ID:当前作业EVE_PROJECT_ID:所属项目EVE_ATTEMPT_ID:当前尝试EVE_REPO_PATH:工作空间路径EVE_AGENT_ID:代理标识符(可选)父作业决定目标深度并将其传递给子作业(在子作业描述或数据中)。每个子作业必须读取并遵守相同的目标深度。
包含在子作业描述中的示例片段:
Target depth: 3 (EPIC). Current depth: 1.
If current depth < target, you may create child jobs and use waits_for relations to parallelize.
If current depth >= target, execute directly.
如果未提供目标深度,则默认为 Story 深度(2),除非范围明确指示为 EPIC。
编排器最宝贵的资源是其上下文窗口。请保护它:
一个运行良好的编排器在完成时应消耗其大部分上下文预算。
eve job current --json)。current_depth >= target_depth,则直接执行。waits_for 进行标准门控。blocks。使用 eve job create 并指定 --parent 来创建子作业。每个子作业描述必须是完全自包含的——子代理无法访问父作业的对话、上下文或推理。子作业执行所需的一切都必须在其描述本身中。
# 并行创建两个子作业
eve job create --project $EVE_PROJECT_ID \
--parent $EVE_JOB_ID \
--description $'Target depth: 3 (EPIC). Current depth: 1.\nScope: Research sources\nDeliverable: Annotated bibliography' \
--phase ready
eve job create --project $EVE_PROJECT_ID \
--parent $EVE_JOB_ID \
--description $'Target depth: 3 (EPIC). Current depth: 1.\nScope: Draft outline\nDeliverable: Structured outline' \
--phase ready
创建子作业后,添加依赖关系以便父作业等待它们:
eve job dep add $EVE_JOB_ID $CHILD_A_ID --type waits_for
eve job dep add $EVE_JOB_ID $CHILD_B_ID --type waits_for
使用 CLI 依赖关系命令来表达关系:
eve job dep add $PARENT_JOB_ID $CHILD_JOB_ID --type waits_for
eve job dep add $CHILD_JOB_ID $OTHER_JOB_ID --type blocks
eve job dep list $JOB_ID
关系指南:
waits_for:标准父作业等待子作业完成blocks:严格的排序约束conditional_blocks:仅当依赖关系是条件性时使用在返回等待控制信号之前添加关系。
当您生成子作业并设置关系后,使用等待信号暂停父作业:
{
"eve": {
"status": "waiting",
"summary": "Spawned 3 parallel child jobs; waiting on waits_for relations"
}
}
规则:
waiting。waiting 将作业重新排队到 ready 状态,同时它保持被关系阻塞。waiting 会触发短暂退避;请避免这种情况。success。failed。默认:除非父作业或项目设置明确要求,否则不进行审查。
如果需要审查:
在指定级别应用(仅顶层、所有级别或无)。
返回 waiting 时不要提交审查。
仅在作业完成时提交审查。
eve job submit $EVE_JOB_ID --summary "Completed work and ready for review"
当父作业在子作业完成后恢复时:
如果子作业失败:
每个子作业描述必须是自包含的。子代理从零开始——无法访问父作业的对话、读取的文件或推理。包含它所需的一切:
Target depth: 3 (EPIC). Current depth: 1.
If current depth < target, you may create child jobs and use waits_for relations to parallelize.
If current depth >= target, execute directly.
Context: <此工作存在的原因——为子作业提供足够的背景信息以便其行动而无需询问>
Scope: <简洁的子目标——要做什么>
Inputs: <子作业需要的具体文件路径、数据引用或先前输出>
Deliverable: <清晰、可验证的结果——"完成"是什么样子>
Constraints: <需要遵守的边界、标准或要求>
子作业描述的关键规则:
/src/auth/handler.ts 以添加令牌刷新逻辑"是可操作的。json-result 等待(如果存在子作业)每周安装次数
158
仓库
首次出现
2026年2月8日
安全审计
安装于
gemini-cli158
codex158
claude-code150
pi55
opencode41
github-copilot41
job.depth (current depth)children (existing sub-jobs)relations (dependencies)blocked / waiting / effective_phaseUse the environment to avoid guessing identifiers:
EVE_JOB_ID: current jobEVE_PROJECT_ID: owning projectEVE_ATTEMPT_ID: current attemptEVE_REPO_PATH: workspace pathEVE_AGENT_ID: agent identifier (optional)The parent decides the target depth and passes it to children (in the child description or data). Each child must read and honor the same target depth.
Example snippet to include in child descriptions:
Target depth: 3 (EPIC). Current depth: 1.
If current depth < target, you may create child jobs and use waits_for relations to parallelize.
If current depth >= target, execute directly.
EPIC: target depth = 3
Story: target depth = 2
If no target depth is provided, default to Story depth (2) unless the scope clearly indicates EPIC.
The orchestrator's most precious resource is its context window. Protect it:
A well-run orchestrator should finish with most of its context budget unspent.
eve job current --json).current_depth >= target_depth, execute directly.waits_for for standard gating.blocks only for strict ordering constraints.Create child jobs using eve job create with --parent. Each child description must be fully self-contained — the child agent has no access to the parent's conversation, context, or reasoning. Everything the child needs to act must be in the description itself.
# Create two child jobs in parallel
eve job create --project $EVE_PROJECT_ID \
--parent $EVE_JOB_ID \
--description $'Target depth: 3 (EPIC). Current depth: 1.\nScope: Research sources\nDeliverable: Annotated bibliography' \
--phase ready
eve job create --project $EVE_PROJECT_ID \
--parent $EVE_JOB_ID \
--description $'Target depth: 3 (EPIC). Current depth: 1.\nScope: Draft outline\nDeliverable: Structured outline' \
--phase ready
After creating children, add dependencies so the parent waits on them:
eve job dep add $EVE_JOB_ID $CHILD_A_ID --type waits_for
eve job dep add $EVE_JOB_ID $CHILD_B_ID --type waits_for
Use the CLI dependency commands to express relationships:
eve job dep add $PARENT_JOB_ID $CHILD_JOB_ID --type waits_for
eve job dep add $CHILD_JOB_ID $OTHER_JOB_ID --type blocks
eve job dep list $JOB_ID
Relation guidance:
waits_for: standard parent waits for child completionblocks: strict ordering constraintconditional_blocks: use only when the dependency is conditionalAdd relations before returning a waiting control signal.
When you spawn children and set relations, pause the parent with a waiting signal:
{
"eve": {
"status": "waiting",
"summary": "Spawned 3 parallel child jobs; waiting on waits_for relations"
}
}
Rules:
waiting after dependencies exist.waiting requeues the job to ready while it stays blocked by relations.waiting without blockers triggers a short backoff; avoid it.success when the work is complete.failed only for unrecoverable outcomes.Default: no review unless explicitly required by the parent or project settings.
If review is required:
Apply at the specified level (top only, all levels, or none).
Do not submit for review when returning waiting.
Submit for review only when the job is complete.
eve job submit $EVE_JOB_ID --summary "Completed work and ready for review"
When a parent resumes after children complete:
If a child fails:
Every child description must be self-contained. The child agent starts cold — no access to the parent's conversation, files read, or reasoning. Include everything it needs:
Target depth: 3 (EPIC). Current depth: 1.
If current depth < target, you may create child jobs and use waits_for relations to parallelize.
If current depth >= target, execute directly.
Context: <why this work exists — enough background for the child to act without asking>
Scope: <concise child objective — what to do>
Inputs: <specific file paths, data references, or prior outputs the child needs>
Deliverable: <clear, verifiable outcome — what "done" looks like>
Constraints: <boundaries, standards, or requirements to honor>
Key rules for child descriptions:
/src/auth/handler.ts to add token refresh logic" is actionable.json-result waiting (if children exist)Weekly Installs
158
Repository
First Seen
Feb 8, 2026
Security Audits
Installed on
gemini-cli158
codex158
claude-code150
pi55
opencode41
github-copilot41
使用Recharts构建分析与指标仪表板:折线图、柱状图与KPI卡片组件教程
156 周安装
Hummingbot connectors-available: 测试交易所连接器可用性,搜索代币交易规则
156 周安装
Hyvä CMS组件导出工具 - 一键合并Magento模块组件定义JSON
156 周安装
飞书/ Lark API 命令行工具 - 自动化消息、文档、表格与日历管理 | feishu-lark-agent
156 周安装
世界构建诊断技能:识别虚构设定问题,提供改进建议,打造深度可信世界观
156 周安装
可观测性审计工具:自动化检测日志、监控、追踪的代码审计技能
156 周安装