agent-organizer

Orchestrates multi-agent workflows with delegation patterns, state management, and execution loops.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/JenilRevaliya/ARGUS --skill agent-organizer-jenilrevaliya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-organizer
Source: https://github.com/JenilRevaliya/ARGUS/tree/main/.agent/skills/agent-organizer
Command: npx skills add https://github.com/JenilRevaliya/ARGUS --skill agent-organizer-jenilrevaliya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multiple AI sub-agents without a clear framework leads to context bloat, lost state between invocations, and uncontrolled execution. This Skill provides a structured orchestration framework for delegating tasks, managing memory across agent boundaries, and enforcing human oversight gates. ## Core Features & Use Cases - Delegation Sub-Agent Pattern: Define structured JSON payload contracts for worker agents with isolated context, clear boundaries, and machine-parseable handoffs. - Supervisor Execution Loops: Fan-out/fan-in dispatch of specialized workers with definitive state signals (COMPLETE, BLOCKED, ERROR) for controlled coordination. - Session State Management: Persist task state in task.md checklists and distill long-term knowledge into learnings.json injected on subsequent startups. - Human-in-the-Loop Gates: Mandatory approval gates before execution and recovery gates after repeated failures. - Use Case: When a user asks to "add OAuth and secure it", the Supervisor dispatches an authentication worker to build the implementation and a security-auditor worker to review it against OWASP, then synthesizes results before committing. ## Quick Start Ask the agent to break down a complex feature request into specialized sub-agent tasks with isolated context and tracked progress in a task file.

Frequently Asked Questions about agent-organizer

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

FAQPage Schema
How do I coordinate multiple AI sub-agents on one task?▼

Use the Supervisor pattern: a parent agent analyzes the request, dispatches specialized worker agents with isolated context payloads, and synthesizes their structured outputs. Workers return state signals like COMPLETE, BLOCKED, or ERROR so the supervisor knows how to proceed.

How to pass context to sub-agents without exceeding token limits?▼

Never pass the full conversation history to a worker. Extract only the exact files and goal context required into a trimmed context_summary, since each agent invocation is stateless and context window budgeting prevents token overflow.

Do sub-agents share memory with the parent agent?▼

No, each agent invocation is stateless unless context is explicitly passed. Persist shared state externally using a task.md file for task checklists and a learnings.json file for distilled long-term knowledge injected on subsequent startups.

When should agents run in parallel versus sequentially?▼

Use fan-out/fan-in parallel dispatch when sub-agent tasks are independent, such as building a feature and auditing it separately. Run sequentially only when one worker's output is required input for the next worker.

What happens when a sub-agent task keeps failing?▼

The framework defines a recovery gate: after three consecutive failures, the orchestrator halts execution and asks the human how to proceed. Workers signal failures with an ERROR state so the supervisor can intervene rather than loop indefinitely.