handoff

What it does

/cl-dev:handoff delegates a step of your workflow to the CodeLantern cloud agent, which picks it up and runs it autonomously. Instead of the skill running interactively in your session, the cloud agent carries out the work against the same issue or pull request and reports back through it. You can step away while a plan gets drafted or a change gets built.

When to use it

Reach for it when a step doesn't need you sitting in front of it, most often planning or implementation, once an issue is claimed and the direction is clear. It's the same workflow, running somewhere else:

… claim-issue → create-impl-plan → approve-plan → implement → …

Good moments to hand off:

• A plan is approved and you want /cl-dev:implement to build it while you focus on something else.
• You want the cloud agent to draft an implementation plan on a claimed issue so it's waiting for you to review.
• You'd rather run a longer step unattended than keep a local session open through it.

Keep a step local when you expect to steer it turn by turn. The interactive skills (like /cl-dev:implement) are built for that back-and-forth.

How to invoke it

From within your coding agent, in the repository you're working in:

/cl-dev:handoff

It works against the issue or pull request you already have in context, so claim the issue first and make sure the step you're delegating is ready to go (for example, a plan should be approved before you hand off the build). If you're returning to work in progress, run /cl-dev:set-context first to bring the current state back into your session, then hand off from there.