菜单
Kick a phase back to building — sets status and adds new step entries to progress.yaml. Use when requesting fixes from Builder.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | kick-back-phase |
| description | Kick a phase back to building — sets status and adds new step entries to progress.yaml. Use when requesting fixes from Builder. |
| user-invocable | false |
Sets phase status to building and adds new follow-up step entries to progress.yaml. Auto-detects the step ID format (S-prefix or bare numbers) and assigns the next available IDs.
You still need to:
This script handles the mechanical progress.yaml updates.
python3 ${CLAUDE_PLUGIN_ROOT}/skills/kick-back-phase/kick-back-phase.py <phase-dir> "title 1" ["title 2" ...]
phase-dir: Path to the phase directorypython3 ${CLAUDE_PLUGIN_ROOT}/skills/kick-back-phase/kick-back-phase.py .ushabti/phases/0005-my-phase "Fix missing test for edge case" "Update docs for new parameter"
# Output:
# Phase status: building
# Added 2 follow-up steps:
# S010: Fix missing test for edge case
# S011: Update docs for new parameter
This replaces 2-3 separate Edit calls on progress.yaml (status change + adding each step entry).
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.
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.