resume-previous-plan
Use when the user wants to resume or rediscover an interrupted optim-plans run; automatically run the active recovery path when one is available.
npx skills add Optim-Agent/optim-plans --skill resume-previous-plan --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Resume Previous Plan Find the user's previous optim-plans run and continue the active recovery path when one is available. 1. First run active status for the current worktree: ```bash python3 scripts/optim_plans.py status --repo <repo> ``` 2. If status succeeds, report the active `run_id`, `status`, `next_action`, and any controller-provided recovery fields: `resume_command`, `retry_command`, `retry_item_id`, `finish_approval_nonce`, and `finish_choices`. 3. If `resume_command` is present, run it. This covers already approved execution launch and retryable execution recovery until the controller reports `blocked`. 4. If status fails with no active pointer, run the Git-common fallback: ```bash python3 scripts/optim_plans.py previous-run --repo <repo> ``` 5. If `previous-run` returns a `candidate`, report its `run_id`, `status`, `artifact_dir`, `terminal_time`, `last_event_type`, and `next_action`. If it returns `candidate: null`, say no preserved run was found. `awaiting_retry_decision` is covered for retryable execution failures: run `resume_command`. Manual recovery and blocked/finish cases still require explicit user approval. Do not approve execution launch, approve finish, re
python3 scripts/optim_plans.py status --repo <repo> python3 scripts/optim_plans.py previous-run --repo <repo>
What does the resume-previous-plan skill do?
Use when the user wants to resume or rediscover an interrupted optim-plans run; automatically run the active recovery path when one is available.
How do I install it?
Run `npx skills add Optim-Agent/optim-plans --skill resume-previous-plan --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Optim-Agent/optim-plans, a repository with 288 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.