New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Requirement Parallel Orchestration

by devcodex-labs in devcodex-labs/devcodex

多需求与宿主原生子 Agent 编排 Skill — 先判断工作项独立性，再以新鲜宿主能力、租约、隔离证据和根 Agent 单写者完成受控派发或自动串行回退。

AGPL-3.0Auto-check passed

Install Requirement Parallel Orchestration

skills CLI
$ npx skills add devcodex-labs/devcodex --skill requirement-parallel-orchestration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install devcodex-labs/devcodex requirement-parallel-orchestration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/devcodex-labs/devcodex.git skills-src && mkdir -p .claude/skills && cp -r skills-src/content/skills/requirement-parallel-orchestration .claude/skills/requirement-parallel-orchestration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
requirement-parallel-orchestration
GitHub stars
439
Token cost
~2.2k tokens
SKILL.md length
654 words
Files
2
Skills in repo
70
Repo updated
First seen
Licence
AGPL-3.0

At a glance

多需求与宿主原生子 Agent 编排 Skill — 先判断工作项独立性，再以新鲜宿主能力、租约、隔离证据和根 Agent 单写者完成受控派发或自动串行回退。

  • Works in 5 steps: work item id 必须唯一；调用方与 child 提供的… → read-only/isolated-validation… → lease 未过期、cancel fence 未变化、root 尚未接管串行； → …
  • SKILL.md covers 职责, 触发条件, 输入契约 and 判定门禁, plus 7 more sections
  • Calls git and npm

What it does

Requirement Parallel Orchestration is an agent skill from devcodex-labs/devcodex. 多需求与宿主原生子 Agent 编排 Skill — 先判断工作项独立性，再以新鲜宿主能力、租约、隔离证据和根 Agent 单写者完成受控派发或自动串行回退。

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `intent.json`).

The repository describes itself as: Intent-driven AI coding workflow runtime for consistent context, skills, approvals, validation, and handoffs across six AI coding hosts. The licence is AGPL-3.0.

Example prompts

  • “/requirement-parallel-orchestration”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. work item id 必须唯一；调用方与 child 提供的 realpath 必须原生为绝对路径，且全部落在 lease 允许根内，没有触碰禁止共享面；
  2. read-only/isolated-validation 没有源码写入；worktree patch 有摘要和独立验证；
  3. lease 未过期、cancel fence 未变化、root 尚未接管串行；
  4. child 启动的 temp/worktree/service 已清理，无 owned residue；
  5. 结果按冻结 merge order 串行复证、应用和 root retest。

What it can do on your machine

Read from SKILL.md and the folder at commit 1dd4525. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Requirement Parallel Orchestration loads about 2.2k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 654 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~29
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from devcodex-labs/devcodex at commit 1dd4525, republished under its AGPL-3.0 licence (© devcodex-labs). 654 words, ~2,233 tokens.

Download SKILL.mdSave it as .claude/skills/requirement-parallel-orchestration/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
requirement-parallel-orchestration
description
多需求与宿主原生子 Agent 编排 Skill — 先判断工作项独立性，再以新鲜宿主能力、租约、隔离证据和根 Agent 单写者完成受控派发或自动串行回退。

Requirement Parallel Orchestration Skill

职责

本 Skill 负责在进入源码实现、修复执行、长流程 Auto 或子会话派发前，判断多个需求/任务是否可以并行推进。它补齐的是执行前编排判定层，不替代 intent、cp-gate、execution-contract、test-router、report 或 memory。

默认原则：缺少证据时返回 serial-required；只有写入面、CP 状态、共享状态和汇合协议都可验证时，才允许输出 ParallelLaunchCardV1。LaunchCard 仍只是计划，不能证明宿主已经派发子 Agent；只有 HostSubagentDispatchPlanV1.status=parallel-eligible、有效 AgentWorkLeaseV1 和实际宿主工具结果同时存在时才可派发。

触发条件

场景是否触发
用户要求多个需求/任务“并行推进”“同时做”“开多个子任务/子 Agent”必须
当前会话准备同时推进 ≥2 个 requirement / bug / optimization / scenario-test必须
Auto、长流程或控制面任务计划拆分为多个可执行 work item必须
只读搜索、Profile/记忆读取或互不写输出的验证并行N/A，按 ConcurrencyPolicy 执行
单一需求的普通串行实现N/A + skipReason

输入契约

ActiveWorkInventoryV1
字段要求
activeRoot当前绑定 active-root；不得跨项目混入
workItems[]每个 requirement / bug / optimization / scenario-test / current task
workItems[].id稳定任务标识
workItems[].cpStateCP1/CP2/CP3 confirmed/pending/stale
workItems[].allowedPaths当前 work item 被允许触碰的路径
workItems[].expectedWrites预期写入路径、surface、writeKind、owner
sourceRefs[]sessions、memory_status、SUMMARY、CP artifact、用户消息或报告锚点
freshnesscurrent / summary-only / stale / unknown

信息不足时不得猜测独立，返回 serial-required + insufficient-*。

判定门禁

RequirementIndependenceGate
status判定条件输出
independentallowedPaths 不重叠，未共享控制面写入，CP/记忆/report/ledger 单写者不竞争，且汇合协议完整ParallelLaunchCardV1[]
weakly-coupled-lock主路径独立，但共享 skill-portfolio、validation-manifest、package-boundary、memory、report、ledger 或 host-deploy 等单写者面lock map、singleWriter、checkpoint、serial merge order
serial-required共享同一源码文件、同一 CP/task state、同一 audit session，或无法证明写入面独立blocker reason、recommended order、needed evidence
SharedSurfaceLockMapV1

核心共享面：

  • active-root
  • cp-state
  • memory
  • report
  • ledger
  • audit-session
  • source-mutation
  • package-boundary
  • validation-manifest
  • skill-portfolio
  • host-deploy

source-mutation 只有在路径不重叠且存在完整 merge protocol 时才可能进入 independent。其他共享控制面默认进入 weakly-coupled-lock，由主会话或指定 single writer 串行写入。

ParallelLaunchCardV1

只有 independent 判定可以输出 LaunchCard。必填字段：

字段要求
requirementId对应 work item id
displayName用户可识别名称
activeRoot绑定根
allowedPaths非空路径数组
forbiddenSharedSurfaces核心共享面数组
sessionPrompt子会话可复制 prompt，必须包含 stop 条件
isolationModesame-active-root-disjoint-paths / separate-worktree / separate-project-root
mergeProtocolIntegrationMergeProtocolV1
validationRoute至少一条验证命令或 selector
stopCondition触碰禁止面、dirty 外溢、验证失败或 CP stale 时停止

缺字段返回 launch-card-invalid；缺 merge protocol 返回 integration-protocol-missing。

IntegrationMergeProtocolV1

字段要求
mergeOrder串行汇合顺序；不能“谁先完成谁合并”
conflictChecksgit diff --name-only、共享 manifest/portfolio/package/docs/Profile 检查
validationRoutechanged/control-plane/profile-deploy/requirement artifacts 等
reportMemoryOwner最终 report/memory 单写者
failureAction冲突、缺验证或 dirty 混合归属时回 serial/CP

宿主原生执行合同

HostNativeCollaborationCapabilityV1

宿主能力必须由当前根 Agent 可观察的工具清单或直接调用结果生成，且至少绑定 spawn、wait、interrupt 的实际工具名、host/variant、支持模式、fanout/depth、observedAt/expiresAt、证据引用和 capabilityDigest。官方文档、AGENTS/Skill 文本、生成配置、其他宿主回执或工具名称猜测都不能作为 direct evidence。

能力缺失、过期、摘要不符或不支持所需隔离模式时，输出完整 serial fallback；不得询问用户重新确认，也不得因为“没有多 Agent”停止主任务。

HostSubagentDispatchPlanV1

根 Agent 在派发前生成一份 immutable plan，至少绑定：

  • 当前 taskId/viewDigest/activeRoot、sourceHead/dirtyDigest；
  • work items、RequirementIndependenceDecisionV1、SharedSurfaceLockMapV1 与固定 merge order；
  • 当前宿主 capability identity 与实际 operation bindings；
  • fanout≤4、depth=1、time/cost gate；
  • serialFallback 的同一 work graph、根单写者和 reason codes；
  • planDigest。

只有预计串行耗时至少 120 秒、预计节省至少 60 秒、协调成本不超过总量 25%，且所有工作项和宿主证据满足条件时，plan 才能是 parallel-eligible。默认 fanout=3，实际值取 work item 数、宿主上限与 4 的最小值。

AgentWorkLeaseV1

每个 child 必须有独立 lease，绑定 planDigest/workItemId/attempt/mode/baseHead/dirtyDigest/activeRoot/isolationRoot/allowedRealpaths/forbiddenSharedSurfaces/issuedAt/expiresAt/cancelFence/leaseDigest。isolated-worktree-patch 的 plan 只冻结相对 allowed paths；宿主创建独立 worktree 后，根 Agent 必须用其真实 isolationRoot 重新计算 lease 的绝对 allowed realpaths。缺 isolation root、与 root checkout 相同或路径逃逸时不签发 lease并自动串行。允许的模式只有：

mode允许范围
read-only只读分析，不得产生源码或正式产物写入
isolated-validation只写该 operationId 独占的 .tmp，返回验证证据并精确清理
isolated-worktree-patch仅宿主明确支持 separate worktree 时，在隔离 worktree 的 allowed realpaths 内形成 patch；不得直接写 root checkout

lease 过期、attempt/plan/source/dirty 不符、cancel fence 改变或 root 已进入串行回退后，结果一律视为 late/quarantined；禁止恢复旧 lease。

ChildAgentEvidenceV1 与 RootAgentIntegrationReceiptV1

child 返回的只是候选证据，至少绑定 host child identity、plan/lease/attempt、base/dirty、实际 changed realpaths、patch digest（如有）、validation receipts、完成时间和 owned resource cleanup。根 Agent 必须验证：

  1. work item id 必须唯一；调用方与 child 提供的 realpath 必须原生为绝对路径，且全部落在 lease 允许根内，没有触碰禁止共享面；
  2. read-only/isolated-validation 没有源码写入；worktree patch 有摘要和独立验证；
  3. lease 未过期、cancel fence 未变化、root 尚未接管串行；
  4. child 启动的 temp/worktree/service 已清理，无 owned residue；
  5. 结果按冻结 merge order 串行复证、应用和 root retest。

任一项不成立时输出 ChildAgentEvidenceValidationV1.classification=quarantined，把该 work item 放入 RootAgentIntegrationReceiptV1.serialTakeoverWorkItemIds。childCompletionIsTaskCompletion=false 与 RootAgentIntegrationReceiptV1.taskCompletion=false 是强制不变量；最终 CP、memory、report、ledger、audit、package、manifest、portfolio、Profile 和 ECR 仍由根 Agent 写入。

Show full SKILL.md (263 more words)Show less
取消、超时与清理

根 Agent 仅对本 plan 的 child 使用宿主 interrupt，并形成 HostSubagentCancelFenceV1。bounded wait 超时或派发失败后先改变 cancel fence，再将未接受 work items 交给根 Agent 串行；随后到达的旧结果不得应用。只清理本 plan 创建的 child、operation temp、worktree 和服务，禁止终止用户既有进程或删除其他任务产物。

执行步骤

  1. 绑定唯一 active-root 和源码根；确认不是跨项目混读。
  2. 有界读取 active work：任务目录、CP 状态、近期 memory/report 摘要、预期写入面。
  3. 构建 ActiveWorkInventoryV1，记录 sourceRefs 和 freshness。
  4. 执行 SharedSurfaceLockMapV1 和 RequirementIndependenceGate。
  5. 对 independent 输出 ParallelLaunchCardV1；对 weakly-coupled-lock 输出锁、single writer 和检查点；对 serial-required 输出 blocker 与推荐顺序。
  6. 读取当前宿主 collaboration tool inventory，形成并校验 HostNativeCollaborationCapabilityV1；不能直接观察则自动串行。
  7. 生成 HostSubagentDispatchPlanV1；未达到 capability/isolation/time/cost gate 时按其中 serialFallback 执行同一 work graph。
  8. 对 parallel-eligible 项生成 AgentWorkLeaseV1，由根 Agent 调用宿主 spawn/wait/interrupt；Hook、MCP、脚本和 child 不得代替根 Agent 调用这些模型工具。
  9. 汇合时验证 ChildAgentEvidenceV1，形成 RootAgentIntegrationReceiptV1，再由根 Agent串行应用、重测、写 report/memory 并执行 ECR。

探针

Probe场景期望
PRB-01两个需求只写各自 requirement 子目录independent + LaunchCard valid
PRB-02需求目录独立但共享 portfolio/manifestweakly-coupled-lock
PRB-03两个任务修改同一 source fileserial-required
PRB-04LaunchCard 缺 required fieldslaunch-card-invalid
PRB-05缺 merge protocolintegration-protocol-missing
PRB-06出现 allowParallelMutations 或默认并行源码写入开关policy-violation
PRB-07capability absent/stale/docs-only 或缺 operationplan=serial-fallback，work graph 保留
PRB-08低于 120s/60s/25% 收益门plan=serial-fallback
PRB-09source mutation 无 separate worktree串行，不退化为共享 checkout
PRB-10lease expiry、timeout、cancel 或 late resultquarantined + root serial takeover
PRB-11changed realpath、dirty、patch/test identity 漂移quarantined，不应用
PRB-12child 全部完成仍需 root merge/retest/ECR，不得直接完成任务

生产入口：npm run test:requirement-parallel-orchestration。

与其他 Skill 的关系

  • dev-default / fix-default：实现前出现多任务、并行、子 Agent 或 worktree 信号时触发本 Skill。
  • execution-contract：把 LaunchCard、dispatch plan、work lease、allowed paths、blocked scope、merge protocol 和 single-writer 约束纳入合同。
  • test-router：以 requirementParallelOrchestration 领域绑定选择 static + unit-integration；控制面实现叠加 profile-deploy。
  • report / memory：记录判定摘要和 LaunchCard 锚点；最终 report/memory 仍由主会话单写者写入。
  • source-consumer-sync：消费者、validation manifest、portfolio、Profile、README/website 和部署副本同步由 Concept Sync Map 约束。

禁止

  • 禁止把只读准备并行扩展为同 active-root 并行 source mutation。
  • 禁止新增 allowParallelMutations、mode=parallel 或绕过 C07 单写者的配置。
  • 禁止没有 allowedPaths、forbiddenSharedSurfaces、mergeProtocol 或 validationRoute 就启动子会话。
  • 禁止子会话直接写共享 CP、memory、report、ledger、audit session、portfolio、validation manifest 或部署副本。
  • 禁止把子会话完成等同于需求完成；必须串行汇合、验证和 ECR。
  • 禁止把官方文档、Skill/AGENTS 文本、工具名猜测或其他宿主证据写成 current-host direct collaboration PASS。
  • 禁止 capability/dispatch/timeout 失败后请求用户重复确认；必须自动执行 plan 中相同 work graph 的串行回退。
  • 禁止 child 递归 spawn；首版 depth 固定为 1，fanout 不得超过 4。

© devcodex-labs, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in content/skills/requirement-parallel-orchestration of devcodex-labs/devcodex.

  • SKILL.md
  • intent.json

Open the folder on GitHubat commit 1dd4525

Compare with similar skills

Requirement Parallel Orchestration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Requirement Parallel Orchestration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Requirement Parallel Orchestration this skilldevcodex-labs/devcodex439—~2.2kAutomated safety check: PassAGPL-3.0
Requirementsrizsotto/Bear6.5k—~2kAutomated safety check: PassGPL-3.0
Parallel Execution Optimizeraffaan-m/ECC274k1 repos~712Automated safety check: PassMIT
Parallel AutomationComposioHQ/awesome-claude-skills77k3 repos~734Automated safety check: PassNone
Parallel WebK-Dense-AI/scientific-agent-skills48k1 repos~2.2kAutomated safety check: NotesMIT
Parallel Debuggingwshobson/agents40k1 repos~1.2kAutomated safety check: PassMIT

Similar skills

  • Requirements

    rizsotto/Bear

    Write, modify, or review a requirement file under docs/requirements -- pick the single owning file, keep the text contract-only, name IDs so they need no explanation, and verify cross-references and…

    6.5k GitHub stars~2k tokensUpdated today
    Testing & QAAuto-check passed

  • Parallel Execution Optimizer

    affaan-m/ECC

    Speed up a task by turning it into a dependency graph of parallel lanes with a lane matrix, batched reads and checks, write surfaces isolated by file, worktree, branch, or service, and a final…

    274k GitHub starsUsed in 1 repo~712 tokens
    DevelopmentAuto-check passed

  • Parallel Automation

    ComposioHQ/awesome-claude-skills

    Automate Parallel tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.

    77k GitHub starsUsed in 3 repos~734 tokens
    Productivity & AutomationAuto-check passed

  • Parallel Web

    K-Dense-AI/scientific-agent-skills

    Uses Parallel CLI for web search, URL extraction, deep research, structured data enrichment, entity discovery, and recurring web monitoring.

    48k GitHub starsUsed in 1 repo~2.2k tokens
    Research & ScienceAuto-check: notes

  • Parallel Debugging

    wshobson/agents

    Debug complex issues using competing hypotheses with parallel investigation, evidence collection, and root cause arbitration.

    40k GitHub starsUsed in 1 repo~1.2k tokens
    DevelopmentAuto-check passed

  • Aria Required Attr

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Include required ARIA attributes for roles.

    74k GitHub stars~459 tokensUpdated yesterday
    Frontend & DesignAuto-check passed

More from devcodex-labs/devcodex

All 70 skills in this repo

  • Accessibility I18n

    devcodex-labs/devcodex

    无障碍与国际化专家 Owner — 当任务涉及可访问性、键盘操作、焦点、屏幕阅读器、ARIA、语言地区、本地化、RTL、翻译资源、用户可见文案或多语言文档时使用；要求把包容性体验和本地化验证绑定到真实用户路径。

    439 GitHub stars~718 tokensUpdated 20 days ago
    Auto-check passed

  • AI Agent System Architecture

    devcodex-labs/devcodex

    AI Agent 系统架构专家 Owner — 当任务涉及 Agent 路由、工具调用、上下文管理、记忆、状态机、权限、人机协作、可观测性、回放验证或模型辅助治理时使用；要求把 Agent 行为设计成可解释、可恢复、可审计。

    439 GitHub stars~2.4k tokensUpdated 20 days ago
    Auto-check passed

  • API Contract Architecture

    devcodex-labs/devcodex

    API 契约架构专家 Owner — 当任务涉及 public API、HTTP/SDK/CLI 契约、版本兼容、错误模型、分页过滤、幂等、Schema、类型、迁移或消费者影响时使用；要求先冻结消费者契约，再设计实现与验证。

    439 GitHub stars~865 tokensUpdated 20 days ago
    Auto-check passed

  • Architecture Design

    devcodex-labs/devcodex

    架构设计文档编排 Owner — 当用户要求架构设计、系统设计、技术架构或可指导开发、Review 与任务拆分的完整方案时使用；要求从业务流程反推节点、状态、数据、一致性、异常补偿、ADR 与实施任务。

    439 GitHub stars~1.1k tokensUpdated 20 days ago
    Auto-check passed

  • Audit Common

    devcodex-labs/devcodex

    审查公共维度 G0~G5 + Profile Freshness Check — 所有 audit 子类型必先执行的基础维度层

    439 GitHub stars~4.1k tokensUpdated 20 days ago
    Auto-check passed

  • Audit Session

    devcodex-labs/devcodex

    审计工作流的跨会话状态机 — 在 <audit-root/.audit-state/<session-id.json 持久化轮次/发现项/收敛状态，支持 Token 中断后精准恢复

    439 GitHub stars~1.8k tokensUpdated 20 days ago
    Auto-check passed

Questions about Requirement Parallel Orchestration

What does Requirement Parallel Orchestration do?

多需求与宿主原生子 Agent 编排 Skill — 先判断工作项独立性，再以新鲜宿主能力、租约、隔离证据和根 Agent 单写者完成受控派发或自动串行回退。. Requirement Parallel Orchestration is an agent skill from devcodex-labs/devcodex.

How do I install Requirement Parallel Orchestration in Claude Code?

Run `npx skills add devcodex-labs/devcodex --skill requirement-parallel-orchestration -a claude-code`. Or copy the skill folder (content/skills/requirement-parallel-orchestration in devcodex-labs/devcodex) into .claude/skills/requirement-parallel-orchestration in your project. Claude Code loads it when a task matches its description.

How do I install Requirement Parallel Orchestration in Codex?

Run `npx skills add devcodex-labs/devcodex --skill requirement-parallel-orchestration -a codex`. Or copy the skill folder (content/skills/requirement-parallel-orchestration in devcodex-labs/devcodex) into .agents/skills/requirement-parallel-orchestration in your project. Codex loads it when a task matches its description.

Can I use Requirement Parallel Orchestration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add devcodex-labs/devcodex --skill requirement-parallel-orchestration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/requirement-parallel-orchestration, .gemini/skills/requirement-parallel-orchestration, .github/skills/requirement-parallel-orchestration and .opencode/skills/requirement-parallel-orchestration in your project.

What does Requirement Parallel Orchestration need to run?

Going by SKILL.md and its folder, Requirement Parallel Orchestration needs the command-line tools its instructions call (git and npm).

Does Requirement Parallel Orchestration access the network?

SKILL.md contains no URLs. Its commands use git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Requirement Parallel Orchestration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Requirement Parallel Orchestration use?

Requirement Parallel Orchestration is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Requirement Parallel Orchestration use?

About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Requirement Parallel Orchestration?

Skills that share tags, products or a category with Requirement Parallel Orchestration: Requirements (rizsotto/Bear, 6.5k stars), Parallel Execution Optimizer (affaan-m/ECC, 274k stars), Parallel Automation (ComposioHQ/awesome-claude-skills, 77k stars) and Parallel Web (K-Dense-AI/scientific-agent-skills, 48k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Requirement Parallel Orchestration?

devcodex-labs (a GitHub organization) maintains it in devcodex-labs/devcodex, which has 439 GitHub stars. The repository holds 70 skills in this directory. The repository was last updated on September 17, 2026.

Source: devcodex-labs/devcodex on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.