multi-agent-collaborationlisted

# Multi-Agent Collaboration ## What This Skill Enables An agent that can operate alongside other agents - dividing work, avoiding conflicts, and maintaining consistency - without stepping on each other's changes or duplicating effort. Without this skill, multi-agent workflows produce merge conflicts, inconsistent patterns, and wasted cycles. ## Core Competencies ### 1. Work Partitioning Divide tasks so agents work on independent surfaces: - **By file**: Agent A owns `auth/`, Agent B owns `dashboard/` - **By layer**: Agent A handles API endpoints, Agent B handles UI components - **By feature slice**: Agent A builds user creation end-to-end, Agent B builds search end-to-end - **Never**: Two agents modifying the same file simultaneously ### 2. Contract Agreement When agents produce code that connects, define the contract first: - Agree on interface signatures (function names, parameter types, return types) - Agree on data shapes (request/response schemas, event payloads) - Write the interface or type definition first, implement second - Both agents can work in parallel once the contract is locked ### 3. Convention Adherence Multiple agents must produce code that looks like one person wrote it: - Read the project's style guide or infer it from existing code before writing - Use the same naming patterns, file structure, and error handling approach - Run the same linter and formatter configuration - Follow the same commit message format ### 4. Conflict Prevention Avoid merge