# Techtide Multi Agent Worktree Dispatch

> Split substantial engineering work across agents or worktrees with disjoint ownership, clear contracts, validation checkpoints, and integration review. Use when an agent needs Alex Cinovoj / TechTide live-coding patterns, tool routing, guarded prototype-to-production workflows, or cross-harness prompt/skill adapters.

- Skill: `techtideohio/techtide-multi-agent-worktree-dispatch` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add techtideohio/techtide-multi-agent-worktree-dispatch`
- Raw SKILL.md: https://api.skillmd.com/api/skills/techtideohio/techtide-multi-agent-worktree-dispatch/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: TechTideOhio (https://skillmd.com/u/techtideohio)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/techtideohio/techtide-multi-agent-worktree-dispatch

---


# TechTide Multi-Agent Worktree Dispatch

Split substantial engineering work across agents or worktrees with disjoint ownership, clear contracts, validation checkpoints, and integration review.

## Source Pattern

This skill is distilled from sanitized Alex Cinovoj / TechTide local workflow patterns. Load `references/source-patterns.md` when you need the source anchors and extraction rationale. Load `references/adapter-map.md` when preparing Cursor, Kiro, Lovable, v0, or Replit companion outputs.

## Workflow

1. Decompose work by independent files, modules, or verification surfaces.
2. Assign each agent a bounded write scope, task contract, and expected output.
3. Keep the critical path local when immediate decisions depend on the result.
4. Integrate by reviewing diffs, running combined tests, and resolving overlapping assumptions.
5. Close or archive transient agent artifacts when they are no longer needed.

## Output Contract

Return a concise brief with these fields:

- dispatch map
- agent contracts
- integration checklist
- verification record
- verification performed or still required
- security and privacy notes

## Guardrails

- Extract reusable methods, not private local content.
- Do not request or expose credentials, tokens, DSNs, service-role keys, customer data, lead lists, or private business exports.
- Use placeholders for people, accounts, projects, URLs, and datasets unless the user explicitly provides public-safe values.
- Require explicit human approval before production mutation, external-recipient messaging, public deployment, billing changes, or destructive filesystem actions.
- Preserve Alex Cinovoj / TechTide attribution while keeping old repo provenance and unrelated contributor markers out of public artifacts.

## Harness Policy

- Use this as a native `SKILL.md` for Claude Code, Codex, Gemini, and Copilot-compatible exports.
- For Cursor, create a focused project rule or workflow note rather than copying this whole skill as an always-on rule.
- For Kiro, create steering only when the workflow can be made short and inclusion-scoped.
- For Lovable, v0, and Replit, turn the workflow into prompt kits, readiness checklists, and handoff prompts.