Menú
Read-only portfolio scan. No-target scan proposes batches with no dispatch. Two or more targets redirect to $run-items. Single targets redirect to $run-item or $run-epic. No mutation in any mode.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Run a retrospective analysis on completed work to identify process improvement opportunities. Use when the user wants to review a completed batch or item run, or invoke on-demand with a PR number, branch, or date as scope hint.
Compatibility/advanced alias: resolve a native GitHub epic into a bounded workflow execution scope, with optional delegated review and merge gates. For the recommended starting point, use /run-work <epic-target> instead. Use /run-epic when you need direct control over delegation flags (--delegate-review, --may-merge, --max-risk). For explicit item lists, use /run-items.
Bounded multi-item execute command: advance two or more explicit workflow items through Protocol 90 explicit_list mode. For a single item use $run-item; for an epic use $run-epic; for a read-only portfolio scan use $run-work.
Batch-orchestrate the repository's staged AI development workflow. Use when the user wants Codex to discover what can advance or start across multiple items, propose the largest safe batch by priority and parallelization feasibility, and supervise approved item work until it reaches a real terminal condition.
Primary bounded command: advance exactly one non-epic workflow item. Use when the user asks for /run-item or wants to resume a specific development, branch, PR, or issue with the shared bounded prelude before Protocol 91. /run-item-work is a deprecated alias with identical behavior.
Advance a single workflow item until it reaches a real terminal condition. Use when the user wants Codex to resume or advance one specific development, branch, or PR without scanning the whole portfolio.
| name | run-work |
| description | Read-only portfolio scan. No-target scan proposes batches with no dispatch. Two or more targets redirect to $run-items. Single targets redirect to $run-item or $run-epic. No mutation in any mode. |
This is the Codex command-style alias for Claude Code /run-work.
/run-work is portfolio scan and batch proposal only — a fully read-only
command. It performs no mutation in any routing mode.
| Routing mode | Action |
|---|---|
no_target_scan | Protocol 90 scan + propose (no dispatch); operator uses $run-items to execute |
redirect_items | Stop; tell the user to run $run-items with the resolved targets |
redirect_item | Stop; tell the user to run $run-item with the resolved target |
redirect_epic | Stop; tell the user to run $run-epic --epic <n> |
ambiguous | Stop; report stopReason |
AGENTS.md for repository-wide rules../scripts/development-workflow/run-work-router.sh [<target>...] [--json].no_target_scan is
returned, or when stdout includes REDIRECT_COMMAND= (key=value output).
With --json, also check redirectCommand in the routing record.no_target_scan, follow Protocol 90 Steps 1–3 (scan + propose) only.
Do not dispatch items — present the proposal and emit the recommended
/run-items command for the operator to execute.
When proposing multiple implementation items, include Protocol 90's
planless overlap disposition from workflow-batch-overlap.sh: concrete
pairs and unconfirmed suspected pairs are serialized by default, and the
proposal shows pair IDs, typed evidence, evidence hashes, and held-item
reasons.no_target_scan output, keep Protocol 90 report categories distinct:
INFORMATIONAL - not actionable in this proposal,
ACTIONABLE RESUME - can advance now,
PROPOSED BATCH - your decision, and
HELD - not included in proposed batch. Approval applies only to
PROPOSED BATCH - your decision items; informational records are excluded
unless the operator explicitly names them in a separate bounded command.workflow_hub, preserve selected product repository context in
implementation handoffs so later mutation-oriented commands can route the
artifact owner, local path or remote identity, and PR/reviewer/cleanup work
without re-resolving or guessing.$run-item; for epic bounded runs use $run-epic;
for multi-item execution use $run-items.run-nested-artifact-guard.sh --approved-base. Do not infer a base during
the read-only scan.Routing specification: docs/workflow/development-workflow/protocols/96-run-work-routing-protocol.md