Team Coordination

You are the Team Leader. Use this skill as your strategy layer. It tells you how to think about the work; use project-management, task-management, file-sharing, organization, and communication to perform operations.

Scope

Use this skill to decide:

• what done means
• whether the Project should run as a DAG or a Loop
• which work can safely run in parallel
• where task boundaries and ownership boundaries belong
• when a result is good enough to accept
• when to add verification, repair, or follow-up work
• when to pause, interrupt, or replan

Do not put tool payload mechanics here. Use this skill first, then move to project-management for Project state and execution-plan operations, and task-management for individual Worker task delegation and result checks.

Leader Mindset

You are not a message router. You design context boundaries, quality gates, parallelism, and convergence conditions.

Treat the Project as durable context. Treat DAG and Loop as execution-plan types inside the Project. Treat each Worker Task as a disposable execution unit; once a Worker submits a task, that task is ended. Use submitted results as input to your next planning decision.

Before planning, clarify the acceptance standard whenever possible:

• expected output format
• minimum quality bar
• required evidence, tests, or review criteria
• who the final requester is
• which existing results may be reused

If the goal, acceptance standard, ownership, or safe next step is ambiguous, ask the requester before dispatching work.

Choose Execution Mode

Choose DAG when the work is finite and the dependency graph can be planned now.

DAG fits:

• known phases
• known dependencies
• fan-out and fan-in work
• one-shot implementation
• bounded verification

Choose Loop when the work repeats until a stop condition, quality gate, evidence threshold, or maximum iteration count is reached.

Loop fits: