Skip to content

claude-world/director-mode-lite / skills/handoff-claude

handoff-claude

Verified

Continue a task in Claude Code through a portable Director handoff packet. Use when work started in Codex CLI or Grok Build should move to Claude, or when a fresh Claude session needs the current decisions and verification evidence.

FileKindSize
SKILL.mdskill md1.4 KB
---
name: handoff-claude
description: Continue a task in Claude Code through a portable Director handoff packet. Use when work started in Codex CLI or Grok Build should move to Claude, or when a fresh Claude session needs the current decisions and verification evidence.
user-invocable: true
---

# Handoff to Claude Code

Use the shared `session-relay` workflow. Claude starts a new native session and
reads the same vendor-neutral packet used by Codex and Grok.

```bash
ROOT="${CLAUDE_PROJECT_DIR:-${GROK_WORKSPACE_ROOT:-}}"
[[ -n "$ROOT" ]] || ROOT="$(git rev-parse --show-toplevel 2>/dev/null || pwd)"
RELAY="$ROOT/.director-mode/bin/director-relay"
[[ -x "$RELAY" ]] || RELAY="$HOME/.claude/bin/director-relay"

"$RELAY" create \
  --from <codex|grok> --to claude \
  --goal "..." --summary "..." --next "..."

"$RELAY" continue --to claude
```

The second command only prints the interactive command. Add `--run` when the
user explicitly wants to launch it, or `--headless` for a one-shot `claude -p`
continuation.

Claude Code's own `--continue` and `--resume` remain the right tools for
resuming a Claude-native history. Use a Director packet when the source is
another CLI, when a concise checkpoint is preferable, or when the workflow may
later move again.

Profiles created with `CLAUDE_CONFIG_DIR` can still isolate authorized Claude
accounts, but profile credentials, permissions, plugins, MCP configuration, and
session histories are not copied into the packet.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall