Menü
Wait for a Claude job to produce a result, blocker, or timeout.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Preflight Claude Code auth, model access, real-browser readiness, workspace path, and permission mode before long delegated jobs.
List Claude jobs for the current workspace.
Refresh or repair the installed CC Codex plugin through Codex plugin commands.
Run an adversarial code review of a Claude job in a fresh independent Claude Code session (thorough; eliminates confirmation bias).
Run a batch of Claude Code instructions via the Batch Parallel Work Orchestration runtime.
Run a Claude Code dynamic deep-research workflow on a question (multi-agent fan-out with WebSearch + cross-checked citations).
Basierend auf der SOC-Berufsklassifikation
| name | claude-wait |
| description | Wait for a Claude job to produce a result, blocker, or timeout. |
You are the Codex skill wrapper for the cc dispatcher.
Resolve <plugin-root> as the parent directory of the skills/ directory that contains this file
(so <plugin-root>/scripts/cc.mjs is the dispatcher). Confirm <plugin-root>/scripts/cc.mjs exists before running.
Run:
node "<plugin-root>/scripts/cc.mjs" wait <jobId-or-prefix>
Return the dispatcher's stdout verbatim. If the command exits non-zero, show stderr/stdout to the user and explain that the dispatcher failed. Do not reimplement the command logic yourself.
Behavior rules:
--json and --compact for machine-readable output when the user
requests it, or when automation needs to parse summary, resultText,
transcriptTail, blockedOn, or actionHints.--timeout <duration> when the user asks for a bounded wait.
Duration examples accepted by the dispatcher: 500ms, 30s, 2m; bare
numbers are seconds.--interval <duration> only when the user explicitly asks to change
the polling cadence.--all only if the user explicitly asks to resolve a job across all
workspaces.$claude-wait polls one job until it reaches a result state, awaiting-followup,
needs_input, stopped, failed, orphaned, or the timeout expires. JSON output
includes:
summary — the same compact job shape as $claude-status --jobresultText — final output when available, otherwise recorded partial output
if one existstranscriptTail — recent transcript lines when a transcript path was capturedsummary.blockedOn,
summary.actionHints.restartWithBypass, and summary.actionHints.stoptimeoutRecovery — present on timeout; includes exact status, partial-result,
stop, and attach commands for the next recovery stepIf the wait times out, the dispatcher exits non-zero but still prints the latest
JSON status/result payload when --json was requested. Surface that payload to
the user rather than discarding it. A timeout does not prove the Claude job is
dead; inspect timeoutRecovery.status, read timeoutRecovery.partialResult if
present, or poll $claude-status --job <jobId> --json --compact.
After waiting, the user typically wants one of:
$claude-result <jobId> — read the final output if summary.resultState is final$claude-result <jobId> --partial — read recorded partial output for an
incomplete job$claude-followup — continue a job that is awaiting a follow-up turn$claude-stop — stop a blocked, stale, or no-longer-needed jobclaude attach <shortId> — resolve manual input such as Chrome browser
selection, passkeys, or permission prompts