---
name: rp-user-action-recovery
description: Regenerates a stale durable human request without accepting an outdated answer.
title: rp-user-action-recovery
canonical_url: https://skilld.dev/gh/wix/skills/rp-user-action-recovery
last_updated: 2026-11-14T03:05:56.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install wix/skills/rp-user-action-recovery`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/rp-user-action-recovery`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/wix/skills/rp-user-action-recovery) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/rp-user-action-recovery`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/rp-user-action-recovery --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/rp-user-action-recovery --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# rp-user-action-recovery

Use when the router reports `user_action_stale`. The request's pinned evidence changed
or disappeared, so answering it is unsafe. Recover only the reported `requestIds`.

1. Read each request through `scripts/user-action.js show --project <projectDir> --request <id>`.
   Identify its stage, effect and pinned artifacts. Do not read secret-bearing config into
   tool output. Preserve the existing request and all recorded answers.
2. For effect `read-back-omission-ack`, run
   `node scripts/user-action.js recover-omission-ack --project <projectDir> --request <stale-id>`.
   Its producer rebuilds the evidence from approved omissions, checkpoints the new request
   and ledger bindings, then supersedes the old request. Retry the same command after an
   interruption. Changed mapping/import inputs require revalidation by their producing stage;
   do not refresh their hashes. Regenerate the completion report so its operator action uses
   the new request, then route again for the human answer. Skip the generic steps below.
3. Use the producing stage's contract to rebuild any missing review evidence and prepare
   a fresh explanation and choices for the current evidence. Do not merely change the old
   digest, reuse outdated prose, answer on the user's behalf, or perform setup/import writes.
   If the evidence cannot be regenerated, report the specific repair needed and stop.
4. Create a new pending request with the same stage, kind and effect scope through
   `scripts/user-action.js create --project <projectDir> --request-file <json>`.
   Pin the current reviewed artifacts. An evidence digest may change; the subject and
   permission being requested must remain the same. A materially different decision needs
   its own producer-owned recovery rather than silently changing this request's scope.
5. Only after the replacement exists, run:
   `node scripts/user-action.js supersede --project <projectDir> --request <stale-id> --replacement <fresh-id>`.
   This refuses a missing, answered, stale or differently scoped replacement. No approval
   effect is applied. Route again and present the fresh request for a human answer.

## Output

The old request remains in `orchestration/user-actions/` as superseded; a fresh pending
replacement carries the current review and artifact hashes. Approvals remain unchanged.
If recovery is blocked, preserve the old request and identify the required repair.
