跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
搜索与研究

orchestrate

Use this skill when coordinating independent agents with explicit ownership, dependencies, integration, and verification. Activates on mentions of swarm, parallel agents, multi-agent, orchestrate, fan-out, wave dispatch, research army, unleash, dispatch agents, or parallel work.

hyperb1iss · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add hyperb1iss/hyperskills --skill orchestrate

技能说明


name: orchestrate description: Use this skill when coordinating independent agents with explicit ownership, dependencies, integration, and verification. Activates on mentions of swarm, parallel agents, multi-agent, orchestrate, fan-out, wave dispatch, research army, unleash, dispatch agents, or parallel work.

Multi-Agent Orchestration

Use independent agents to add useful capacity while keeping one coherent result. Partition by the questions, artifacts, and resources that can progress independently. The coordinator owns integration and the final claim of completion.

The user's instructions take precedence over this skill's guidelines. Delegation, tools, and external actions remain subject to current host instructions and authorization. This skill does not grant a worker broader authority than the coordinator has.

Check Capabilities Before Dispatch

Inspect the available tools and their current schemas. Hosts differ in agent lifecycle, inherited context, filesystem sharing, worktree isolation, asynchronous results, and permissions. Discover those properties instead of inferring them from a product name or copying stale arguments.

Use the host's supported delegation tools when permitted. An external CLI reviewer still consumes resources and remains subject to delegation and permission rules; it is not an escape hatch around a restriction. Without a suitable delegation surface, execute directly or prepare tasks for authorized external workers. A task queue alone does not launch an agent.

Choose the Shape by Dependency

Work shapeCoordination pattern
Independent research questionsParallel investigators, evidence-based synthesis
Disjoint feature ownership with stable interfacesParallel builders, designated integration owner
One change repeated across modulesScoped automated transform or partitioned workers, combined verification
Dependent edits or shared mutable stateOne owner for the dependency, parallelize work around it
Consequential reviewIndependent read-only reviewers with useful risk lenses
Small, tightly coupled changeDirect execution

Agent count follows named useful lanes, available capacity, and integration cost. More agents are worthwhile when they add distinct evidence or shorten independent work. Do not use historical fleet sizes as defaults. Check the critical path: accelerating a branch that is already waiting on one shared interface may add no throughput.

Establish Ownership and Integration

Before launching builders, inspect repository status and existing worktrees. Map shared resources as well as files: generated artifacts, schemas, lockfiles, database fixtures, ports, build outputs, and package caches can collide across otherwise disjoint modules.

Choose isolation based on the work:

IsolationAppropriate useRequired coordination
Shared tree, disjoint pathsSmall independent changes with clear ownershipSingle owner for contended files and Git index operations
Separate worktreesWorkers need independent branches or build stateKnown base, branch/path, merge order, and integration owner
Read-only revisionReview or researchFixed revision/diff plus permitted scratch outputs

Worktrees isolate tracked files and the index; they do not automatically isolate ports, databases, or external services. Follow the project's worktree layout. Never overwrite a human's or sibling's edits to clear a conflict.

For shared trees, let workers report patches and checks while one coordinator stages and commits scoped changes, unless another explicit ownership scheme is agreed. Avoid broad staging and repository-wide autofixes during concurrent editing. Inspect hook side effects before accepting a commit. For lock contention, investigate the actual owner; an inconclusive process listing does not establish that a lock is safe to remove. Consult git for recovery.

Define how partial progress becomes integrated progress before dispatch. Name the artifact each consumer expects and the condition under which it is ready. Do not leave completed branches without an owner to inspect and combine them.

Write Briefs That Transfer the Necessary Context

Give each worker the original relevant request and a bounded assignment. Include facts that are expensive to rediscover or absent from their checkout, especially user corrections and untracked decisions. Use absolute paths and exact revisions when location matters.

Brief elementPurpose
Outcome and scopeThe result needed, owned surfaces, and exclusions
Current evidenceRelevant code, versions, interfaces, and verified premises
DependenciesWhat is ready, what is promised, and who owns it
AuthorityPermitted mutations, commit rights, external actions
VerificationChecks and acceptance conditions for this contribution
ReturnChanged artifacts or findings, evidence, limita
阅读完整来源 ↗