subagent-dependency

Coordinate subagent dependencies for parallel execution and safe result merging.

1|Updated Apr 9, 2026

Search Tags:#workflow #dependencies #agents #orchestration #merge #subagent #parallel-execution

Ready to run

npx skills add https://github.com/hbvg234/jnmt.vn --skill subagent-dependency

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: subagent-dependency
Source: https://github.com/hbvg234/jnmt.vn/tree/main/.claude/skills/subagent-dependency
Command: npx skills add https://github.com/hbvg234/jnmt.vn --skill subagent-dependency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill teaches how to structure and manage dependencies between multiple subagents, enabling parallel execution while ensuring safe, merged results.

Core Features & Use Cases

Dependency graph modeling: represents agents as nodes and dependencies as edges, enabling both parallel and sequential execution.
Wave-based dispatch: schedules agents in parallel waves and then sequentially processes merged outputs for final analysis.
Deterministic merging & safety: provides a standardized merged report format and enforces read-only mechanics to prevent unintended modifications.
Use cases: orchestrating multi-agent workflows on large codebases, optimizing runtime by running independent agents concurrently.

Quick Start

Provide your task description and let the skill generate a wave-based dispatch plan for subagents.

Frequently Asked Questions about subagent-dependency

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I coordinate dependencies between subagents for parallel execution?▼

Subagent dependency coordination uses wave-based dispatch to schedule independent agents in parallel waves, then sequentially processes merged outputs to produce a unified action plan without unintended codebase modifications.

What is the best way to orchestrate multi-agent workflows on large codebases?▼

Orchestrating multi-agent workflows on large codebases requires wave-based dispatch to run independent agents concurrently, optimizing runtime while enforcing read-only safety constraints during deterministic result merging.

How does wave-based dispatch work for parallel agent execution?▼

Wave-based dispatch schedules independent subagents concurrently in parallel waves, waits for each wave to complete, then sequentially processes merged outputs to generate a final unified report.

Can I use subagent orchestration to run sequential and parallel phases in the same workflow?▼

Yes, subagent orchestration supports both sequential and parallel phases by mapping dependencies to control execution order, allowing independent agents to run concurrently while dependent agents wait for upstream results.

How do I safely merge results from multiple parallel agents?▼

Safely merge results from parallel agents by applying a standardized merged report format and enforcing read-only mechanics during execution to prevent unintended modifications across the codebase.

What are the limitations of using dependency graphs for subagent orchestration?▼

A limitation of dependency graph subagent orchestration is that read-only safety constraints prevent agents from making live modifications, meaning the workflow produces a merged action plan rather than directly applying codebase changes.