dev-collaboration

Multi-agent software development workflows are coordinated by assigning triad roles (DRAFTER, REVIEWER, BREAKER) to create, review, and harden dev artifacts. This skill enforces explicit prompts, sequencing, and completion criteria via a shared comms.md ledger and artifact change logs.

Code review and feedback loops across multiple agents are structured using a shared comms.md ledger for notifications and explicit role-based sequencing. The REVIEWER role provides feedback on drafted artifacts, ensuring traceable progress through artifact change logs.

Yes, the multi-agent collaboration workflow supports dual-hatted roles when only two agents are available. One agent can assume combined responsibilities from the triad roles (DRAFTER, REVIEWER, BREAKER), maintaining the structured workflow and explicit task sequencing.

A ledger-based communication system coordinates developer artifacts by using a shared comms.md file for explicit notifications and role assignments. Agents log progress and artifact changes to this ledger, ensuring traceable feedback loops and structured handoffs between the triad roles.

Explicit role sequencing for artifact creation is needed when multiple agents must draft, review, and harden dev artifacts collaboratively. This structured workflow ensures assignments and feedback loops are traceable, preventing uncoordinated changes to shared software artifacts.

Yes, multi-agent code review requires a shared artifact change log to track progress and ensure traceable feedback. The dev-collaboration workflow leverages role scripts and artifact change logs alongside the comms.md ledger to enforce explicit completion criteria.