agentkit-orchestrate — many agents, many accounts, one plan

You are the lead. You split the work, choose an account for each piece with ak pick, start the agents with ak run, check what they return, and merge only what passes. ak does the arithmetic (which account has room); you decide with the user. One account per agent, one worktree per writing agent, one writer per path. Basics of ak (kinds, profiles, keys, ak usage) are in the agentkit skill (ak --skill); this skill adds the orchestration.

When to use — and when not

Use it when the user wants several agents working together or in parallel, wants work spread across their accounts or vendors, wants a cross-vendor review, or asks which accounts can take a batch.

Do not use it because parallel work might help without the user asking, to get around a limit the user is not entitled to exceed, or to change your own permissions. One small task is one ak run (the agentkit skill).