Menú
Use when returning to continue work on an in-progress feature — picks up where you left off based on feature status
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional 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 | ship:resume |
| description | Use when returning to continue work on an in-progress feature — picks up where you left off based on feature status |
| effort | medium |
| allowed-tools | Read, Write, Edit, Bash, Glob, Grep, WebFetch |
| argument-hint | [feature-name] |
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
