ha-multi-agent-coding

Orchestrates parallel sub-agent coding work with bounded scope, isolation, and parent-side synthesis.

1.6k|149|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/shiwenwen/hope-agent --skill ha-multi-agent-coding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ha-multi-agent-coding
Source: https://github.com/shiwenwen/hope-agent/tree/main/skills/ha-multi-agent-coding
Command: npx skills add https://github.com/shiwenwen/hope-agent --skill ha-multi-agent-coding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deciding when and how to split coding work across multiple agents is error-prone: uncontrolled fan-out wastes tokens, causes file conflicts, and leaves results unsynthesized. This Skill gives the main agent a disciplined strategy for delegating only genuinely independent work and merging results correctly.

Core Features & Use Cases

  • Fan-Out Decision Rules: Clear criteria for when parallel sub-agents pay off versus when a single agent should keep the work, avoiding delegation by default.
  • Child Contracts & Isolation: Each child gets a bounded objective, allowed/forbidden actions, file ownership or read-only isolation, and a required structured output schema.
  • Progressive Control & Synthesis: Consume partial results with waitAny or checkpoints, steer or cancel children, then resolve conflicts from evidence and run parent-level verification.
  • Use Case: Ask the agent to investigate six independent modules in parallel; it fans out read-only research children, consumes results as they arrive, and synthesizes one coherent answer instead of waiting on the slowest reviewer.

Quick Start

Ask the agent to investigate these independent modules in parallel using bounded sub-agents and synthesize the findings into one answer.

Frequently Asked Questions about ha-multi-agent-coding

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

FAQPage Schema
How do I run multiple coding agents in parallel on one task?

Fan out only independent work: give each child a bounded objective, file ownership or read-only isolation, and a required structured output schema. The main agent then consumes results progressively and synthesizes the final answer itself.

When should I use a single agent instead of multi-agent orchestration?

Keep one agent when the task is small, steps depend on prior results, agents would edit the same files, or coordination and token cost exceeds the parallel gain. Delegation should not be the default for complex-looking work.

How do I prevent parallel agents from conflicting on the same files?

Use shared read-only mode for research and verification, separate worktrees for independent writes, or mutually exclusive file ownership when writes cannot be isolated. Permission modes and protected paths remain enforced by the runtime.

Can I consume partial sub-agent results without waiting for all of them?

Yes. The main agent can use waitAny or checkpoints to consume the first useful results, query status without consuming output, steer or cancel remaining children, and only wait for all children when a true barrier is required.

What are the limits of multi-agent coding orchestration?

Fan-out count, depth, turns, tokens, and time must be explicitly bounded, and recursive workflow creation is forbidden. Children never own final user communication, and completion of all agents is not a result until the parent synthesizes and verifies it.