delegate-to-claude

To delegate a GitHub issue to claude-code, this skill uses a headless invocation within an isolated worktree, providing explicit delegation and streaming stdout back to the Codex pane for real-time progress monitoring.

Worktree isolation in a headless claude-code workflow creates a controlled, auditable environment by offloading tasks to a separate git worktree, ensuring the main repository remains unaffected during automated implementation.

Yes, you can stream stdout from claude-code back to the Codex pane. This skill maintains worktree isolation while streaming output, enabling real-time progress tracking for the delegated task.

Yes, explicit permissions flags and user consent considerations are required. The skill enforces clear handoff rules to ensure safe, controlled execution when offloading work to claude-code.

You should use a headless worktree to orchestrate claude-code automation when a Codex workflow needs to offload implementation tasks with explicit delegation, requiring a controlled and isolated execution environment.

The primary limitation is that this delegation process requires explicit handoff rules and user consent. It is specifically designed for Codex workflows offloading to claude-code, not for general automated code generation.