team-decisionlisted

# Team Decision ## Overview The team decision skill guides the choice between parallel Agent Teams execution and sequential subagent orchestration. This skill analyzes task characteristics to determine whether parallel execution is safe, beneficial, and cost-effective. **Owner Agent**: Senku (Planner Agent) **Consumers**: Orchestrator (primary decision maker) ### Key Principles 1. **Safety First**: Only parallelize when tasks are truly independent 2. **Cost-Benefit Analysis**: Parallel overhead must be justified by time savings 3. **File Ownership**: Exclusive file ownership prevents conflicts 4. **Fail to Sequential**: When in doubt, use sequential orchestration ### When to Use This Skill Apply team decision analysis when: - A task naturally decomposes into multiple subtasks - Subtasks could potentially run in parallel - Time-to-completion is a priority - Determining whether to spawn a team or orchestrate sequentially --- ## Decision Criteria Table | Criterion | Use Teams (Parallel) | Use Sequential | |-----------|---------------------|----------------| | **Task Independence** | No shared state or files | Tasks have dependencies | | **File Ownership** | Exclusive file sets | Overlapping file sets | | **Parallelism Safety** | Safe or Moderate | Risky | | **Number of Tasks** | 2-4 independent tasks | 1 task or 5+ tasks | | **Time Sensitivity** | High (user waiting) | Low (can afford serial) | | **Coordination Cost** | Low (simple merge) | High (complex merge) | | **