Orchestrate Implementation

Worktree isolation patterns are adapted from using-git-worktrees and David Ondrej's git-worktree. Test-seam patterns are adapted from Matt Pocock's tdd, tests, and mocking guidance (all MIT). Exact pins are recorded in sources.json.

Shared-write separation, smallest-safe-decomposition, and bounded child context are adapted from Cursor's poteto-mode at commit 93b00b89ef425a9c1bac0d0b317dfc49c930ac99 (MIT, Copyright (c) 2026 Cursor).

Overview

The current session is the orchestrator. Keep user intent, scope, authority, routing, candidate assembly, and final acceptance here. Delegate bounded evidence gathering and implementation; do not turn a collection of chat sessions into an implicit scheduler.

The parent owns every child's work: review the diff yourself and write the final conclusion; a child's self-report is input, not acceptance. Delegate large outputs and bulk exploration, but hand children bounded file references and a task contract rather than accumulated conversation history.

REQUIRED SUB-SKILL: Use pi-subagents for child lifecycle, fresh contexts, managed worktrees, artifacts, missions, review, and recovery.

Use pi-intercom only for explicitly named, persistent read-only peers or visible cross-project peers. Spawned children use Pi's native supervisor channel for decisions and progress.

Modes

Choose one mode from the request or configured default: