parallel-feature-development

parallel feature development

wshobson ↓ 7.4k
Claude Code
View source ↗

What it does

  • 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
  • Simple setup, no merge overhead
  • Requires strict file ownership to avoid conflicts

Requirements & configuration

  • If a file genuinely needs changes from multiple implementers:
  • When implementers need to coordinate at boundaries:
  • Cons: More integration points, layer 3 depends on layers 1 and 2.
  • Requires strict file ownership to avoid conflicts
  • Interface contracts drifted: the implementer who owns the API changed a signature without notifying the test implementer. Enforce the rule that contract files require a broadcast before modification.

Derived from the skill's own SKILL.md documentation · extracted 2026-07-23

parallel feature development

Source

Repository: https://github.com/wshobson/agents

parallel-feature-development FAQ

What does the parallel-feature-development skill do?

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. Decomposing a feature for parallel implementation Establishing file ownership boundaries between agents

What does parallel-feature-development require?

If a file genuinely needs changes from multiple implementers: When implementers need to coordinate at boundaries: Cons: More integration points, layer 3 depends on layers 1 and 2. Requires strict file ownership to avoid conflicts Interface contracts drifted: the implementer who owns the API changed a signature without notifying the test implementer. Enforce the rule that contract files require a broadcast before modification.

How do I install parallel-feature-development?

Run: npx -y skills add https://github.com/wshobson/agents --skill parallel-feature-development --agent claude-code — the source lives at github.com/wshobson/agents.

Maintain parallel-feature-development?

Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.

parallel-feature-development on getagentictools
[![parallel-feature-development on getagentictools](https://getagentictools.com/badge/skills/wshobson-agents-parallel-feature-development.svg)](https://getagentictools.com/skills/wshobson-agents-parallel-feature-development?ref=badge)
npx agentictools info skills/wshobson-agents-parallel-feature-development

The second line is the CLI lookup for this page — handy in READMEs and docs.