Menu
Set the status field in a phase's progress.yaml. Use instead of manual Edit calls when transitioning phase status.
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
| name | set-phase-status |
| description | Set the status field in a phase's progress.yaml. Use instead of manual Edit calls when transitioning phase status. |
| user-invocable | false |
Updates the status field in a phase's progress.yaml. Handles both nested and flat YAML formats.
python3 ${CLAUDE_PLUGIN_ROOT}/skills/set-phase-status/set-phase-status.py <phase-dir> <status>
phase-dir: Path to the phase directory (e.g., .ushabti/phases/0005-my-phase)status: One of planned, building, review, complete# Builder finishing implementation
python3 ${CLAUDE_PLUGIN_ROOT}/skills/set-phase-status/set-phase-status.py .ushabti/phases/0005-my-phase review
# Overseer kicking back
python3 ${CLAUDE_PLUGIN_ROOT}/skills/set-phase-status/set-phase-status.py .ushabti/phases/0005-my-phase building
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.