Delegate

Gemini CLI: This skill is triggered by description matching. State any arguments in your message. Sub-agent spawning is not supported — the automated review step in /submit-for-review must be done manually using the review-agent prompt in a separate session.

What /delegate does

/delegate generates a ready-to-paste prompt that gives another AI agent everything it needs to contribute code on the current branch. Run it during the planning gate of /start (Step 2), before saying go, to carve off part of the work for another agent.

Each /delegate invocation also tells the lead agent to skip that work when it proceeds.

Prerequisites

/delegate relies on context already loaded by /start. If you are not in the middle of a /start planning gate (Case A Step 2 or Case B Step 2), say:

"/delegate is meant to be run during the planning step of /start, before you type go. Run /start first to load the issue context, then use /delegate to carve off tasks."

Stop.

If $ARGUMENTS is empty, ask: "What task should the prompt describe?" and wait for a response.

Step 1 — Gather branch and diff context

git branch --show-current

git diff --name-only dev...HEAD

If that errors because the dev ref isn't present locally, diff against main...HEAD instead.

Step 2 — Build the prompt

Compose the following as a fenced markdown block (```markdown) so the operator can copy it.

Use the issue title, body, and agent implementation notes from the current /start session — do not re-fetch them.

## Your task

<$ARGUMENTS — the operator's description of the delegated work>

## Branch

You are on branch `<branch name>`. Stay on this branch.

## Context

**Issue #<number>: <title>**

<issue body — include the full body as-is>

<if there are agent implementation notes from the issue comments, include them under a "### Agent notes" subheading>

## What's already been done on this branch

<list of changed files from git diff, or "No changes yet — clean branch." if empty>

## Rules

- **Do not commit.** Leave all changes unstaged. The lead developer will handle commits.
- **Be surgical.** Only modify what is necessary for your task. Do not refactor adjacent code, reorganize imports, or "improve" files outside the scope of your task.
- **Do not start until the branch exists on the remote.** The lead developer will create and push the branch. Wait until `git checkout <branch name>` followed by `git pull origin <branch name>` succeeds before beginning work.

Step 3 — Present to operator and update lead scope

Print the generated prompt preceded by:

Here's a delegation prompt for: $ARGUMENTS

Review and edit as needed, then paste into your agent of choice after the lead agent has created and pushed the branch.

Then print the fenced prompt block.

After presenting, record internally that $ARGUMENTS has been delegated. When the operator says go and the lead agent proceeds to write code, it must skip the delegated work. If multiple /delegate invocations occur before go, accumulate all of them.

After presenting, say:

Noted — the lead agent will skip this part when you say go. Run /delegate <another task> to delegate more, or type go to proceed.

Hard rules

• Never commit, push, or modify any files.
• Never post to GitHub (no comments, labels, or issue updates).
• Output only — the skill produces text for the operator to copy.
• Do not suggest or name a specific agent to paste into — that is the operator's choice.