ship-resume
Skill1 starsChanged 7 months agoMITView on GitHub
Resume from last checkpoint after session restart or compaction. Reads progress.json and reconstructs state.
In this repository43 other files it gives its agents.
- accessibilitySkill
- agent-evalSkill
- agentic-engineeringSkill
- ai-regression-testingSkill
- api-designSkill
- atomic-planningSkill
- backend-patternsSkill
- coding-standards-eccSkill
- context-engineeringSkill
- frontend-patternsSkill
- git-worktreesSkill
- langchain-dependenciesSkill
- langchain-fundamentalsSkill
- langchain-middlewareSkill
- langchain-ragSkill
- langgraph-fundamentalsSkill
- langgraph-persistenceSkill
- minimalist-skillSkill
- output-skillSkill
- redesign-skillSkill
- security-scanSkill
- ship-architectSkill
- ship-autoSkill
- ship-bugfixSkill
- ship-deploySkill
- ship-discoverSkill
- ship-executeSkill
- ship-finish-branchSkill
- ship-newSkill
- ship-planSkill
- ship-researchSkill
- ship-reviewSkill
- ship-settingsSkill
- ship-specSkill
- ship-statusSkill
- ship-testSkill
- ship-worktreeSkill
- soft-skillSkill
- systematic-debuggingSkill
- taste-skillSkill
- test-driven-developmentSkill
- two-stage-reviewSkill
- verification-before-completionSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Read the relevant state files for the current phase:
- Distinctive: line 13
If in discovery: read PROJECT.md
- Very specific: line 14
If in research/spec/architect: read CONTEXT.md + any completed state files
- Distinctive: line 15
If in execution: read PRD.md + ARCHITECTURE.md + current plan file
- Distinctive: line 16
If a worktree exists, switch to it.
- Distinctive: line 23
Never re-run completed phases.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Resume — Continue from last checkpoint
Process
- Read
.claude/state/progress.json. - Determine current phase and task from the progress data.
- Read the relevant state files for the current phase:
- If in discovery: read PROJECT.md
- If in research/spec/architect: read CONTEXT.md + any completed state files
- If in execution: read PRD.md + ARCHITECTURE.md + current plan file
- If a worktree exists, switch to it.
- Report current state to the user.
- Suggest the next action.
Rules
- This is the recovery mechanism. It must work after compaction, session restart, or laptop sleep.
- Never re-run completed phases. Pick up from exactly where things left off.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.