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 features for parallel development, establishing file ownership boundaries, or managing integration between parallel work streams.

Install with Tessl CLI

npx tessl i github:wshobson/agents --skill parallel-feature-development

What are skills?

Review — 70%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Evaluation results

100%

Parallel Development Plan: Product Review Feature

File ownership decomposition plan

Criteria

Without context

With context

Files enumerated

100%

Cluster identification

100%

Clusters assigned to owners

100%

One owner per file

100%

Interface points defined

100%

Shared type file ownership

100%

Concrete contract definitions

100%

Project-type directory conventions

100%

Branch strategy selection

100%

Integration approach included

100%

Without context: $0.2328 · 7m 8s · 8 turns · 57 in / 4,595 out tokens

With context: $0.4532 · 8m 33s · 17 turns · 106 in / 6,321 out tokens

90%

-6%

Resolving Ownership Conflicts in Parallel Feature Work

Shared file conflict resolution

Criteria

Without context

With context

File restructuring proposed

100%

New files named

100%

One owner per file

100%

Change-request workflow

70%

Simultaneous editing prohibited

90%

100%

Resolution priority justified

100%

Developer-specific actions

100%

Alternatives considered

100%

Interface extraction explored

100%

Concrete file references

100%

Without context: $0.2527 · 2m 26s · 10 turns · 73 in / 4,521 out tokens

With context: $0.4952 · 4m 23s · 25 turns · 2,890 in / 5,697 out tokens

97%

Integration Plan for Parallel Checkout Feature

Integration pattern and merge planning

Criteria

Without context

With context

Dependency-ordered merging

100%

Contract-wins resolution

50%

75%

Response shape conflict addressed

100%

Build check in verification

100%

Type check in verification

100%

Test steps in verification

100%

Interface verification step

100%

Integration pattern named

100%

Pattern suitability evaluated

100%

Lint check in verification

100%

Without context: $0.1792 · 5m 17s · 7 turns · 57 in / 3,130 out tokens

With context: $0.3167 · 6m 8s · 14 turns · 173 in / 4,307 out tokens

Evaluated: about 19 hours ago
Agent: Claude Code

Table of Contents

Parallel Development Plan: Product Review Feature Resolving Ownership Conflicts in Parallel Feature Work Integration Plan for Parallel Checkout Feature

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.