ship-resume

Resume interrupted feature development within the Ship framework.

9|3|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/dilhanz/ship --skill ship-resume
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-resume
Source: https://github.com/dilhanz/ship/tree/main/.claude/skills/ship-resume
Command: npx skills add https://github.com/dilhanz/ship --skill ship-resume

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you pick up where you left off in a feature development workflow, ensuring continuity and preventing loss of progress.

Core Features & Use Cases

  • Resumes interrupted work: Automatically determines the next logical step in the Ship development process (plan, build, verify).
  • Context-aware: Reads existing feature context to decide the appropriate action.
  • Use Case: You were working on a new feature, got interrupted, and need to quickly get back to coding. Running this command will put you right back on track.

Quick Start

Use the ship-resume skill to continue working on your current feature.

Frequently Asked Questions about ship-resume

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume an interrupted feature development workflow?

To resume an interrupted feature development workflow, the skill identifies incomplete features by reading existing context files and automatically initiates the next appropriate step, such as planning, building, or verification.

What is the best way to continue development after losing progress on a feature?

The best way to continue development after losing progress is to use an automated continuation process that references feature status and context files to determine exactly where you left off and put you right back on track.

How does automated workflow continuation determine the next development step?

Automated workflow continuation determines the next development step by reading existing feature context and status files to decide whether the appropriate action is to plan, build, or verify the feature.

Do I need existing context files to resume feature development?

Yes, you need existing feature context and status files to resume feature development, as the automated continuation process references these files to identify incomplete features and decide the appropriate next workflow step.

Can I pick up complex development cycles automatically after an interruption?

Yes, you can pick up complex development cycles automatically after an interruption by referencing feature status, which supports the automated continuation of the workflow from the exact point of interruption.