Skip to content
Back to skills

Resume

ASecurity

Resume an interrupted research-agent run. Re-launches the researcher with instructions to read .research/state.md and log.md, reorient, and continue from the documented current focus. Use after a context compression, session restart, or explicit pause.

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 19, 2026
ai-agentsgo

Security analysis

A100/100

Scanned October 19, 2026

npx -y skills add queelius/claude-anvil --skill resume --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Resume?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Resume
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/queelius-resume/badge)](https://www.skillsdirectory.com/skills/queelius-resume)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: resume
description: >-
  Resume an interrupted research-agent run. Re-launches the researcher
  with instructions to read .research/state.md and log.md, reorient, and
  continue from the documented current focus. Use after a context
  compression, session restart, or explicit pause.
---

# Resume Research

Continue a paused or interrupted research-agent run. If the user names a branch (e.g. "resume the induction-proof branch" or `/research-agent:resume induction-proof`), verify `.research/branches/<name>/` exists and add `<branch>name</branch>` to the launch prompt; all checks below then apply to the branch subtree's files.

## Step 1: Verify .research/ exists

Use the Read tool on `.research/state.md`. If `state.md` is missing but `.research/goal.md` exists (a run interrupted before its first REFLECT), still resume: the researcher reorients from goal.md and log.md and rebuilds state.md. Only when `.research/` itself is absent should you tell the user there is no research to resume and suggest `/research-agent:research`.

## Step 2: Quick state preview

Use Read tool to load `.research/state.md` and the last 5 entries from `.research/log.md`. Show the user a one-paragraph preview of what the researcher will pick up:

> Resuming research on "{goal}". Current focus: {from state.md}. Last cycle was {N} on {date}: {modality} -> {result}. Outstanding sub-problems: {count open}. Untested hypotheses: {count untested}.

## Step 3: Launch the researcher with resume framing

Spawn the researcher agent (Agent tool, subagent_type `research-agent:researcher`) with this prompt:

    <mode>resume</mode>

    <working_directory>
    {absolute path to current working directory}
    </working_directory>

    Resume your research from disk. Do NOT recreate .research/ or
    overwrite goal.md.

    Step 1: Read .research/state.md in full to reload current beliefs,
    sub-problem statuses, hypothesis statuses, and current focus.

    Step 2: Read the last 15 entries of .research/log.md to recall recent
    activity, including any failed attempts and pivots.

    Step 3: Continue your research loop from the documented "Current
    focus" in state.md. Run cycles as normal: DECOMPOSE if needed,
    HYPOTHESIZE, ATTEMPT, EVALUATE, REFLECT. Append to log.md after
    every cycle.

    If state.md indicates the goal has been concluded (synthesis.md
    exists), do NOT run new cycles; tell the orchestrator the research
    is already complete and point at synthesis.md.

## Step 4: Inform the user

After launching, tell the user:

> Researcher resumed. It has reloaded state from .research/state.md and is continuing from the current focus. Use `/research-agent:status` to check progress, or `/research-agent:synthesize` to force conclusion.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.