Agent skill · operations · wshobson
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system simultaneously, when establishing file ownership to prevent merge conflicts in a shared codebase, when designing interface contracts so parallel implementers can build against each other's APIs before they are ready, or when deciding whether to use vertical slices versus horizontal layers for a full-stack feature.
Why this skill is useful
Provides specific strategies and patterns for managing parallel development that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-05. 38,570 stars on the source repository.
What this skill does
Parallel Feature Development Strategies for decomposing features into parallel work streams, establishing file ownership boundaries, avoiding conflicts, and integrating results from multiple implementer agents. When to Use This Skill Decomposing a feature for parallel implementation Establishing file ownership boundaries between agents Designing interface contracts between parallel work streams Choosing integration strategies (vertical slice vs horizontal layer) Managing branch and merge workflows for parallel development File Ownership Strategies By Directory Assign each implementer ownership of specific directories: Best for: Well-organized codebases with clear directory boundaries. By Module Assign ownership of logical modules (which may span directories): Best for: Feature-oriented architectures, domain-driven design. By Layer Assign ownership of architectural layers: Best for: Traditional MVC/layered architectures. Conflict Avoidance Rules The Cardinal Rule One owner per file. No file should be assigned to multiple implementers. When Files Must Be Shared If a file genuinely needs changes from multiple implementers: 1. Designate a single owner — One implementer owns the file 2. Other implementers request changes — Message the owner with specific change requests 3. Owner applies changes sequentially — Prevents merge conflicts 4. Alternative: Extract interfaces — Create a separate interface file that the non-owner can import without modifying Interface Contracts When implementers need to coordinate at boundaries: Both implementers import from the contract file but neither modifies it. Integration Patterns Vertical Slice Each implementer builds a complete feature slice (UI + API + tests): Pros: Each slice is independently testable, minimal integration needed. Cons: May duplicate shared utilities, harder with tightly coupled features. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills wshobson/parallel-feature-development