Background work

The parent owns user communication and integration. Default to one worker and the lowest-cost suitable model tier.

Split and isolate

• Assign exclusive write ownership, including specs and task checklists. The parent may draft the next change against an agreed contract, but must wait for verified output before dependent implementation.
• Default to a shared checkout. Choose a worktree when independent code changes need isolation; explain briefly without routinely asking permission. Worktrees do not remove dependencies.
• Check required inputs: T3 worktrees start from the parent local commit and exclude uncommitted edits. If inputs are missing, use safe shared-checkout or sequential work, or ask about committing them. Never stage, commit, or push without explicit authorization.

Delegate and continue

• Use supported asynchronous delegation and retain the task ID. Claude Code supports Agent with run_in_background: true; use T3 delegate_task when app ownership, model settings, or worktree isolation require it. Check available capabilities.
• Return control after launch. Rely on completion notifications, without polling loops or transcript tailing. Check status when needed; after interruption, check the existing task before retrying.
• Supply the outcome, decisions, spec/instruction paths, workspace, write allowlist, acceptance criteria, and required checks. Do not assume conversation inheritance. For OpenSpec Apply, name the change and provide its Apply instructions; the parent handles shared spec consolidation and archiving.

Include in every worker brief:

Edit only assigned files; report cross-scope fixes for the parent. Return early with partial work if findings invalidate the task or continuing risks something irreversible. Put assumptions, relevant edge cases, and adjacent problems in a "Surprises" section at the top; ignore out-of-scope trivia. Report changes, checks actually run, remaining issues, and workspace details.