resume
Continue work on an in-progress feature from where you left off
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Continue work on an in-progress feature from where you left off
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when a feature plan has been verified and is ready for implementation — executes tasks with atomic commits
Use when you want to auto-run all remaining Ship steps for a feature without manual step-by-step invocation
Use when a feature has been brainstormed and needs a detailed implementation plan with tasks
Use when a brainstormed feature needs architectural decisions — presents 2-3 approaches for user to choose before planning
Use when a plan has been created and needs independent verification against codebase patterns before building
Use when beginning new feature work, adding functionality, or fixing a bug — runs intensive brainstorming to capture requirements before planning
| name | resume |
| description | Continue work on an in-progress feature from where you left off |
| when_to_use | TRIGGER when: user says "resume", "continue", "pick up", or returns to existing feature. DO NOT TRIGGER when: no features are in-progress. |
| effort | medium |
| allowed-tools | Read, Glob, Skill |
| argument-hint | [feature-name] |
!for f in .planning/features/*/CONTEXT.md; do [ -f "$f" ] && d=$(dirname "$f") && echo "$(basename "$d"): $(sed -n 's/^status: *//p' "$f")"; done 2>/dev/null; true
!for f in .planning/features/*/PLAN.md; do [ -f "$f" ] && d=$(dirname "$f") && echo "$(basename "$d") plan: $(grep -c 'status="done"' "$f" 2>/dev/null || echo 0) done, $(grep -c 'status="pending"' "$f" 2>/dev/null || echo 0) pending"; done 2>/dev/null; true
Resume work on a feature.
Check .planning/features/ for feature directories. If none exist, tell the user to run /ship:start.
If $ARGUMENTS is provided, use it as the feature name. Otherwise, find features that are not done.
If multiple non-done features exist, show them and ask which one to resume.
Read the feature's CONTEXT.md and determine the next action based on status:
| Status | Action |
|---|---|
brainstormed | Run /ship:plan |
planned | Run /ship:plan-verify |
plan-verified | Run /ship:build |
building | Run /ship:build (will resume from last completed task) |
built | Run /ship:verify |
done | Tell the user this feature is complete |
$ARGUMENTS