delegation

name	delegation
description	Portable guidance for delegation. Use when work involves delegation.

When to Use the Split

• Multi-file tasks, or anything touching a domain with a dedicated skill.
• Bulk/mechanical work (migrations across many files, repetitive components) — plan once, execute cheap.
• Skip it for one-file fixes; the overhead isn't worth it.

A failing review resumes the same executor with numbered findings appended — never launch a fresh executor with an open-ended repair prompt.

Rules

• Never hand the executor an open-ended task ("improve X"). If the plan can't be written concretely, the task isn't ready for a cheap model.
• The plan travels whole — don't summarize it when prompting the executor.
• Keep each executor batch to at most 8 tightly coupled files. Larger mechanical sets are fine only when every edit is independently specified.
• Send the original plan, baseline, and allowed-file list to the reviewer so a dirty worktree cannot be mistaken for scope creep.
• The reviewer's verdict gates the commit: "fix first" findings get fixed before anything ships.