Menu
Find the next unimplemented step in a phase. Use when determining what to work on next.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | find-next-step |
| description | Find the next unimplemented step in a phase. Use when determining what to work on next. |
| user-invocable | false |
Run this command to see active phases and their next unimplemented step:
if [ -d .ushabti/phases ] && [ "$(ls -A .ushabti/phases 2>/dev/null)" ]; then
for dir in .ushabti/phases/*/; do
status=$(grep "^ status:" "$dir/progress.yaml" 2>/dev/null | awk '{print $2}')
if [ "$status" = "building" ] || [ "$status" = "planned" ]; then
name=$(basename "$dir")
next=$(awk '/- id:/{id=$3} /implemented: false/{print id; exit}' "$dir/progress.yaml" 2>/dev/null)
impl=$(grep -c "implemented: true" "$dir/progress.yaml" 2>/dev/null || echo 0)
total=$(grep -c "implemented:" "$dir/progress.yaml" 2>/dev/null || echo 0)
if [ -n "$next" ]; then
echo "$name: next step is $next ($impl/$total done)"
else
echo "$name: all steps implemented - ready for review"
fi
fi
done
else
echo "No active phases"
fi
In progress.yaml, each step has:
id: Step identifier (S001, S002, ...)implemented: false until Builder completes itreviewed: false until Overseer verifies itprogress.yaml to find first step with implemented: falsesteps.mdprogress.yaml: set implemented: true, add notes, list touched filesIf no steps have implemented: false, the phase is ready for review. Set phase.status: review in progress.yaml and hand off to Overseer.
Bootstrap phase context for Builder. Provides current phase, next step, and full phase file contents.
Bootstrap phase context for Overseer. Provides phase under review with full file contents and card metadata.
Approve a phase — sets status to complete, marks all steps reviewed, updates linked card. Use when declaring a phase green.
Create a phase directory with all required files in one call. Use instead of separate mkdir + Write calls when creating a new phase.
Kick a phase back to building — sets status and adds new step entries to progress.yaml. Use when requesting fixes from Builder.
Mark a step as implemented in progress.yaml with notes and touched files. Use after completing each step instead of manual Edit calls.