Menü
Use when checking feature progress or wanting to see what features exist and their current status
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | ship:status |
| description | Use when checking feature progress or wanting to see what features exist and their current status |
| effort | low |
| allowed-tools | Read, Glob |
Show the status of all features with progress details.
Check if .planning/features/ exists. If not, tell the user no features have been started and suggest /ship:start "your idea".
List all feature directories in .planning/features/.
For each feature, read CONTEXT.md and extract:
If a PLAN.md exists, also extract:
<phase> elements, list each phase with its status and task countsIf a VERIFY.md exists, note whether verification passed or found gaps.
Display as a formatted summary:
## Ship Status
| Feature | Status | Progress | Summary |
|---------|--------|----------|---------|
| {name} | {status} | {done}/{total} tasks | {problem summary} |
For the active (non-done) feature, show additional detail:
Phase progress (if phased plan):
Phase 1: {name} — done (3/3 tasks)
Phase 2: {name} — building (1/4 tasks) ← current
Phase 3: {name} — pending (0/2 tasks)
Next step based on status:
brainstormed → "Next: /ship:plan to create the implementation plan"planned → "Next: /ship:plan-verify to verify the plan against the codebase"plan-verified → "Next: /ship:build to start building"building → "Next: /ship:build to continue building (or /ship:resume in a new session)"built → "Next: /ship:verify to verify acceptance criteria and hunt bugs"done → "Feature complete! Start something new with /ship:start"$ARGUMENTS
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