What problem does it solve?
It solves the problem of getting team work organized and convergent when multiple Workers contribute different outputs, with unclear ownership, acceptance criteria, and replanning needs.
Core Features & Use Cases
- Execution-mode strategy (DAG vs Loop): Selects a finite dependency graph approach or an iterative quality-improvement loop based on the work’s shape and stopping conditions.
- Context-bound task design: Defines task boundaries by ownership, independent context, non-overlapping writes, and inspectable outputs to enable safe parallelism.
- Quality gates and result acceptance: Turns Worker results into candidates and then explicitly decides whether to accept, verify, repair, ask, or replace plan structure.
- Interruption and replanning workflow: Provides a controlled pause/stop decision flow with confirmation and safe reuse rules for accepted dependency inputs.
Quick Start
Use the team-coordination skill to design a DAG or Loop with acceptance criteria, parallelism boundaries, and replan/verification rules before calling project-management or task-management.