parallel-feature-development

1# Parallel Feature Development
2 
3Strategies for decomposing features into parallel work streams, establishing file ownership boundaries, avoiding conflicts, and integrating results from multiple implementer agents.
4 
5## When to Use This Skill
6 
7- Decomposing a feature for parallel implementation
8- Establishing file ownership boundaries between agents
9- Designing interface contracts between parallel work streams
10- Choosing integration strategies (vertical slice vs horizontal layer)
11- Managing branch and merge workflows for parallel development
12 
13## File Ownership Strategies
14 
15### By Directory
16 
17Assign each implementer ownership of specific directories:
18 
19```
20implementer-1: src/components/auth/
21implementer-2: src/api/auth/
22implementer-3: tests/auth/
23```
24 
25**Best for**: Well-organized codebases with clear directory boundaries.
26 
27### By Module
28 
29Assign ownership of logical modules (which may span directories):
30 
31```
32implementer-1: Authentication module (login, register, logout)
33implementer-2: Authorization module (roles, permissions, guards)
34```
35 
36**Best for**: Feature-oriented architectures, domain-driven design.
37 
38### By Layer
39 
40Assign ownership of architectural layers:
41 
42```
43implementer-1: UI layer (components, styles, layouts)
44implementer-2: Business logic layer (services, validators)
45implementer-3: Data layer (models, repositories, migrations)
46```
47 
48**Best for**: Traditional MVC/layered architectures.
49 
50## Conflict Avoidance Rules
51 
52### The Cardinal Rule
53…