agent-orchestration

Name: agent-orchestration
Availability: InStock
Author: Uygnoey

Orchestrate seven agents through phase-based FSM for Layer2 development workflows.

Updated Mar 4, 2026

Search Tags:#development #documentation #agents #orchestration #fsm #git-branch #layer2

Ready to run

npx skills add https://github.com/uygnoey/autonomous-dev-agent-ts --skill agent-orchestration-uygnoey

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-orchestration
Source: https://github.com/uygnoey/autonomous-dev-agent-ts/tree/main/.claude/skills/agent-orchestration
Command: npx skills add https://github.com/uygnoey/autonomous-dev-agent-ts --skill agent-orchestration-uygnoey

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

이 스킬은 Layer2 구현에서 7개 에이전트의 역할 분담과 FSM 기반의 Phase 전환을 통해 개발 파이프라인의 복잡한 워크플로를 관리합니다.

Core Features & Use Cases

7개 고정 에이전트 역할: architect, qa, coder, tester, qc, reviewer, documenter
Phase 전환 FSM: DESIGN -> CODE -> TEST -> VERIFY
Coder×N Git 브랜치 관리: main 및 feature 브랜치 분리
documenter 이벤트 트리거: Phase 완료 시 문서 생성 및 종료
references 활용: agent-roles-detail.md로 상세 역할 참조
Layer2 구현 시 참조: 필요 시 layer2 설계가이드에 연결
복합 시나리오 대응: 다수의 병렬 작업과 이벤트 기반 문서화 지원

Quick Start

Initialize the Layer2 orchestration by loading the seven agent roles, configuring the FSM, and starting the documenter-triggered workflow.

Frequently Asked Questions about agent-orchestration

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

FAQPage Schema

How do I orchestrate multiple agents for autonomous software development workflows?▼

Multi-agent orchestration for autonomous software development is managed by assigning seven fixed agent roles—architect, qa, coder, tester, qc, reviewer, and documenter—coordinated through a phase-based FSM. This structure handles role separation, multi-branch code collaboration, and event-driven documentation across the pipeline.

What is a phase-based FSM for managing multi-agent code collaboration?▼

A phase-based FSM for multi-agent collaboration is a deterministic state machine that transitions through DESIGN, CODE, TEST, and VERIFY phases. It ensures structured progression by triggering the documenter agent to generate documentation and finalize outputs upon phase completion.

How do I separate agent roles for parallel coding tasks across Git branches?▼

Separate agent roles for parallel coding tasks by assigning multiple Coder agents to manage distinct feature Git branches alongside the main branch. The architecture uses seven specialized agents, ensuring isolated development and deterministic phase transitions within the FSM.

Does this agent orchestration approach support event-driven documentation triggers?▼

Yes, event-driven documentation triggers are supported natively by the documenter agent role. When the FSM completes a phase transition, the documenter agent is automatically triggered to generate required documentation before the workflow proceeds or terminates.

Can I use this orchestration framework for Layer2 development implementations?▼

Yes, the orchestration framework is specifically designed for Layer2 development implementations. It connects to Layer2 design guides when needed and applies a deterministic FSM to manage the complex, multi-branch workflows inherent in Layer2 architecture.