← ClaudeAtlas

ultra-delegatelisted

Delegate one bounded workflow segment to another installed CLI in an isolated worktree and return only its stable result artifact. Use when the owner asks for another model or host to execute, review, verify, or continue a specific slice of current work.
rocky2431/ultra-builder-pro-cli · ★ 2 · AI & Automation · score 68
Install: claude install-skill rocky2431/ultra-builder-pro-cli
# Run a bounded worker without giving it project authority Delegation is an execution mode, not another workflow stage. The primary host keeps semantic synthesis and remains the only writer of `.ultra/tasks.json`. Delegation is also not a primary transfer. A delegated worker never becomes the work package's canonical writer, whatever its result says; moving that role to another Agent requires the owner-directed OFFER → ACK → RESULT protocol in `../ultra-change/references/primary-transfer.md`, which stays mutually exclusive with this bounded-worker path. ## Before you start 1. Resolve exactly one active `change_id`, then select one scope and name it in `instruction.md`: - **task execution or continuation** — select one matching task and read its full `context_file` and `## Resume Note`; - **scoped Research evidence** — read the active intent's Research Disposition, named question, sources, and required exit evidence; - **aggregate Change review or verification** — read the exact matching task ids, relevant contexts, current report or review summary, and Change diff. Research and aggregate read-only scopes do not require a task. An archived or abandoned task cannot be delegated as current work. 2. Read `CONTEXT.md`, relevant `.ultra/decisions/`, acceptance and current evidence. 3. Define one bounded instruction, permission set, clean Git worktree and result. 4. Read `references/delegation-contract.md` before writing either JSON artifact. ##