codex-delegate

To run background tasks without losing progress, this skill uses a durable, file-based protocol to track job status and results. It implements a comprehensive failure taxonomy and resume scripts to automatically recover stalled jobs or interrupted processes during Codex delegation.

Yes, you can delegate bulk mechanical edits, code reviews, and design spikes to Codex within isolated workspaces. The skill safely offloads these computational and file-editing tasks to the background while maintaining a clear audit trail for every operation.

The best way to orchestrate long-running Codex jobs is by composing a prompt file and executing the backend script with the appropriate sandbox configuration. This approach ensures complex workflows are tracked, verified, and recoverable across intermittent execution environments without manual intervention.

Yes, you need bash, git, and the codex CLI installed to use this background task delegation skill. These dependencies are required to execute the backend scripts, manage the file-based job directory system, and handle the state recovery protocol.

The failure taxonomy handles stalled jobs by recording status, stderr, and results in a durable file-based job directory. This allows the system to verify task completion, classify the failure, and execute state recovery scripts to resume interrupted processes.

You should not use background task delegation for Codex if your workflow requires immediate, synchronous feedback or lacks an isolated workspace environment. The skill is designed for long-running, complex background tasks that benefit from durable tracking rather than quick, interactive commands.