+ Practical state flow and task-message example
- Replaces the request with an unsupported blog scenario
--- name: agent-organization-expert description: Multi-agent orchestration skill for team assembly, task decomposition, workflow optimization, and coo
| Category | Using AI › Writing prompts |
|---|---|
| Tags | AnalyzingIdeationChecklist |
---
name: agent-organization-expert
description: Multi-agent orchestration skill for team assembly, task decomposition, workflow optimization, and coordination strategies to achieve optimal team performance and resource utilization.
---
# Agent Organization
Assemble and coordinate multi-agent teams through systematic task analysis, capability mapping, and workflow design.
## Configuration
- **Agent Count**: ${agent_count:3}
- **Task Type**: ${task_type:general}
- **Orchestration Pattern**: ${orchestration_pattern:parallel}
- **Max Concurrency**: ${max_concurrency:5}
- **Timeout (seconds)**: ${timeout_seconds:300}
- **Retry Count**: ${retry_count:3}
## Core Process
1. **Analyze Requirements**: Understand task scope, constraints, and success criteria
2. **Map Capabilities**: Match available agents to required skills
3. **Design Workflow**: Create execution plan with dependencies and checkpoints
4. **Orchestrate Execution**: Coordinate ${agent_count:3} agents and monitor progress
5. **Optimize Continuously**: Adapt based on performance feedback
## Task Decomposition
### Requirement Analysis
- Break complex tasks into discrete subtasks
- Identify input/output requirements for each subtask
- Estimate complexity and resource needs per component
- Define clear success criteria for each unit
### Dependency Mapping
- Document task execution order constraints
- Identify data dependencies between subtasks
- Map resource sharing requirements
- Detect potential bottlenecks and conflicts
### Timeline Planning
- Sequence tasks respecting dependencies
- Identify parallelization opportunities (up to ${max_concurrency:5} concurrent)
- Allocate buffer time for high-risk components
- Define checkpoints for progress validation
## Agent Selection
### Capability Matching
Select agents based on:
- Required skills versus agent specializations
- Historical performance on similar tasks
- Current availability and workload capacity
- Cost efficiency for the task complexity
### Selection Criteria Priority
1. **Capability fit**: Agent must possess required skills
2. **Track record**: Prefer agents with proven success
3. **Availability**: Sufficient capacity for timely completion
4. **Cost**: Optimize resource utilization within constraints
### Backup Planning
- Identify alternate agents for critical roles
- Define failover triggers and handoff procedures
- Maintain redundancy for single-point-of-failure tasks
## Team Assembly
### Composition Principles
- Ensure complete skill coverage for all subtasks
- Balance workload across ${agent_count:3} team members
- Minimize communication overhead
- Include redundancy for critical functions
### Role Assignment
- Match agents to subtasks based on strength
- Define clear ownership and accountability
- Establish communication channels between dependent roles
- Document escalation paths for blockers
### Team Sizing
- Smaller teams for tightly coupled tasks
- Larger teams for parallelizable workloads
- Consider coordination overhead in sizing decisions
- Scale dynamically based on progress
## Orchestration Patterns
### Sequential Execution
Use when tasks have strict ordering requirements:
- Task B requires output from Task A
- State must be consistent between steps
- Error handling requires ordered rollback
### Parallel Processing
Use when tasks are independent (${orchestration_pattern:parallel}):
- No data dependencies between tasks
- Separate resource requirements
- Results can be aggregated after completion
- Maximum ${max_concurrency:5} concurrent operations
### Pipeline Pattern
Use for streaming or continuous processing:
- Each stage processes and forwards results
- Enables concurrent execution of different stages
- Reduces overall latency for multi-step workflows
### Hierarchical Delegation
Use for complex tasks requiring sub-orchestration:
- Lead agent coordinates sub-teams
- Each sub-team handles a domain
- Results aggregate upward through hierarchy
### Map-Reduce
Use for large-scale data processing:
- Map phase distributes work across agents
- Each agent processes a partition
- Reduce phase combines results
## Workflow Design
### Process Structure
1. **Entry point**: Validate inputs and initialize state
2. **Execution phases**: Ordered task groupings
3. **Checkpoints**: State persistence and validation points
4. **Exit point**: Result aggregation and cleanup
### Control Flow
- Define branching conditions for alternative paths
- Specify retry policies for transient failures (max ${retry_count:3} retries)
- Establish timeout thresholds per phase (${timeout_seconds:300}s default)
- Plan graceful degradation for partial failures
### Data Flow
- Document data transformations between stages
- Specify data formats and validation rules
- Plan for data persistence at checkpoints
- Handle data cleanup after completion
## Coordination Strategies
### Communication Patterns
- **Direct**: Agent-to-agent for tight coupling
- **Broadcast**: One-to-many for status updates
- **Queue-based**: Asynchronous for decoupled tasks
- **Event-driven**: Reactive to state changes
### Synchronization
- Define sync points for dependent tasks
- Implement waiting mechanisms with timeouts (${timeout_seconds:300}s)
- Handle out-of-order completion gracefully
- Maintain consistent state across agents
### Conflict Resolution
- Establish priority rules for resource contention
- Define arbitration mechanisms for conflicts
- Document rollback procedures for deadlocks
- Prevent conflicts through careful scheduling
## Performance Optimization
### Load Balancing
- Distribute work based on agent capacity
- Monitor utilization and rebalance dynamically
- Avoid overloading high-performing agents
- Consider agent locality for data-intensive tasks
### Bottleneck Management
- Identify slow stages through monitoring
- Add capacity to constrained resources
- Restructure workflows to reduce dependencies
- Cache intermediate results where beneficial
### Resource Efficiency
- Pool shared resources across agents
- Release resources promptly after use
- Batch similar operations to reduce overhead
- Monitor and alert on resource waste
## Monitoring and Adaptation
### Progress Tracking
- Monitor completion status per task
- Track time spent versus estimates
- Identify tasks at risk of delay
- Report aggregated progress to stakeholders
### Performance Metrics
- Task completion rate and latency
- Agent utilization and throughput
- Error rates and recovery times
- Resource consumption and cost
### Dynamic Adjustment
- Reallocate agents based on progress
- Adjust priorities based on blockers
- Scale team size based on workload
- Modify workflow based on learning
## Error Handling
### Failure Detection
- Monitor for task failures and timeouts (${timeout_seconds:300}s threshold)
- Detect agent unavailability promptly
- Identify cascade failure patterns
- Alert on anomalous behavior
### Recovery Procedures
- Retry transient failures with backoff (up to ${retry_count:3} attempts)
- Failover to backup agents when needed
- Rollback to last checkpoint on critical failure
- Escalate unrecoverable issues
### Prevention
- Validate inputs before execution
- Test agent availability before assignment
- Design for graceful degradation
- Build redundancy into critical paths
## Quality Assurance
### Validation Gates
- Verify outputs at each checkpoint
- Cross-check results from parallel tasks
- Validate final aggregated results
- Confirm success criteria are met
### Performance Standards
- Agent selection accuracy target: >${agent_selection_accuracy:95}%
- Task completion rate target: >${task_completion_rate:99}%
- Response time target: <${response_time_threshold:5} seconds
- Resource utilization: optimal range ${utilization_min:60}-${utilization_max:80}%
## Best Practices
### Planning
- Invest time in thorough task analysis
- Document assumptions and constraints
- Plan for failure scenarios upfront
- Define clear success metrics
### Execution
- Start with minimal viable team (${agent_count:3} agents)
- Scale based on observed needs
- Maintain clear communication channels
- Track progress against milestones
### Learning
- Capture performance data for analysis
- Identify patterns in successes and failures
- Refine selection and coordination strategies
- Share learnings across future orchestrationsThis prompt provides guidance for assembling and coordinating multiple agents. It covers requirement analysis, dependency mapping, agent selection, and backup planning.
All three replace the prompt defaults with an unsupported blog workflow. Claude is the most detailed, ChatGPT the most practical, while Gemini most explicitly misstates the supplied settings.
+ Practical state flow and task-message example
- Replaces the request with an unsupported blog scenario
+ Clear roles, data contracts, and quality gates
- Invents a blog task and unsupported settings
+ Systematic workflow and failure handling
- Claims settings that contradict the prompt
| Criterion | ChatGPT | Claude | Gemini | Leader |
|---|---|---|---|---|
| Instruction following | 2 | 2 | 2 | Tie |
| Accuracy | 4 | 3 | 2 | ChatGPT +33% |
| Specificity | 2 | 2 | 2 | Tie |
| Structure | 8 | 9 | 8 | Claude +13% |
| Right length | 6 | 6 | 5 | Tie |
Scored 1–10 by gpt-5.6-sol with model names hidden (2026-09-24). This is an AI review, not a measurement.
We gave three models the same input and copied their answers unedited. Each ran in its CLI (an agent harness), and answers in the ChatGPT or Claude apps or on the web may differ. Outputs are in Korean.
[Pasted material] agent_count: 5 task_type: 콘텐츠 파이프라인 (리서치→초안→교정→발행) orchestration_pattern: hierarchical max_concurrency: 4 timeout_seconds: 600 retry_count: 2 우리 팀은 매주 블로그 글 3편을 리서치-초안 작성-SEO 교정-발행 단계로 처리하는데, 각 단계를 에이전트에 맡기고 리드 에이전트가 조율하는 구조로 설계해줘.
주 3편을 안정적으로 처리하려면 5개 에이전트의 계층형 파이프라인이 적합합니다.
┌─ 연구 에이전트 ─┐
리드 에이전트 ──────┼─ 초안 에이전트 ─┼─ SEO 교정 에이전트 ── 발행 에이전트
└─ ┘
각 에이전트는 담당 단계를 소유하고, 리드 에이전트는 세 글의 상태·의존성·품질 게이트를 관리합니다.
| 역할 | 주요 책임 | 산출물 |
|---|---|---|
| 리드 에이전트 | 일정 관리, 작업 배정, 품질 게이트, 재작업 조율, 최종 보고 | 주간 보드, 상태 보고서, 승인 기록 |
| 리서치 에이전트 | 키워드·경쟁 글·근거 자료 조사, 검색 의도 파악 | 리서치 브리프 |
| 초안 에이전트 | 브리프 기반 글 작성, 구조·사례·CTA 구성 | 초안 원고 |
| SEO 교정 에이전트 | 검색 의도, 제목·메타·헤딩·내부 링크·가독성 검수 | 교정 원고, SEO 체크리스트 |
| 발행 에이전트 | CMS 입력, 이미지·카테고리·태그 설정, 예약 발행, 최종 확인 | 게시글 URL, 발행 로그 |
각 글에 고유 ID를 부여합니다.
WEEK-39-A
WEEK-39-B
WEEK-39-C
각 글은 다음 상태를 순서대로 거칩니다.
BACKLOG
→ RESEARCH
→ DRAFT
→ SEO_REVIEW
→ HUMAN_APPROVAL
→ SCHEDULED
→ PUBLISHED
상태는 리드 에이전트만 변경하도록 하면 충돌을 줄일 수 있습니다.
파이프라인은 글 3편을 한꺼번에 같은 단계에 넣기보다 하루 간격으로 stagger 처리합니다.
| 요일 | 주요 작업 |
|---|---|
| 월요일 | 세 글의 주제·키워드 확정, A 리서치 |
| 화요일 | A 초안, B 리서치 |
| 수요일 | A SEO 교정, B 초안, C 리서치 |
| 목요일 | A 승인·예약 발행, B SEO 교정, C 초안 |
| 금요일 | B 승인·발행, C SEO 교정·승인·예약 발행 |
실제 게시일은 콘텐츠 성격에 따라 예약할 수 있으며, 발행 에이전트는 CMS 예약까지 처리합니다.
리서치 브리프
↓ Gate 1: 키워드·근거·검색 의도 확인
초안
↓ Gate 2: 분량·구조·주장·CTA 확인
SEO 교정
↓ Gate 3: 제목·메타·내부 링크·가독성 확인
사람 승인
↓ Gate 4: 사실 오류·브랜드 톤·법적 위험 확인
예약 발행
↓ Gate 5: 실제 URL·서식·링크·이미지 확인
각 게이트에서 실패하면 이전 단계로 되돌리지 않고, 수정 요청을 명시한 상태로 재작업합니다.
NEEDS_RESEARCH_REVISION
NEEDS_DRAFT_REVISION
NEEDS_SEO_REVISION
NEEDS_HUMAN_REVIEW
리드 에이전트는 매일 다음 순서로 조율합니다.
작업 메시지는 다음 형식으로 통일하는 것이 좋습니다.
[작업 ID] WEEK-39-A
[목표] 검색 의도에 맞는 1,800자 초안 작성
[입력] research/WEEK-39-A.md
[필수 조건] 핵심 키워드 1개, 보조 키워드 3개, CTA 1개
[마감] 2026-09-29 15:00
[완료 조건] 초안 파일과 자체 검수 체크리스트 제출
각 글에는 다음 메타데이터를 함께 저장합니다.
article_id: WEEK-39-A
owner: draft-agent
status: SEO_REVIEW
attempt: 1
deadline: 2026-09-30T12:00:00+09:00
source_file: research/WEEK-39-A.md
last_updated: 2026-09-24T10:30:00+09:00
blocker: null
[확인 필요]로 표시주간 리드 보고서에는 다음 지표를 포함합니다.
핵심 목표는 주 3편 발행, 예약 발행 실패 0건, 사실 오류 0건, SEO 교정 재작업률 감소로 설정하면 됩니다.
이 구조에서는 리드 에이전트가 전체 조율을 담당하고, 나머지 4개 에이전트는 각 단계의 전문성과 책임을 명확히 유지할 수 있습니다.
| 4 Optimized Versions of A Prompt (in Arabic) | |
| $500/Hour AI Consultant Prompt | |
| Adaptive Thinking Framework | |
| AI Kickstart prompt | |
| AI Process Feasibility Interview |