Manages parallel worker contracts and result merging.

Install

mkdir -p .claude/skills/parallel-contract && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15847" && unzip -o skill.zip -d .claude/skills/parallel-contract && rm skill.zip

Installs to .claude/skills/parallel-contract

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Defines the contract for fan-out parallel workers: isolation boundaries, result schema, and merge conflict resolution rules. Use when running parallel sub-agents on independent work units.
188 chars✓ has a “when” trigger
Intermediate

Key capabilities

  • Define isolation boundaries for parallel workers
  • Specify a standard result schema for workers
  • Outline merge conflict resolution rules
  • Check for overlapping file modifications during merge
  • Flag unresolvable conflicts for human review

How it works

This skill defines a contract for parallel workers, enforcing file scope isolation and a standard result schema. A merge agent then resolves conflicts by checking for overlaps and preferring narrower scopes.

Inputs & outputs

You give it
Independent work units processed by parallel sub-agents
You get back
Merged results with conflicts resolved or flagged for human review

When to use parallel-contract

  • Define worker task scope
  • Merge parallel worker results
  • Resolve task conflicts

About this skill

:shield: Isolation Rules

Each worker MUST:

  1. Only modify files within its assigned scope
  2. Not read or modify files in another worker's scope
  3. Return results in the standard schema

:page_facing_up: Result Schema

Workers return:

  • scope: string — the module or file path
  • status: done | partial | failed
  • files_changed: list of paths
  • issues: list of strings
  • output: free-form data

:twisted_rightwards_arrows: Merge Rules

The merge agent resolves conflicts by:

  1. Checking for overlapping file modifications
  2. Preferring the worker with narrower scope
  3. Flagging unresolvable conflicts for human review

When not to use it

  • The task does not involve parallel sub-agents
  • The work units are not independent
  • The task is about database schema evolution without API surface impact

Limitations

  • Each worker MUST only modify files within its assigned scope
  • Each worker MUST NOT read or modify files in another worker's scope
  • Each worker MUST return results in the standard schema

How it compares

This approach standardizes worker isolation and result merging, providing a structured way to manage parallel task outcomes and conflicts, which differs from ad-hoc merging strategies.

Compared to similar skills

parallel-contract side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
parallel-contract (this skill)04moNo flagsIntermediate
openspec-onboard106moReviewBeginner
workflow-orchestration-patterns102moNo flagsAdvanced
meta-automation-architect78moReviewAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry