What problem does it solve? Splitting a project across multiple agents, developers, or teams often leads to overlapping edits, duplicated effort, unclear ownership, and integration failures. This Skill produces a structured coordination plan that defines who owns what, what depends on what, and when work must synchronize. ## Core Features & Use Cases - Workstream Definition: Maps a project into cohesive workstreams (architecture, UI, data, accessibility, testing, documentation) with objectives, scope, deliverables, and acceptance criteria. - Dependency and Execution Mapping: Distinguishes blocking prerequisites from stable contracts that enable parallel work, and marks execution lanes (start now, start after contract, start after dependency, integration only). - Collision Prevention and Checkpoints: Assigns one owner per shared artifact, defines handoff contracts, and schedules coordination checkpoints with required evidence. - Use Case: A technical lead needs to split a web app rebuild among three agents covering frontend, API, and testing. The Skill outputs a workstream map, ownership table, dependency plan, and launch order so the agents can work in parallel without editing the same files. ## Quick Start Ask the agent to split your project into coordinated workstreams with clear ownership, dependencies, and integration checkpoints for parallel execution.
