What problem does it solve? When multiple agents or developers implement different parts of the same feature simultaneously, they collide on shared files, drift on interface assumptions, and produce merge conflicts. This Skill provides concrete strategies for decomposing features into independent work streams so parallel implementation proceeds without blocking or conflicting. ## Core Features & Use Cases - File Ownership Strategies: Assign ownership by directory, module, or architectural layer, enforcing the cardinal rule of one owner per file. - Interface Contracts: Define shared TypeScript contract files owned by the team lead so implementers build against each other's APIs before they exist. - Integration Patterns: Choose between vertical slices, horizontal layers, or hybrid decomposition, plus single-branch, sub-branch, or trunk-based merge workflows. - Use Case: Splitting a full-stack authentication feature across three implementer agents—one owns login UI and API as a vertical slice, another owns shared JWT middleware, and the third owns tests—while a lead-owned contract file keeps signatures aligned. ## Quick Start Ask the AI to decompose your feature into parallel work streams with file ownership assignments and interface contracts for each implementer.
