Menu
Check the current status of a phase. Use when you need to understand where a phase is in the workflow.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
| name | get-phase-status |
| description | Check the current status of a phase. Use when you need to understand where a phase is in the workflow. |
| user-invocable | false |
Run this command to see all phases with their status and step counts:
if [ -d .ushabti/phases ] && [ "$(ls -A .ushabti/phases 2>/dev/null)" ]; then
for dir in .ushabti/phases/*/; do
name=$(basename "$dir")
status=$(grep "^ status:" "$dir/progress.yaml" 2>/dev/null | awk '{print $2}')
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)
echo "$name: $status ($impl/$total steps)"
done
else
echo "No phases exist yet"
fi
| Status | Meaning | Next Action |
|---|---|---|
planned | Phase created, not started | Builder begins implementation |
building | Implementation in progress | Builder continues or addresses fixes |
review | Implementation complete | Overseer reviews |
complete | Phase is green | Scribe plans next phase |
planned → building (Builder starts)
building → review (Builder finishes all steps)
review → building (Overseer requests fixes)
review → complete (Overseer approves)