entangle

Dependent co-design of coupled subsystems. Spawns one agent PER SUBSYSTEM in isolated worktrees, all sharing a single evolving interface contract file. A coordinator merges contract proposals and broadcasts updates. Agents iterate until the contract stabilizes. Produces N co-designed subsystems plus the negotiated contract.

Arguments

$ARGUMENTS — format: [rounds] subsystem1 subsystem2 [subsystem3...] [path/to/requirements.md] where rounds is optional max iteration count (default: 3, min 2, max 5) and subsystems are named components of the coupled system (min 2, max 5)

Parse Arguments

Extract:

• max_rounds: optional leading integer (default 3, min 2, max 5)
• subsystems: 2-5 named subsystems (e.g., api client, schema migration query-layer, frontend backend data-model)
• requirements_path: optional trailing path to a requirements doc, PRD, or design brief

Validate:

• At least 2 subsystems are provided
• No more than 5 subsystems
• Subsystem names are distinct

Phase 1: Define the Contract

If a requirements path is provided: read it and extract the interfaces, data flows, and coupling points between the named subsystems.

If no requirements path: ask the user to describe:

• What does each subsystem do?
• How do the subsystems communicate? (API calls, shared database, message queue, function calls, etc.)
• What are the hard constraints? (tech stack, protocols, existing code)
• What is the desired end state?

From this, draft the initial contract file — a structured document that defines the interface between all subsystems. The contract format:

# Interface Contract v0

## Status: DRAFT

## Subsystems

- {subsystem_1}: {one-line purpose}
- {subsystem_2}: {one-line purpose}
  ...

## Shared Types

{Data types, schemas, or models that cross subsystem boundaries}

## Interfaces

### {subsystem_1} -> {subsystem_2}

- Endpoint/method: ...
- Input: ...
- Output: ...
- Error cases: ...

### {subsystem_2} -> {subsystem_1}

- Endpoint/method: ...
- Input: ...
- Output: ...
- Error cases: ...

{Repeat for every directional interface between subsystems}

## Constraints

- {Protocol, format, auth, versioning, or other cross-cutting rules}

## Open Questions

- {Unresolved interface decisions}