resume

/shipyard:resume - Session Restoration

You are executing the Shipyard resume workflow. Follow these steps precisely.

Step 1: Verify State Exists

Check if .shipyard/ directory exists.

• If it does not exist: Display:

  "No Shipyard project found. Nothing to resume. Run /shipyard:init to start a new project." Stop here.

Step 2: Read Last Position

Follow State Loading Protocol (read STATE.json, HISTORY.md, ROADMAP.md, PROJECT.md, config.json, and recent SUMMARY/VERIFICATION files to establish session context; see docs/PROTOCOLS.md) -- read STATE.json for current phase, position, status, and HISTORY.md for history.

Step 3: Detect Incomplete Work

Scan the current phase directory .shipyard/phases/{N}/ for signs of incomplete work:

Planning was interrupted if:

• RESEARCH.md exists but no plan files
• Some plans exist but verifier hasn't run

Building was interrupted if:

• Plan files exist without corresponding SUMMARY.md files in results/
• SUMMARY.md exists with status partial or failed
• REVIEW.md shows CRITICAL_ISSUES without a subsequent fix

Shipping was interrupted if:

• VERIFICATION.md exists but STATE.json doesn't show "shipped"

Document what was in progress and what remains.

Step 4: Reconstruct Context

Build a context summary by reading (in order):

1. .shipyard/PROJECT.md -- overall project goals
2. .shipyard/ROADMAP.md -- phase overview and progress
3. .shipyard/config.json -- workflow preferences
4. The most recent phase's plans and results
5. The last 2-3 SUMMARY.md files for recent decisions and context
6. Any REVIEW.md files with unresolved issues

Synthesize this into a brief context restoration message:

## Session Restored

**Project:** {name}
**Current Phase:** {N} - {title}
**Last Action:** {description from HISTORY.md}
**Incomplete Work:**
- {list of what was in progress}

**Key Context:**
- {2-3 most important decisions or facts from recent summaries}