status
Show feature progress and status across all features
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Menu
Show feature progress and status across all features
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação 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 | status |
| description | Show feature progress and status across all features |
| when_to_use | TRIGGER when: user says "status", "progress", or asks about current state. DO NOT TRIGGER when: asking about git status or non-Ship topics. |
| effort | low |
| allowed-tools | Read, Glob |
!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
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"done → "Feature complete! Start something new with /ship:start"$ARGUMENTS