Menu
Approve a phase — sets status to complete, marks all steps reviewed, updates linked card. Use when declaring a phase green.
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 | approve-phase |
| description | Approve a phase — sets status to complete, marks all steps reviewed, updates linked card. Use when declaring a phase green. |
| user-invocable | false |
Single command to perform all mechanical state transitions when declaring a phase green:
complete in progress.yamlreviewed: true in progress.yamlcard: field, updates the card's status to done with current timestampYou still need to write your review decision in review.md separately — that's creative content this script doesn't touch.
python3 ${CLAUDE_PLUGIN_ROOT}/skills/approve-phase/approve-phase.py <phase-dir>
phase-dir: Path to the phase directory (e.g., .ushabti/phases/0005-my-phase)python3 ${CLAUDE_PLUGIN_ROOT}/skills/approve-phase/approve-phase.py .ushabti/phases/0009-tag-reconciler
# Output:
# Phase status: complete
# All steps: reviewed
# Card 'tag-reconciler': marked done
This replaces 4-5 separate Edit calls (status update + marking each step reviewed + card read + card update).
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.
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.
Set the status field in a phase's progress.yaml. Use instead of manual Edit calls when transitioning phase status.