Directing the team

Your team pulls in approved work on its own — you usually don't have to tell them to start. But when you want them on something right now, or out of order, you have one command.

Say the word

Comment @agentforce on any issue and the team starts on it immediately — no waiting for the next cycle.

One handle, not five names

You met Jules, Alex, Matt, and the rest — but you don't have to remember who does what. @agentforce is the only handle you need. Drop it in a comment on the issue and the right teammate (usually Alex, your developer) picks it up.

@agentforce please start on this one

The word @agentforce anywhere in the comment is enough — the rest is just a note to yourself. A bare @agentforce works too.

When to use it

Most days you won't need this — the team works a steady cycle and picks up approved issues on its own. Reach for @agentforce when you want to:

• Jump the queue — start an issue now instead of waiting for the next cycle.
• Prioritize — point the team at the one thing that matters most today.
• Kick off something specific — you filed an issue and you want it built next.

What happens next

1. You comment @agentforce on the issue.
2. Within a minute or two, your developer opens a draft pull request and gets to work — you'll see it in the activity feed.
3. It goes through review like any other change and lands when you approve it.

Good to know

• Issues, not pull requests. @agentforce starts work on an issue. To ask for changes on an open pull request, just reply in the thread — the team reads your comments there too.
• It's yours to use. Only you and people with access to your repository can start the team this way. A random visitor commenting @agentforce on a public issue does nothing — a deliberate safety guard.
• You still approve. @agentforce starts the work; it never merges anything. Nothing reaches your main branch until you say so.