esper:continue
Productivityesper:continue is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Resume an interrupted session. Reads the active increment, assesses progress, and picks up where the last session left off.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/workflow/esper-continue/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/esper-continue, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
You are resuming an interrupted implementation session.
Step 1: Check setup
Run esperkit context get. If it fails, tell the user to run esper:init first and stop.
Parse the context JSON.
Step 2: Find the active increment
If active_increment is null:
- Run
esperkit increment list --format jsonto check for pending increments - If pending increments exist: "No active increment. You have pending increments. Run
esper:atomto activate one, oresper:batchto review the queue." - If no increments at all: "No increments found. Run
esper:atomto create one, oresper:specto work on specs." - Stop.
Step 3: Read the active increment
Read the increment file from .esper/increments/active/<filename>.
Parse its frontmatter and full body.
If the increment references a spec file, read it: esperkit spec get <file>
Step 4: Assess current state
Run git log --oneline -10 to see recent commits.
Run git status --porcelain to see uncommitted changes.
Cross-reference against the increment:
- Check
## Scopeitems against recent commits and file changes - Check
## Progresssection for recorded progress - Check
## Files Affectedagainst actual file state - Check
## Verification— run the verification commands if possible
Step 5: Summarize and resume
Present a concise status:
Resuming: [increment title]
Done:
- [completed scope items]
Remaining:
- [incomplete scope items]
Uncommitted changes:
- [files with changes]
Step 6: Continue implementation
Pick up implementation from the first incomplete scope item:
- Follow the
## Scopesection - Create/modify files as planned
- Run verification after each change
- Update
## Progressas work is completed - Commit according to workflow_defaults
When all scope items are complete:
- Run final verification
- Ask the user if they want to finish: "All scope items complete. Run
esper:goto finish, oresper:reviewto verify first."
Available CLI commands
esperkit context get— read contextesperkit increment list— list incrementsesperkit spec get <file>— read a spec