Delegate Skills orchestrates multi-agent coding

This is less a magical agent router than a disciplined adapter layer—and that is exactly why it is useful. It treats delegation as a software delivery boundary, not a prompt-forwarding trick.

• –Separate sessions receive only the task brief, reducing context bloat and forcing clearer requirements.
• –A shared `result.json` contract normalizes CLI-specific outputs, exit codes, touched files, and session IDs.
• –Fleet lanes let teams assign feature, testing, or UI work to different coding agents.
• –Reviewers rerun project gates and commit changes themselves, preserving an important human-controlled safety boundary.
• –Node 18+, Git, shell access, and authenticated agent CLIs are required; for small fixes, the orchestration overhead may outweigh the benefit.