Team Coordination (Independent)

What problem does it solve?

Independent specialist heartbeats often lack default coordinators and may lose durable context between runs, so this guidance keeps each lane accountable and prevents inventing unauthorized coordination.

Core Features & Use Cases

• Heartbeat Ownership: Each agent reads its responsibilities first, executes its slice of work, and does not wait for delegation or synthesis from others.
• Durable Records: Capture multi-heartbeat work on the task board, log tradeoffs in the decision log, and summarize conventions in the knowledge log to survive across runs.
• Use Case: When a developer heartbeat uncovers a configuration issue, it records the discovery and chosen fix in the decision log and updates the task board so the next run continues smoothly.

Quick Start

Own a heartbeat slice, persist updates to the task board and logs, and conclude with a HANDOFF section when persistence is enabled.